Hi Chanwoo,
On 8/29/2013 11:53 AM, Chanwoo Choi wrote:
[snip]
You should keep following naming stlye. extcon-gpio-usbvid.c is wrong naming
style.
- extcon-[device name].c
- extcon-gpio-usbvid.c -> extcon-dra7xx.c or etc.
Actually dra7xx is the SoC name and the USB VBUS/ID detection is not spec
My wife and I won the Euro Millions Lottery of 41 Million British Pounds and we
have decided to donate 1.5 million British Pounds to 6 individuals worldwide as
our own charity project. Your email address was among the emails which were
submitted to us by the Google, Inc as a web user, which was
Hi,
On Wed, Aug 28, 2013 at 09:46:42PM -0700, Giovanni wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=60810
>
> Bug ID: 60810
> Summary: Kernel oops with controller XHCI while wait usb packet
>
Can you give us a detail kernel top commit and config which you built
Peter Chen writes:
> Changed for v2:
> - Fixed the build error for patch 5/5
>
> Below are un-queued chipidea patches, some of them were reviewed.
I'd like to send 1/5, 3/5 and 4/5 now, have a closer look at 2/5 and
queue 5/5 for 3.13 unless you have objections.
Regards,
--
Alex
--
To unsubscri
On Wed, Aug 28, 2013 at 11:15 PM, Sarah Sharp
wrote:
> On Wed, Aug 28, 2013 at 07:39:14PM +0200, Sedat Dilek wrote:
>> On Wed, Aug 28, 2013 at 7:24 PM, Dmitry Kasatkin
>> wrote:
>> Still noone answered me why "drivers/usb/host/xhci-ring.c" does NOT
>> include (dev_info_ratelimited() and other d
On Wed, Aug 28, 2013 at 7:46 PM, Alan Stern wrote:
> On Wed, 28 Aug 2013, Clemens Ladisch wrote:
>
>> Sorry, what I said applies more to explicit sync endpoints. When using
>> implicit sync, a playback URB is submitted for each completed capture
>> URB, with the number of samples per packet ident
David Miller writes:
> From: Rob Gardner
> Date: Wed, 28 Aug 2013 18:40:22 -0600
>
>> The exception list means "usb_device_id entries for specific devices
>> that are known to need the workaround." There are just two such entries.
>> There isn't even a separate list. So maybe we just have a nome
This patch removes ehci_vdbg debugging statements from EHCI host controller
driver because they produce too much information, lowering the signal to noise
ratio when debugging, and because they are not used anymore.
Signed-off-by: Xenia Ragiadakou
---
drivers/usb/host/ehci-hub.c | 6 -
dr
The debugging code for ehci is enabled to run if the DEBUG flag is defined.
This patch enables the debugging code also when the kernel is configured
with dynamic debugging on.
Signed-off-by: Xenia Ragiadakou
---
drivers/usb/host/ehci-dbg.c | 8
drivers/usb/host/ehci-fsl.c | 2 +-
dr
This patch removes the duplicate of debug_async_open() prototype following
three lines below the debug_async_open() declaration.
Signed-off-by: Xenia Ragiadakou
---
drivers/usb/host/ehci-dbg.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/host/ehci-dbg.c b/drivers/usb/host/ehci-
This patch removes the ehci statictics information output in ehci_stop()
because they do not provide interesting info. At any case, the current
statistics can be viewed by reading the 'registers' file in debugfs.
Signed-off-by: Xenia Ragiadakou
---
drivers/usb/host/ehci-hcd.c | 8
1 fil
On Thu, Aug 29, 2013 at 01:07:36AM +0800, Greg Kroah-Hartman wrote:
> On Wed, Aug 28, 2013 at 04:09:32PM +0800, Huang Rui wrote:
> > On Wed, Aug 28, 2013 at 11:38:28AM +0800, Greg Kroah-Hartman wrote:
> > > On Wed, Aug 28, 2013 at 11:13:12AM +0800, Huang Rui wrote:
> >
> > Yes, you're right. This
On Thu, Aug 29, 2013 at 01:07:36AM +0800, Greg Kroah-Hartman wrote:
> On Wed, Aug 28, 2013 at 04:09:32PM +0800, Huang Rui wrote:
> > On Wed, Aug 28, 2013 at 11:38:28AM +0800, Greg Kroah-Hartman wrote:
> > > On Wed, Aug 28, 2013 at 11:13:12AM +0800, Huang Rui wrote:
>
> Then just do this "quirk" fo
On Thu, Aug 29, 2013 at 02:59:50AM +0800, Alan Stern wrote:
> On Wed, 28 Aug 2013, Greg Kroah-Hartman wrote:
>
> > On Wed, Aug 28, 2013 at 01:13:46PM -0400, Alan Stern wrote:
> > > On Wed, 28 Aug 2013, Greg Kroah-Hartman wrote:
> > >
> > > > > [Q] Why the special devices are only mice? Would high
On 08/29/2013 04:30 PM, George Cherian wrote:
> Hi Chanwoo,
>
> On 8/29/2013 11:53 AM, Chanwoo Choi wrote:
> [snip]
>> You should keep following naming stlye. extcon-gpio-usbvid.c is wrong naming
>> style.
>> - extcon-[device name].c
>> - extcon-gpio-usbvid.c -> extcon-dra7xx.c or etc.
>>> Actual
On Thu, Aug 29, 2013 at 12:05 AM, Alan Stern wrote:
> On Wed, 28 Aug 2013, Ming Lei wrote:
>
>> > Think about it this way: Why did you write the "USB: EHCI: improve
>> > interrupt qh unlink" patch in the first place? Essentially the same
>> > reason applies to uhci-hcd and ohci-hcd, and they will
Hi Xenia,
thank you for the patch. I tried to reproduce the error with patched 3.10.9
kernel but it seems the kmemleak is indeed gone. Provided I get only these lines
logged which used to be followed by kmemleak findings I believe the original
fixed:
[15885.206032] usb 4-2.1: reset SuperSpeed US
On Thu, Aug 29, 2013 at 10:53:50AM +0300, Alexander Shishkin wrote:
> Peter Chen writes:
>
> > Changed for v2:
> > - Fixed the build error for patch 5/5
> >
> > Below are un-queued chipidea patches, some of them were reviewed.
>
> I'd like to send 1/5, 3/5 and 4/5 now, have a closer look at 2/5
On Tue, Aug 27, 2013 at 10:39 PM, Alan Stern wrote:
> On Tue, 27 Aug 2013, Ming Lei wrote:
>
>> > Yes. A new spinlock would be needed to synchronize the top half and
>> > the bottom half. The same spinlock would also be used to avoid
>> > scheduling the tasklet when it is already running, like i
On 8/29/2013 4:07 PM, Chanwoo Choi wrote:
On 08/29/2013 04:30 PM, George Cherian wrote:
Hi Chanwoo,
On 8/29/2013 11:53 AM, Chanwoo Choi wrote:
[snip]
You should keep following naming stlye. extcon-gpio-usbvid.c is wrong naming
style.
- extcon-[device name].c
- extcon-gpio-usbvid.c -> extcon-d
On 08/29/2013 02:21 PM, Martin MOKREJŠ wrote:
Hi Xenia,
thank you for the patch. I tried to reproduce the error with patched 3.10.9
kernel but it seems the kmemleak is indeed gone. Provided I get only these lines
logged which used to be followed by kmemleak findings I believe the original
fixe
On 08/29/2013 08:48 PM, George Cherian wrote:
> On 8/29/2013 4:07 PM, Chanwoo Choi wrote:
>> On 08/29/2013 04:30 PM, George Cherian wrote:
>>> Hi Chanwoo,
>>>
>>> On 8/29/2013 11:53 AM, Chanwoo Choi wrote:
>>> [snip]
You should keep following naming stlye. extcon-gpio-usbvid.c is wrong
n
Hi Xenia,
thank you, how about inclusion of the "parent hub" number in the
following message (as of now):
Parent hub missing LPM exit latency info. Power management will be impacted.
I find it awkward to later on run manually lspci/lsusb to find what is the
parent.
I think I do NOT get the
Actually, there is some new bug I haven't seen before (this is 3.10.9 kernel).
First of all, I see my TI XHCI controller does not use MSI-X anymore, will have
to check my .config why is it so.
Second, it should have IRQ 45 and 46 according to dmesg. But lspci reports
IRQ 16 is used by TI XHCI contr
Hi Chanwoo,
On 8/29/2013 5:42 PM, Chanwoo Choi wrote:
[big snip ]
I tested various development board based on Samsung Exynos series SoC.
Although some gpio of Exynos series SoC set high state(non zero, 1) as default
value,
this gpio state could mean off state, disconnected or un-powered state
On Wed, 28 Aug 2013, H. Peter Anvin wrote:
> On 08/28/2013 12:16 PM, Alan Stern wrote:
> > Russell, Peter, and Ingo:
> >
> > Can you folks enlighten us regarding this issue for some common
> > architectures?
> >
>
> On x86, IRET is a serializing instruction; it guarantees hard
> serialization
Hi,
I have a custom device, which is usb-hid. But, when i plug it in the system,
it is not recognized as a usb-hid device. I have put prints on the
usbhid_probe() function, to confirm that, but there is no prints in the
dmesg, which confirms that this is not recognized as a usb-hid device.
NO
On Thu, 29 Aug 2013, Ming Lei wrote:
> On Wed, 28 Aug 2013 12:23:31 -0400 (EDT)
> Alan Stern wrote:
>
> > You must never alter ehci->last_iso_frame like this. It violates the
> > driver's invariants for time to run "backward". After all, there may
> > already be other TDs scheduled for the f
On Thu, 29 Aug 2013, James Stone wrote:
> On Wed, Aug 28, 2013 at 7:46 PM, Alan Stern wrote:
> > On Wed, 28 Aug 2013, Clemens Ladisch wrote:
> >
> >> Sorry, what I said applies more to explicit sync endpoints. When using
> >> implicit sync, a playback URB is submitted for each completed capture
On Thu, 29 Aug 2013, Xenia Ragiadakou wrote:
> This patch removes ehci_vdbg debugging statements from EHCI host controller
> driver because they produce too much information, lowering the signal to noise
> ratio when debugging, and because they are not used anymore.
>
> Signed-off-by: Xenia Ragia
On Thu, 29 Aug 2013, Ming Lei wrote:
> >> You have said the same problem exists on these drivers already
> >> without giveback in tasklet patch, so for the problem and solution,
> >> there is no difference.
> >
> > What do you mean? We can't fix those other drivers by changing
> > ehci-hcd. It's
On Thu, 29 Aug 2013, Ming Lei wrote:
> > In the end, this comes down to a decision about priorities. Do you
> > want to give higher priority to new events or to givebacks? Overall, I
> > don't think it matters.
>
> If possible, the events should be put higher priority, like events
> handling in
On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> Hi Xenia,
> thank you, how about inclusion of the "parent hub" number in the
> following message (as of now):
>
> Parent hub missing LPM exit latency info. Power management will be impacted.
>
>
>
> I find it awkward to later on run manually lsp
On Thu, 29 Aug 2013, kasi viswanathan wrote:
>
> Hi,
>
> I have a custom device, which is usb-hid. But, when i plug it in the system,
> it is not recognized as a usb-hid device. I have put prints on the
> usbhid_probe() function, to confirm that, but there is no prints in the
> dmesg, which co
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>> Hi Xenia,
>> thank you, how about inclusion of the "parent hub" number in the
>> following message (as of now):
>>
>> Parent hub missing LPM exit latency info. Power management will be
>> impacted.
>>
>>
>>
>> I find it awkwa
Hi,
Can someone help me, please?
Regards,
Kishore.
-Original Message-
From: Krishna Kishore
Sent: Wednesday, August 28, 2013 6:05 PM
To: Chris Lee; Mariusz Bialonczyk
Cc: Linux Media Mailing List; linux-usb@vger.kernel.org
Subject: RE: stv090x vs stv0900 support
Hi,
When read
On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> Alan Stern wrote:
> > On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> >
> >> Hi Xenia,
> >> thank you, how about inclusion of the "parent hub" number in the
> >> following message (as of now):
> >>
> >> Parent hub missing LPM exit latency info. Power m
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>> Alan Stern wrote:
>>> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>>>
Hi Xenia,
thank you, how about inclusion of the "parent hub" number in the
following message (as of now):
Parent hub missing LPM exi
On Wed, 28 Aug 2013, Kevin Archer wrote:
> unbind yielded nothing
>
> using 3.11.0-031100rc5-generic
>
> lsusb -v -s 1:2
>
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
...
> Hub Port Status:
>Port 1: .0103 power enable connect
>Port 2: .0100 power
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>> Hi Xenia,
>> thank you, how about inclusion of the "parent hub" number in the
>> following message (as of now):
>>
>> Parent hub missing LPM exit latency info. Power management will be
>> impacted.
>>
>>
>>
>> I find it awk
On Thu, Aug 29, 2013 at 05:25:55PM +0800, Peter Chen wrote:
> On Thu, Aug 29, 2013 at 10:53:50AM +0300, Alexander Shishkin wrote:
> > Peter Chen writes:
> >
> > > Changed for v2:
> > > - Fixed the build error for patch 5/5
> > >
> > > Below are un-queued chipidea patches, some of them were review
On Thu, Aug 29, 2013 at 03:20:32PM +, Krishna Kishore wrote:
> Hi,
>
> Can someone help me, please?
Personally, I'm not allowed to do so because of:
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential,
> proprietary or legally privileged information. In case you are not th
On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> > Since this device is 4-2, the parent hub is usb4.
>
> Actually, even if that would be a another USB HUB and not a PCI device (root
> hub),
> I would be happy if it extracted something like:
>
> Bus 004 Device 006: ID 2109:0810 $iManufacturer and $i
On 08/29/2013 04:31 PM, Martin MOKREJŠ wrote:
Actually, there is some new bug I haven't seen before (this is 3.10.9 kernel).
First of all, I see my TI XHCI controller does not use MSI-X anymore, will have
to check my .config why is it so.
Second, it should have IRQ 45 and 46 according to dmesg. B
On Thu, Aug 29, 2013 at 10:02:13AM +0200, Sedat Dilek wrote:
> P.S.: The forgotten patch is now in usb-next, but I don't see any
> credits, coins, gold, platin...
Thank you for reporting this. Your name was mentioned in the tag Greg
pulled:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb
Hi Sarah,
I'm getting the following warnings from the 3.10.9 kernel all the time
when I unplug a USB 3 storage device from my laptop:
[203282.987687] usb 4-1: USB disconnect, device number 21
[203282.992904] usb 4-1: Set SEL for device-initiated U1 failed.
[203282.992909] u
On Wed, Aug 28, 2013 at 04:08:12PM -0700, Julius Werner wrote:
> > So the 2.41a has BESL support, but may not set the BLC flag. What
> > happens if we use the HIRD encoding instead? Will things break? It
> > seems like we would need to disable USB 2.0 LPM on that host all
> > together, if it exp
On Thu, 2013-08-22 at 15:41 -0500, Felipe Balbi wrote:
> On Wed, Aug 21, 2013 at 10:13:28AM -0500, Kumar Gala wrote:
> >
> > On Aug 21, 2013, at 8:06 AM, Ivan T. Ivanov wrote:
> >
> > > On Tue, 2013-08-20 at 18:01 +0100, Pawel Moll wrote:
> > >> On Tue, 2013-08-20 at 16:06 +0100, Pawel Moll wrot
On 2013-08-28 21:37, Alan Stern wrote:
>>> No, if you unload the ohci-hcd driver then the webcam won't be used.
>>> Are you certain that merely stopping the daemon program will prevent
>>> the problem?
>>
>> Quite certain but retesting can confirm that.
>
> Maybe without activity, the OHCI cont
In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
descriptor to hold the value read by the device. The new bos descriptor
has to be compared with the old one in order to figure out if device 's
firmware has changed in which case the device has to be reenumerated.
In the original
On Wed, Aug 28, 2013 at 10:15:34PM +, Paul Zimmerman wrote:
> > From: Sarah Sharp [mailto:sarah.a.sh...@linux.intel.com]
> > Sent: Wednesday, August 28, 2013 2:52 PM
> >
> > On Mon, Aug 26, 2013 at 07:37:56PM +, Paul Zimmerman wrote:
> > > > From: Sarah Sharp [mailto:sarah.a.sh...@linux.in
At 32 frames/period (reported round-trip latency 1.33ms), it starts up
but there are too many xruns for it to be usable.
James
On Thu, Aug 29, 2013 at 4:00 PM, Alan Stern wrote:
> On Thu, 29 Aug 2013, James Stone wrote:
>
>> On Wed, Aug 28, 2013 at 7:46 PM, Alan Stern
>> wrote:
>> > On Wed, 28
On Thu, Aug 29, 2013 at 08:37:57PM +0300, Xenia Ragiadakou wrote:
> In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
> descriptor to hold the value read by the device. The new bos descriptor
> has to be compared with the old one in order to figure out if device 's
> firmware ha
> If you take a look at Table
> 13: BESL/HIRD Encoding from the xHCI spec version including errata to
> 08/14/2012
Could you please provide a link to that errata? I still cannot find
it... but from your explanation, that design decision sounds pretty
horrible. Why didn't they just choose not to se
> From: Sarah Sharp [mailto:sarah.a.sh...@linux.intel.com]
> Sent: Thursday, August 29, 2013 10:42 AM
>
> On Wed, Aug 28, 2013 at 10:15:34PM +, Paul Zimmerman wrote:
> > > From: Sarah Sharp [mailto:sarah.a.sh...@linux.intel.com]
> > > Sent: Wednesday, August 28, 2013 2:52 PM
> > >
> > > On Mon
On 08/29/2013 08:53 PM, Greg KH wrote:
On Thu, Aug 29, 2013 at 08:37:57PM +0300, Xenia Ragiadakou wrote:
In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
descriptor to hold the value read by the device. The new bos descriptor
has to be compared with the old one in order to f
On Thu, Aug 29, 2013 at 10:06:16AM -0700, Greg Kroah-Hartman wrote:
> Hi Sarah,
>
> I'm getting the following warnings from the 3.10.9 kernel all the time
> when I unplug a USB 3 storage device from my laptop:
> [203282.987687] usb 4-1: USB disconnect, device number 21
> [203282.992904
On Thu, Aug 29, 2013 at 10:53:13AM -0700, Greg KH wrote:
> On Thu, Aug 29, 2013 at 08:37:57PM +0300, Xenia Ragiadakou wrote:
> > In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
> > descriptor to hold the value read by the device. The new bos descriptor
> > has to be compared w
On Thu, Aug 29, 2013 at 09:16:56PM +0300, Xenia Ragiadakou wrote:
> On 08/29/2013 08:53 PM, Greg KH wrote:
> > On Thu, Aug 29, 2013 at 08:37:57PM +0300, Xenia Ragiadakou wrote:
> >> In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
> >> descriptor to hold the value read by the d
On Thu, Aug 29, 2013 at 11:18:21AM -0700, Sarah Sharp wrote:
> On Thu, Aug 29, 2013 at 10:06:16AM -0700, Greg Kroah-Hartman wrote:
> > Hi Sarah,
> >
> > I'm getting the following warnings from the 3.10.9 kernel all the time
> > when I unplug a USB 3 storage device from my laptop:
> > [203282.9
Hi Giovanni,
Mathias mentioned that this patch might fix your issue:
http://marc.info/?l=linux-usb&m=136269803207465&w=2
Can you please compile a custom 3.10 stable kernel with that patch
applied and see if it fixes your issue?
Sarah Sharp
On Wed, Aug 28, 2013 at 09:46:42PM -0700, Giovanni wro
On Thu, Aug 29, 2013 at 11:22:46AM -0700, Sarah Sharp wrote:
> On Thu, Aug 29, 2013 at 10:53:13AM -0700, Greg KH wrote:
> > On Thu, Aug 29, 2013 at 08:37:57PM +0300, Xenia Ragiadakou wrote:
> > > In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
> > > descriptor to hold the valu
Alan Stern wrote:
> On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
>
>>> Since this device is 4-2, the parent hub is usb4.
>>
>> Actually, even if that would be a another USB HUB and not a PCI device (root
>> hub),
>> I would be happy if it extracted something like:
>>
>> Bus 004 Device 006: ID 210
On Thu, 29 Aug 2013, Udo van den Heuvel wrote:
> On 2013-08-28 21:37, Alan Stern wrote:
> >>> No, if you unload the ohci-hcd driver then the webcam won't be used.
> >>> Are you certain that merely stopping the daemon program will prevent
> >>> the problem?
> >>
> >> Quite certain but retesting
> From: jwer...@google.com [mailto:jwer...@google.com] On Behalf Of Julius
> Werner
> Sent: Thursday, August 29, 2013 11:07 AM
>
> > If you take a look at Table
> > 13: BESL/HIRD Encoding from the xHCI spec version including errata to
> > 08/14/2012
>
> Could you please provide a link to that er
Xenia Ragiadakou wrote:
> On 08/29/2013 04:31 PM, Martin MOKREJŠ wrote:
>> Actually, there is some new bug I haven't seen before (this is 3.10.9
>> kernel).
>> First of all, I see my TI XHCI controller does not use MSI-X anymore, will
>> have
>> to check my .config why is it so.
>> Second, it sho
On Thu, 29 Aug 2013, James Stone wrote:
> At 32 frames/period (reported round-trip latency 1.33ms), it starts up
> but there are too many xruns for it to be usable.
Interesting. Can you try doing the same thing with just playback, no
recording? If that still gets underruns, please collect a us
In usb_reset_and_verify_device(), hub_port_init() allocates a new bos
descriptor to hold the value read by the device. The new bos descriptor
has to be compared with the old one in order to figure out if device 's
firmware has changed in which case the device has to be reenumerated.
In the original
On Thu, Aug 29, 2013 at 08:36:51PM +0200, Martin MOKREJŠ wrote:
>
>
> Alan Stern wrote:
> > On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> >
> >>> Since this device is 4-2, the parent hub is usb4.
> >>
> >> Actually, even if that would be a another USB HUB and not a PCI device
> >> (root hub),
>
On Thu, 29 Aug 2013, Sarah Sharp wrote:
> On Thu, Aug 29, 2013 at 10:06:16AM -0700, Greg Kroah-Hartman wrote:
> > Hi Sarah,
> >
> > I'm getting the following warnings from the 3.10.9 kernel all the time
> > when I unplug a USB 3 storage device from my laptop:
> > [203282.987687] usb 4-1: USB
On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> > This really is asking too much of the kernel. That's why we have
> > userspace utilities like lsusb.
> >
> > For example, it wouldn't be hard to write a shell script that would
> > take a device name like "4-2" and print out the information you wan
On 08/29/2013 05:48 AM, George Cherian wrote:
> On 8/29/2013 4:07 PM, Chanwoo Choi wrote:
...
>> I tested various development board based on Samsung Exynos series SoC.
>> Although some gpio of Exynos series SoC set high state(non zero, 1) as
>> default value,
>> this gpio state could mean off state
On 08/28/2013 11:33 AM, George Cherian wrote:
> Add a generic USB VBUS/ID detection EXTCON driver. This driver expects
> the ID/VBUS pin are connected via GPIOs. This driver is tested on
> DRA7x board were the ID pin is routed via GPIOs. The driver supports
> both VBUS and ID pin configuration and
On 08/28/2013 11:33 AM, George Cherian wrote:
> Add
> -extcon nodes for USB ID pin detection.
> -i2c nodes.
> -pcf nodes to which USB ID pin is connected.
> diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
> &dwc3_1 {
> - dr_mode = "otg";
> +
On Thu, Aug 29, 2013 at 02:58:25PM -0400, Alan Stern wrote:
> On Thu, 29 Aug 2013, Sarah Sharp wrote:
>
> > On Thu, Aug 29, 2013 at 10:06:16AM -0700, Greg Kroah-Hartman wrote:
> > > Hi Sarah,
> > >
> > > I'm getting the following warnings from the 3.10.9 kernel all the time
> > > when I unplug a
On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
> > This really isn't necessary. All the information you want is already
> > in the system log. It's merely a matter of locating it.
> >
> > I can show you how. If you post a complete dmesg log, starting from
> > boot and running up to one of these
Hi Sarah,
thank you for your patch, but not fix my issue. I attached new kernel oops log
into bugzilla.
https://bugzilla.kernel.org/attachment.cgi?id=107363
Regards,
Giovanni
On Thu, 8/29/13, Sarah Sharp wrote:
Subject: Re: Bug 60810 - Kernel oops
On 08/29/2013 11:32 PM, Alan Stern wrote:
On Thu, 29 Aug 2013, Martin MOKREJŠ wrote:
[snip]
I understand your point but don't think this is the case. OK, please show me why
is LPM not available. If USB is complaining about that being disabled it could
tell me based on what attribute at least. A
- use all columns
- the driver uses both 'netdev' and 'net'. Let's use 'netdev' ('net' is
shorter but it tastes of network namespaces)
- don't dereference dev->net when there is a local netdev at hand
- use some existing #define (please check those)
- skb_set_tail_pointer to avoid compiler cast w
Keep it small though literate.
---
drivers/net/usb/sr9700.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/drivers/net/usb/sr9700.c b/drivers/net/usb/sr9700.c
index f7f46e6..3f05b35 100644
--- a/drivers/net/usb/sr9700.c
+++ b/drivers/net/usb/s
Liu, please check those.
---
drivers/net/usb/sr9700.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/net/usb/sr9700.c b/drivers/net/usb/sr9700.c
index 3f05b35..3ae3caf 100644
--- a/drivers/net/usb/sr9700.c
+++ b/drivers/net/usb/sr9700.c
@@ -99,8 +99,9 @@ static i
On Wed, Aug 28, 2013 at 01:28:08PM -0700, H. Peter Anvin wrote:
> On 08/28/2013 12:16 PM, Alan Stern wrote:
> > Russell, Peter, and Ingo:
> >
> > Can you folks enlighten us regarding this issue for some common
> > architectures?
>
> On x86, IRET is a serializing instruction; it guarantees hard
>
When an error occurs adding a udc platform device there is a risk of an
infinite loop.
If more than one platform device was added i will remain >= than 0. The
intention seems
to clean up all the different already added platform devices before the failure
occurs,
so fixed the code to actually do
These two patches fix some minor issues in the dummy_hcd driver. Both
errors were detected with the help of coverity analysis.
These patches have been updated based on Alan Sterns comments.
For the first patch I have harmonized both occurences of the different
clean-up routine as suggested.
The
Since USB_SS_PORT_LS_U0 is 0x the & operation with the port state would
always be 0. Thus the if would never be true. Moreover USB_PORT_STAT_ENABLE
is 0x0002 and as such would never equal to 1. What we actually look for is a
port that is in U0/link active state.
Thanks to Alan Stern for sugges
Hi George,
On 08/29/2013 10:45 PM, George Cherian wrote:
> Hi Chanwoo,
>
>
> On 8/29/2013 5:42 PM, Chanwoo Choi wrote:
> [big snip ]
I tested various development board based on Samsung Exynos series SoC.
Although some gpio of Exynos series SoC set high state(non zero, 1) as
defau
On Thu, 2013-08-29 at 16:51 -0700, Paul E. McKenney wrote:
> On Wed, Aug 28, 2013 at 01:28:08PM -0700, H. Peter Anvin wrote:
> > On 08/28/2013 12:16 PM, Alan Stern wrote:
> > > Russell, Peter, and Ingo:
> > >
> > > Can you folks enlighten us regarding this issue for some common
> > > architecture
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with &of->dev,
so we can directly pass a struct platform_device.
Signed-off-by: Libo Chen
---
drivers/usb/phy/phy-tegra-usb.c |2 +-
1 files changed, 1 insertions
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with &of->dev,
so we can directly pass a struct platform_device.
Signed-off-by: Libo Chen
---
drivers/usb/host/r8a66597-hcd.c |4 ++--
1 files changed, 2 insertio
On 08/29/2013 04:51 PM, Paul E. McKenney wrote:
> On Wed, Aug 28, 2013 at 01:28:08PM -0700, H. Peter Anvin wrote:
>> On 08/28/2013 12:16 PM, Alan Stern wrote:
>>> Russell, Peter, and Ingo:
>>>
>>> Can you folks enlighten us regarding this issue for some common
>>> architectures?
>>
>> On x86, IRET
On Fri, 2013-08-30 at 01:06 +0200, Francois Romieu wrote:
just trivia:
> diff --git a/drivers/net/usb/sr9700.c b/drivers/net/usb/sr9700.c
[]
> @@ -288,19 +291,19 @@ static void sr9700_set_multicast(struct net_device *net)
[]
> +static int sr9700_set_mac_address(struct net_device *netdev, void *p)
Hi Chanwoo,
On 8/30/2013 5:41 AM, Chanwoo Choi wrote:
Hi George,
On 08/29/2013 10:45 PM, George Cherian wrote:
Hi Chanwoo,
On 8/29/2013 5:42 PM, Chanwoo Choi wrote:
[big snip ]
I tested various development board based on Samsung Exynos series SoC.
Although some gpio of Exynos series SoC set
Hi George,
On 08/30/2013 03:15 PM, George Cherian wrote:
> Hi Chanwoo,
>
> On 8/30/2013 5:41 AM, Chanwoo Choi wrote:
>> Hi George,
>>
>> On 08/29/2013 10:45 PM, George Cherian wrote:
>>> Hi Chanwoo,
>>>
>>>
>>> On 8/29/2013 5:42 PM, Chanwoo Choi wrote:
>>> [big snip ]
>> I tested various deve
93 matches
Mail list logo
