kly really seems to be of no use at all (the
switch-case ahead seems to be hit nearly always), the unlikely in the
write_mem32 seems to be fine.
I compared after each 30 seconds and got median ratio of 1381:1 (for the
likely path) after about 20 minutes, i see a range between 1046:1 and
3511:1. So
On Sonntag 11 November 2007 03:37:28, you (Frank Seidel) wrote:
> While in the read_mem32 the unlikekly really seems to be of no use at all (the
> switch-case ahead seems to be hit nearly always), the unlikely in the
> write_mem32 seems to be fine.
> I compared after each 30 sec
Hello,
this one also holds the - little reworked and optimized -
cleanup of the read/write_mem32 functions.
Comments and any feedback is more than welcome.
Thanks a lot - especially to Jiri, Alan and Greg,
Frank
---
>From [EMAIL PROTECTED] Tue Apr 9 12:12:43 2002
Date: Thu, 24 Aug 2006 01
,
but i have to admit this is most probably a much too naive way of thinking,
especially in regards of compiler optimizations.
And in this special case now there are already most calls (about 80 percent)
caught by the switch-case-shortcuts anyway.
So, i'll revert it.
Thanks a lot for your feedback,
al => So, applied without changes.
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
i++) {
Those changes e.g. aren't needed when just adding the one define as i
suggested above.
All other comments vanished after i studied them better :-)
I'll repost the complete patch in a few moments (in CC to Greg again).
Thanks so much for this,
Frank
-
To unsubscribe from this list: sen
On Sonntag 11 November 2007 17:43:28, you (Frank Seidel) wrote:
> this one also holds the - little reworked and optimized -
> cleanup of the read/write_mem32 functions.
Yes, again a new version, but this one really has a big rework of
the multicard support from Jiri (with minor changes f
a bug, or is it a design decision to not report UEVENTS when removing
PCMCIA pccards? If the latter, why did it happen once in the first excerpt?
Best regards,
Frank Aune
Please CC me if replying.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
doesn't actually do anything with the flag, it
just fixes the warning (and probably accessing the last argument).
Signed-off-by: Frank Lichtenheld <[EMAIL PROTECTED]>
---
drivers/isdn/sc/card.h |2 +-
drivers/isdn/sc/packet.c |2 +-
2 files changed, 2 insertions(+), 2 deletio
arzik <[EMAIL PROTECTED]>
Signed-off-by: Frank Lichtenheld <[EMAIL PROTECTED]>
---
drivers/isdn/sc/shmem.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/isdn/sc/shmem.c b/drivers/isdn/sc/shmem.c
index e0331e0..06a5554 100644
--- a/drivers/isdn/sc/shme
Hi,
this is a small trivial rework of the dcdbas driver so
HAL can get uevents when platform devices are added or removed.
Its tested and seems to work without problem, but please bear in mind
this is the work of a beginner.
Any feedback is very welcome.
Thanks,
Frank
---
Trivial small rework
On Mittwoch 14 November 2007 19:32:01, you (Frank Seidel) wrote:
> Hi,
>
> this is a small trivial rework of the dcdbas driver so
> HAL can get uevents when platform devices are added or removed.
Sorry for the noise! In the meantime i realized (thanks to a nice
colleague) this
rything made it
into mainline, so i8k is due for another facelift.
Needs the following in order to work correctly on my Inspiron E1705:
Add DMI Product name to i8k for Dell MP061 hardware (Inspiron 9400/E1705)
Signed-off-by: Frank Sorenson <[EMAIL PROTECTED]>
- ---
drivers/char/i8k.c |
ore, it is *not* about updatedb, but about all
applications that use a lot of memory, and then terminate.
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-
ge
ipmisensors: sensor 26 (type 2) reading 187
ipmisensors: Send 0x2d 0x18 0x0
That's the only problem I have. It would be great to see it merged.
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Here is my /proc/cpuinfo, I have SMP disabled at the moment. Looks
like my model is slightly older than Cal's.
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 72
model name : AMD Turion(tm) 64 X2 Mobile Technology TL-50
stepping: 2
cpu MHz
> What exact type of machine is it?
Not sure which one Cal has but I have an Averatec 2370 12inch laptop
with an nVidia MCP51 chipset.
AMD Turion(tm) 64 X2 Mobile Technology TL-50
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTE
I have the latest BIOS update for my laptop which is buggy I suppose.
There has been only one update this year if my memory serves me
correctly. Is there any hope to fix this or am I at the mercy of the
hardware vendor which apparenlty doesn't look like they will release
another patch this year. Pl
I have an Averatec 2370 laptop with the nVidia MCP51. With kernel
2.6.20 I had no issues with ACPI however with 2.6.21 and higher the
kernel will hang on boot until I press the suspend button or the power
button in which case the kernel wakes up and finishes the boot
process. Including the followin
> Frank, can you try a non-SMP build with ACPI and see if you still have the
> problem?
I certainly will, I never tried it without it so now I am curious.
Thanks a bunch!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Your work around seems to do the trick. I took out SMP support, added
ACPI and now it boots normally.
On 7/29/07, Frank Hale <[EMAIL PROTECTED]> wrote:
> > Frank, can you try a non-SMP build with ACPI and see if you still have the
> > problem?
>
> I certainly will, I neve
, I see no practical difference between the two.
Please CC me on replies, I am not on the list.
Best regards
Frank Benkstein.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
Frank Benkstein wrote:
> I wonder why there are different permissions needed for VT_PROCESS
> (access to the current virtual console) and VT_LOCKSWITCH
> (CAP_SYS_TTY_CONFIG).
To be more direct:
require CAP_SYS_TTY_CONFIG for VT_SETMODE as its essentially the same as
VT_LOCKSWITCH
Andrew Morton wrote:
> On Wed, 01 Aug 2007 00:22:38 +0200 Frank Benkstein <[EMAIL PROTECTED]> wrote:
>
>> I wonder why there are different permissions needed for VT_PROCESS
>> (access to the current virtual console) and VT_LOCKSWITCH
>> (CAP_SYS_TTY_CONFIG
Andrew Morton wrote:
> On Wed, 01 Aug 2007 04:44:32 +0200
> Frank Benkstein <[EMAIL PROTECTED]> wrote:
>
>> Frank Benkstein wrote:
>>> I wonder why there are different permissions needed for VT_PROCESS
>>> (access to the current virtual console) and VT_LOC
For some reason, the first twenty times I read the doc, I missed the
"terminated and waited-for" bit for RUSAGE_CHILDREN.
Patch withdrawn, for the moment anyway. (And the right fix won't solve
our problem, sigh.)
--
Frank Mayhar <[EMAIL PROTECTED]>
Google, Inc.
-
To unsub
elf was lifted from task_mem() in proc/task_mmu.c. The only
questionable bit is where it does the read_lock() of the tasklist_lock;
although it seems safe enough, I would appreciate if those more
knowledgeable about that locking vet it (briefly) for safety.
Signed-off-by: Frank Mayhar <[EMAIL PROT
Hallo!
I haven't seen anything on linux.kernel about what the merge plans are
for the USB subsystem going into 2.6.24.
Should I be submitting my driver as a patch to linux.kernel or are Alan
or Greg going to push their changes?
Thanks,
Frank
-
To unsubscribe from this list: send the
cation. I
have only used the alsa-utils amixer command to set the controls, and
alsactl to save the settings in /etc/asound.state and then restore them
at boot.
So you could look at the amixer source to see how they are called.
The available controls are normally defined in the ASoC codec
Variables that are only used in #ifdef CONFIG_X86 should also
only be declared there.
Signed-off-by: Frank Lichtenheld <[EMAIL PROTECTED]>
---
drivers/video/uvesafb.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/video/uvesafb.c b/drivers/video/uve
On Samstag 10 November 2007 00:43:29, you (Jiri Slaby) wrote:
> Frank, could you comment (and test) following changes to the nozomi driver?
> I did them before you post the updated version and rediffed them a while
> ago, I hope I haven't done any mistake while doing it.
Great thank
On Samstag 10 November 2007 00:44:10, you (Jiri Slaby) wrote:
> nozomi, expand some functions
>
> nozomi_setup_interrupt and tty_do_close are used only in one place and has
> no pros of being in separate functions.
definitely true, all apllied without change
Thanks,
Frank
-
To
function, because it leaked
> fifo->buffer.
>
> Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
all applied without change
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More major
x out of
> bounds)
The last point i can't retrace, as all those parts were already IMHO.
NTTY_TTY_MINORS is just an alias for MAX_PORT, but of course its much
better readable and also shorter. But i doubt this prevents to an array
index to get out of bounds ;-)
but all applied without a c
ops instead
Sadfully my knowledge of the tty layer is still too low to comment anything
usefull, but all sound and looks reasonable to me.
And i did a special testrun after this patch and couldn't see any problems.
So, applied without change.
Thanks,
Frank
-
To unsubscribe from this list: send
nozomi_setup_private_data in remove, pointers are set in
> probe
All perfect catches IMHO. Applied without changes.
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kerne
step of struct nozomi_devices removal.
i need a closer look at this (together with RFC 8/13).
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info
i also cannot test yet here at home),
i'd defer those two until next week when i get a chance to test and have
more time.
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
to mutexes." ;-)
Now it works again (doesn't deadlock my card anymore).
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
y. I tested this patch and it seems to not break anything.
Applied without changes.
Thanks a lot,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Samstag 10 November 2007 00:50:12, you (Jiri Slaby) wrote:
> nozomi, remove unused includes
>
defered those (to review next week together with patch 7 and 8)
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Sysfs.h uses definitions (e.g. struct list_head s_sibling) from list.h
but does not include it.
Signed-off-by: Frank Haverkamp <[EMAIL PROTECTED]>
---
include/linux/sysfs.h |1 +
1 file changed, 1 insertion(+)
--- ubi-2.6.git.orig/include/linux/sysfs.h
+++ ubi-2.6.git/include/linux/s
it, and we found that it is strange that sysfs.h
is using structs from list.h but is not including it. As result I sent
the patch to propose that it gets included to avoid any possible
trouble.
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
g it in the RQ_CFQQ macro leads to this oops.
The "break"-out patch below for __cfq_dispatch_request might be at least
a possible workaround for this, but it could also be total bullsh..
Perhaps someone smarter might pick this up.. and give a real fix.
Have fun,
Frank
---
block/cfq-ios
the process modified the file
later:
ls -l crypt.img
-rw-r--r-- 1 frank frank 20970175708 Feb 6 22:46 crypt.img
So i do not know if it is related.
Today I had three complete system freezes(keyboard dead,mouse dead, no
magic sysreq), but no Oops while doing:
losetup /dev/loop1 /hom
nd the concept of the input events. In
that case, please give me a short description or let me know were I can
find any documentation.
Best regards, Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mo
aw events?
I have to connected special Point Of Sales Keyboards. Sometimes they are
sending none standard scan codes, only make codes and no break codes. I
had successfully implemented this in kernel version 2.4 and now I have
to do it in 2.6.
Best regards, Frank
-
To unsubscribe from this list:
Hi Jan,
Jan Kara <[EMAIL PROTECTED]> writes:
> On Wed 07-02-07 20:45:26, Frank Hartmann wrote:
>> you are the first to react on my message. I did not try 2.6.20 uptonow.
>>
>> What I did in the meantime:
>>
>> Switched to 2.6.19.2
>>
>> I r
24 04 8d 1c 06 3b 5c 24 08 0f 96 c2 3b
Feb 11 14:30:48 fantasio kernel: EIP: [pg0+546224918/1070154752]
walk_page_buffers+0x1e/0x87 [ext3] SS:ESP 0068:c14f5dbc
regards
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
seems easy. So I will try.
I have some problem: I am not sufficiently familar with git!
I found
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
Is this the way to do a git-bisect?
>From where do I get the 'labels' for good(2.6.17) and bad(2.6.20
[__modpost] Error 1
make: *** [modules] Error 2
xboom
Here's a patch with the easy fix, but I'm not certain it's a permanent fix.
Frank
This patch fixes a compile error when CONFIG_PHYLIB is a module.
Signed-off-by: Frank Sorenson <[EMAIL PROTECTED]>
---
kernel/workqueu
s: fix the festering mess that claims to handle IDE quirks
Hardware is a Dell Inspiron E1705 laptop running FC6 x86_64.
I've attached a netcconsole dump of the panic, as well as lspci output.
Is there any additional information I can provide?
Thanks,
Frank
[0.00] Linux version 2.6.19-
Remi Colinet wrote:
Frank Sorenson <[EMAIL PROTECTED]> wrote:
The latest -git tree panics at boot for me. git-bisect traced the
offending commit to:
368c73d4f689dae0807d0a2aa74c61fd2b9b075f is first bad commit
commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f
Author: Alan Cox &
sizeof(*mpayload) + datalen, GFP_KERNEL);
I may be totally wrong, but is dereferencing a not initialized pointer
(even just for using sizeof) really ok? Wouldn't it be safer to use
a sizeof(struct mmc_key_payload) here?
Thanks,
Frank
-
To unsubscribe from this list: send the line "u
d in Documentation so I hope that enough
information is included.
kind regards
Frank
--
[3.] Keywords (i.e., modules, networking, kernel):
ext3, audio, Oops
[4.] Kernel version (from /proc/version):
fantasio:~/tmp/linux-2.6.19.1$
include/linux/compile.h
MODPOST vmlinux
UIMAGE arch/avr32/boot/images/uImage
"mkimage" command not found - U-Boot images will not be built
Image arch/avr32/boot/images/uImage is ready
make[1]: `arch/avr32/boot/images/vmlinux.elf' is up to date.
Building modules, stage 2.
MODPOST 20
From: Stefan Seyfried <[EMAIL PROTECTED]>
I hate having to recompile the kernel, just to be able to debug suspend.
Remove CONFIG_DISABLE_CONSOLE_SUSPEND, replace it by a tunable in
/sys/power/disable_console_suspend.
Signed-off-by: Stefan Seyfried <[EMAIL PROTECTED]>
Signed-off-by:
MB/sec to 1-2MB/sec, and the system is nearly
unusable.
System is a Dell Inspiron E1705 (Core 2 Duo 2.16GHz) running x86_64 FC6.
Frank
- --
Frank Sorenson - KD7TZK
Linux Systems Engineer, DSS Engineering, UBS AG
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comme
of function
‘vfree’
Signed-off-by: Frank Lichtenheld <[EMAIL PROTECTED]>
---
sound/pci/mixart/mixart_hwdep.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
Against linus' tree from today
diff --git a/sound/pci/mixart/mixart_hwdep.c b/sound/pci/mixart/mixart_hwdep.c
in
This patch (for 2.6.21-mm2) contains a trivial cleanup:
- removes unused exist_board() variation
- removed part is depecrated and doesn't compile anymore
Signed-off-by: Frank Seidel <[EMAIL PROTECTED]>
---
drivers/net/skfp/drvfbi.c | 40
1 f
This patch (for 2.6.21-mm2) contains a trivial cleanup:
- removes unused exist_board() variation
- removed part is depecrated and doesn't compile anymore
Signed-off-by: Frank Seidel <[EMAIL PROTECTED]>
---
drivers/net/skfp/drvfbi.c | 40
1 f
Change of string form like Jeff Garzik suggested
it at http://janitor.kernelnewbies.org/TODO
to get better assembly output as this format only
declares a single variable.
Signed-off-by: Frank Seidel <[EMAIL PROTECTED]>
---
arch/ppc/platforms/4xx/xilinx_ml300.c |2 +-
arch/ppc/platfor
ure
and i really couldn't see any sizeof, typeof or other suspicious usages
of those strings in this set of cleanups.
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://v
y received a failure notice containing
Remote host said: 550 5.2.1 <[EMAIL PROTECTED]>... Mailbox disabled for this
recipient
So, are you Mr. Goos' successor and to be contacted on
changes/suggestions for the skfp driver in the future?
Thanks,
Frank
-
To unsubscribe from this list: sen
he problem?
Thanks,
Frank
- --
Frank Sorenson - KD7TZK
Linux Systems Engineer, DSS Engineering, UBS AG
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGSb5JaI0dwg4A47wRAjkgAJ9Urvpo+cTAbRvbl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Gleixner wrote:
> Frank,
>
> On Tue, 2007-05-15 at 09:06 -0500, Frank Sorenson wrote:
>> Hangs at boot here:
>> Kernel alive
>> Kernel direct mapping tables up to 1 @ 8000-d000
>> (and that&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Sorenson wrote:
> Thomas Gleixner wrote:
>> Frank,
>
>> On Tue, 2007-05-15 at 09:06 -0500, Frank Sorenson wrote:
>>> Hangs at boot here:
>>> Kernel alive
>>> Kernel direct mapping tables u
chipsets, when the BIOS
> hides it.
>
> Venki, great work, thanks !
>
> - Another variant of PIT wreckage fixup
> Frank, does this one work for you ?
Unfortunately, no.
After adding *lots* of early_printks, I see that it hangs in
hpet_is_known(hdp) called f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Sorenson wrote:
> After adding *lots* of early_printks, I see that it hangs in
> hpet_is_known(hdp) called from hpet_alloc(&hd), so something in the hpet
> code is still buggy. Adding nohpet to the kernel command line allows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Sorenson wrote:
> Hrm. Looks like it gets past the hpet_is_known There's still something
> in the hpet detection code, but I didn't get to the bottom of it yet.
> I'll do some more debugging to track down where it&#
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Samstag, 30. Juni 2007, Robert Hancock wrote:
> Frank Fiene wrote:
> > Lenovo Z61p, Intel Core2 Duo T7200
> >
> > I have 4GB RAM installed and BIOS recognize 4GB RAM.
> > Linux kernel (Ubuntu-7.04, 32bit-PAE and 64bit, openSUSE-10.2
> > 32bit-PAE and 64b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Lameter wrote:
> On Thu, 17 May 2007, Frank Sorenson wrote:
>> Frank Sorenson wrote:
>>
>>> Hrm. Looks like it gets past the hpet_is_known There's still something
>>> in the hpet detection code, bu
up.
>
> Does the same problem show up with
>
> http://tglx.de/projects/hrtimers/2.6.22-rc2/linux-2.6.22-rc2-x86_64-highres-v1.patch
>
> tglx
I see the slow bootup as well, even with 2.6.22-rc2-hrt1. It takes at
least 5 times as long to boot, for X to start, to login, etc.
F
)))
> + return -EFAULT;
> ...
Have fun,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ACK for both patches,
thank you Eric for the patches, will add them to my patchset
for Jeff.
Frank
On Thu, Apr 19, 2007 at 01:58:40AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]>
>
> Use kthread_run to start the lcs kernel threads not a
&
t the usable size of a block is not n^2 anymore. I think it
was a good decision, because if we would have put in in NAND OOB area,
the discussion here might be limited to NAND users only.
Regards,
Frank Haverkamp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
rds,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ng with
networking or usb.
Is it possible, that one of the commit above causes Oopses like the stuff below?
regards
Frank
Feb 25 17:07:29 fantasio kernel: printing eip:
Feb 25 17:07:29 fantasio kernel: e0c03b16
Feb 25 17:07:29 fantasio kernel: *pde =
Feb 25 17:07:29 fantasio kernel: Oops: 00
figure out
resonable parameters:
mtd=4
With the three arrays we did not see a nice way of achieving this.
ubimtds=content,4,7
hdroffs=1984,?,1984
dataoff=s2048,?,2048
The ? look odd, don't they?
We also looked at the slram parameters which are like this:
slram=nam
Hi Doug,
On 2016/7/21 5:33, Doug Anderson wrote:
Hi,
On Tue, Jul 19, 2016 at 12:28 AM, Frank Wang wrote:
You need a patch description here, even for simple patches. All you
have now is a subject.
OK, I will describe it next version.
Signed-off-by: Frank Wang
---
arch/arm64/boot/dts
Hi Heiko,
On 2016/7/21 17:26, Heiko Stübner wrote:
Hi Frank,
Am Donnerstag, 21. Juli 2016, 10:49:53 schrieb Frank Wang:
@@ -69,6 +69,15 @@
regulator-max-microvolt = <330>;
};
+ vbus_host: vbus-host-regulator {
+ comp
ription into the devicetree bindings.
- Optimized some process of driver.
Frank Wang (4):
Documentation: bindings: add DT documentation for Rockchip USB2PHY
phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy
arm64: dts: rockchip: add usb2-phy support for rk3399
arm64: d
Signed-off-by: Frank Wang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6:
- Changed '_' to '-' for otg-id and otg-bvalid property.
Changes in v5:
- Added 'reg' property to ide
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is required necessarily.
Signed-off-by: Frank Wang
Suggested-by: Heiko Stuebner
Suggested-by: Guenter Roeck
Add usb2-phy nodes and specify phys phandle for ehci.
Signed-off-by: Frank Wang
---
Changes in v9:
- Move the usb gpio config to rk3399-evb.dts
- Fix ehci phy-names property.
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 42 +-
1 file changed, 41 insertions(+), 1
Add vcc5v0_host regulator for usb2-phy and enable host-port support.
Signed-off-by: Frank Wang
---
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 44 +++
1 file changed, 44 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
b/arch/arm64/boot/dts
mmdc/write-accesses/
427.76 MB mmdc/write-bytes/
5.334757334 seconds time elapsed
Signed-off-by: Zhengyu Shen
Signed-off-by: Frank Li
---
Changes from v6 to v7
use mmdc_pmu prefix
remove unnecessary check
improve group event check according to mark's feed
mmdc/write-accesses/
427.76 MB mmdc/write-bytes/
5.334757334 seconds time elapsed
Signed-off-by: Zhengyu Shen
Signed-off-by: Frank Li
---
Changes from v7 to v8
fix a group event check problem, should be slibling.
Changes from v6 to v7
use mmdc_pmu prefix
if (get_order(size) > MAX_ORDER)
> return NULL;
>
> - return dma_alloc_coherent(&cd->pci_dev->dev, size, dma_handle,
> - GFP_KERNEL);
> + return dma_zalloc_coherent(&cd->pci_dev->dev, size, dma_handle,
> + GFP_KERNEL);
> }
>
> void __genwqe_free_consistent(struct genwqe_dev *cd, size_t size,
> --
> 2.5.5
>
I think this should be fine.
Signed-off-by: Frank Haverkamp
Hi Guenter,
On 2016/6/17 21:20, Guenter Roeck wrote:
Hi Frank,
On 06/16/2016 11:43 PM, Frank Wang wrote:
Hi Guenter,
On 2016/6/17 12:59, Guenter Roeck wrote:
On 06/16/2016 07:09 PM, Frank Wang wrote:
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before
Hi Heiko & Guenter,
On 2016/6/20 11:00, Guenter Roeck wrote:
On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang wrote:
Hi Guenter,
On 2016/6/17 21:20, Guenter Roeck wrote:
Hi Frank,
On 06/16/2016 11:43 PM, Frank Wang wrote:
Hi Guenter,
On 2016/6/17 12:59, Guenter Roeck wrote:
On 06/16/201
Hi Heiko,
On 2016/6/20 12:56, Guenter Roeck wrote:
Hi Frank,
On Sun, Jun 19, 2016 at 8:32 PM, Frank Wang wrote:
Hi Heiko & Guenter,
On 2016/6/20 11:00, Guenter Roeck wrote:
On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang
wrote:
Hi Guenter,
On 2016/6/17 21:20, Guenter Roeck wrote:
Hi Heiko,
On 2016/6/21 17:05, Heiko Stübner wrote:
Hi Frank,
Am Dienstag, 21. Juni 2016, 15:52:45 schrieb Frank Wang:
On 2016/6/20 12:56, Guenter Roeck wrote:
On Sun, Jun 19, 2016 at 8:32 PM, Frank Wang
wrote:
Turns out my problem was one of terminology. Using "suspend" and
&quo
Signed-off-by: Frank Wang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v7: None
Changes in v6:
- Changed '_' to '-' for otg-id and otg-bvalid property.
Changes in v5:
- Added 'reg' property to identify the different phy-blocks.
Chan
on into the devicetree bindings.
- Optimized some process of driver.
Frank Wang (2):
Documentation: bindings: add DT documentation for Rockchip USB2PHY
phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy
.../bindings/phy/phy-rockchip-inno-usb2.txt| 64 ++
drivers/phy/Kconfi
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is required necessarily.
Signed-off-by: Frank Wang
Suggested-by: Heiko Stuebner
Suggested-by: Guenter Roeck
o the mailbox driver could not
extract the contents of message, if it do cast type, it may become
non-general from driver view. Hence, is it possible to add a message
header into scpi_xfer which for the bottom mailbox driver or dope out
any other methods to solve it?
BR.
Frank
Initial RFC di
mmdc/write-accesses/
427.76 MB mmdc/write-bytes/
5.334757334 seconds time elapsed
Signed-off-by: Zhengyu Shen
Signed-off-by: Frank Li
---
Changes from v4 to v5
Remove mmdc_pmu:irq
remove static variable cpuhp_mmdc_pmu
remove spin_lock
check is_sampling_e
On 09/08/16 06:38, Rob Herring wrote:
> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren wrote:
>> * Frank Rowand [160831 13:51]:
>>> On 08/29/16 15:35, Tony Lindgren wrote:
>>>> if (of_device_is_incomplete(pdev->dev.of_node, status)) {
>>>>
301 - 400 of 2766 matches
Mail list logo
