Hi,
On Sat, Sep 22, 2012 at 2:08 PM, Venu Byravarasu vbyravar...@nvidia.com wrote:
-Original Message-
From: Stephen Warren [mailto:swar...@wwwdotorg.org]
Sent: Friday, September 21, 2012 9:45 PM
To: ABRAHAM, KISHON VIJAY
Cc: Venu Byravarasu; ba...@ti.com; gre...@linuxfoundation.org;
-Original Message-
From: ABRAHAM, KISHON VIJAY [mailto:kis...@ti.com]
Sent: Monday, September 24, 2012 11:48 AM
To: Venu Byravarasu
Cc: Stephen Warren; ba...@ti.com; gre...@linuxfoundation.org; linux-
ker...@vger.kernel.org; linux-usb@vger.kernel.org
Subject: Re: [PATCH v3] USB:
On 9/23/2012 8:33 PM, Rafael J. Wysocki wrote:
On Sunday, September 23, 2012, Peter Stuge wrote:
Rafael J. Wysocki wrote:
Well, we actually need to handle power domains appropriately.
..
Some work in that direction has been done in the ARM space, where we have
much more direct access to
On 9/24/2012 12:13 AM, Alan Stern wrote:
Therefore all we need is an API for individual devices, not for
domains. Of course, userspace may want to know which devices all
belong to the same power domain.
agreed on both.
I'd like PowerTOP to be able to report at least who keeps power alive and
On Sat, Sep 22, 2012 at 3:37 AM, Samuel Ortiz sa...@linux.intel.com wrote:
Hi Paul,
On Wed, Sep 19, 2012 at 08:39:40PM +, Paul Walmsley wrote:
Hi Samuel,
I've queued patch 1 of this series for 3.7, which should go upstream via
the OMAP - arm-soc path. Also asked Keshava to re-send
+Required properties:
+- compatible: must be marvell,orion-ehci
+- reg: physical base address of the controller and length of memory mapped
+ region.
+- interrupts: The EHCI interrupt
+- phy-version: Can be one of:
+ NA - Don't touch the phy, something else has already configured
On 09/23/2012 10:56 PM, Joachim Eastwood :
Fixes the following NULL pointer dereference:
[7.74] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[7.81] Unable to handle kernel NULL pointer dereference at virtual
address 0028
[7.81] pgd = c3a38000
[
Hi,
On Sat, Sep 22, 2012 at 3:03 AM, Rabin Vincent ra...@rab.in wrote:
2012/9/6 Kishon Vijay Abraham I kis...@ti.com:
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is
2012/9/24 ABRAHAM, KISHON VIJAY kis...@ti.com:
On Sat, Sep 22, 2012 at 3:03 AM, Rabin Vincent ra...@rab.in wrote:
USB doesn't work on pandaboard on linux-next, and bisection shows this
patch. Unfortunately, I can't provide a dmesg log because USB is the
only way I currently have to get one
Hi Kishon, Felipe,
Any further comments on these patches? Can they be merged now?
Thanks,
Praveen
On Mon, Sep 17, 2012 at 6:24 PM, Praveen Paneri p.pan...@samsung.com wrote:
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to
Hi,
On Mon, Sep 24, 2012 at 3:08 PM, Praveen Paneri p.pan...@samsung.com wrote:
Hi Kishon, Felipe,
Any further comments on these patches? Can they be merged now?
I don't have any other comments.
Thanks
Kishon
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
On 9/17/12, Praveen Paneri p.pan...@samsung.com wrote:
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable phy. Tested with
smdk6410 and smdkv310. More SoCs can be
Hi,
Maybe this is a better solution, especially considering aversion to do
this by the module parameters.
Or maybe it is better to give support for I2C, SPI to ftdi_sio module and
use sysfs to switch betwen uart/ic2c/spi ...
If can do this on interface basis per-device it looks
-Original Message-
From: Oliver Neukum [mailto:oneu...@suse.de]
Sent: Friday, September 21, 2012 10:35 AM
To: Alexey ORISHKO; bj...@mork.no; net...@vger.kernel.org; linux-
u...@vger.kernel.org
Subject: removing the timer from cdc-ncm
Hi,
here is the patch that does everything I
On Monday 24 September 2012 14:13:50 Alexey ORISHKO wrote:
I've tried to apply it, but always got a message that patch does not apply.
What is the base for this patch?
Greg KH's tree, specifically commit 6dab7ede9390d4d937cb89feca932e4fd575d2da
HTH
Oliver
--
To
Hi,
On Mon, Sep 24, 2012 at 02:53:24PM +0300, philippedesw...@gmail.com wrote:
From: Philippe De Swert philippe.desw...@jollamobile.com
Unless generic_interrupt is defined the irq setup
in musb_init_controller fails for the omap2430 driver
since that one does not set it's own interrupt
On Mon, Sep 24, 2012 at 03:15:39PM +0300, Felipe Balbi wrote:
Hi,
On Mon, Sep 24, 2012 at 02:53:24PM +0300, philippedesw...@gmail.com wrote:
From: Philippe De Swert philippe.desw...@jollamobile.com
Unless generic_interrupt is defined the irq setup
in musb_init_controller fails for the
On Monday, September 24, 2012, Arjan van de Ven wrote:
On 9/23/2012 8:33 PM, Rafael J. Wysocki wrote:
On Sunday, September 23, 2012, Peter Stuge wrote:
Rafael J. Wysocki wrote:
Well, we actually need to handle power domains appropriately.
..
Some work in that direction has been done in
On Monday, September 24, 2012, Arjan van de Ven wrote:
On 9/24/2012 12:13 AM, Alan Stern wrote:
Therefore all we need is an API for individual devices, not for
domains. Of course, userspace may want to know which devices all
belong to the same power domain.
agreed on both.
I'd like
On 09/17/2012 07:54 AM, Praveen Paneri wrote:
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable phy. Tested with
smdk6410 and smdkv310. More SoCs can be brought under later.
Signed-off-by: Praveen Paneri
Hi,
On Mon, Sep 24, 2012 at 03:54:22PM +0300, Philippe De Swert wrote:
Hi,
On 24/09/2012, Felipe Balbi ba...@ti.com wrote:
SoB's mail doesn't From mail.
Well still in the progress of migrating of my personal to work laptop.
Since the patch does not seem correct the replacement will have
On Saturday, September 22, 2012, Rafael J. Wysocki wrote:
On Friday, September 21, 2012, Sarah Sharp wrote:
Two weeks ago at Linux Plumbers Conference, I presented about the Intel
Lynx Point USB port power off mechanism. This email is a report out of
what was discussed, and a kick off
On 09/06/2012 09:57 AM, Kishon Vijay Abraham I wrote:
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver
Hi Alan,
On Sat, Sep 15, 2012 at 11:03:39AM -0400, Alan Stern wrote:
On Sat, 15 Sep 2012, Matthijs Kooijman wrote:
Hi folks,
I've spent some time this week trying to debug frequent hiccups in my
audio playback, on my USB sound card. The short version is that it seems
the 24 ms worth
On 2012/9/24 21:18, Rafael J. Wysocki wrote:
On Saturday, September 22, 2012, Rafael J. Wysocki wrote:
On Friday, September 21, 2012, Sarah Sharp wrote:
Two weeks ago at Linux Plumbers Conference, I presented about the Intel
Lynx Point USB port power off mechanism. This email is a report out
Hi,
On 09/20/2012 11:42 PM, Pete Batard wrote:
Hi,
It with pleasure that I would like to announce the release of libusbx
1.0.13. This version brings the following notable changes:
The Fedora packages for libusbx have been upgraded to 1.0.13 now.
Regards,
Hans
--
To unsubscribe from this
On Mon, Sep 24, 2012 at 12:09 AM, Alan Stern st...@rowland.harvard.edu wrote:
No, you can still handle the other case. You need to report the
condition to the PM core, say by calling pm_wakeup_event().
Good point, so kind of below code should be added to usb_suspend_both
to handle the
On Sun, 23 Sep 2012, Oliver Neukum wrote:
On Sunday 23 September 2012 12:23:40 Alan Stern wrote:
It turns out that the USB-2 spec does not take into account the
The race _was_ recognized in one of the errata documents published
after the USB-2.0 spec came out. The solution recommended in
PHY_CLK_VALID bit doesn't work properly with UTMI PHY.
e.g. This bit is always zero on P5040, etc.
There is no need to check this bit for UTMI PHY, just keep
checking for ULPI PHY to prevent system hanging.
This patch should be squashed into previous commit 3735ba8db8e6e
powerpc/usb: fix bug of
-Original Message-
From: Greg KH [mailto:g...@kroah.com]
Sent: 2012年9月22日 22:49
To: Kumar Gala
Cc: Liu Shengzhou-B36685; linuxppc-...@lists.ozlabs.org; linux-
u...@vger.kernel.org
Subject: Re: [PATCH v3] powerpc/usb: fix bug of CPU hang when missing
USB PHY clock
On Sat, Sep
On Thu, Sep 20, 2012 at 10:42:10PM +0100, Pete Batard wrote:
Hi,
It with pleasure that I would like to announce the release of
libusbx 1.0.13. This version brings the following notable changes:
* [MAJOR] Fix a typo in the API with struct libusb_config_descriptor
where MaxPower was used
On Mon, Sep 24, 2012 at 03:52:55PM +0200, Hans de Goede wrote:
Hi,
On 09/20/2012 11:42 PM, Pete Batard wrote:
Hi,
It with pleasure that I would like to announce the release of libusbx
1.0.13. This version brings the following notable changes:
The Fedora packages for libusbx have been
On Mon, 24 Sep 2012, Ming Lei wrote:
On Mon, Sep 24, 2012 at 12:51 AM, Alan Stern st...@rowland.harvard.edu
wrote:
On Sun, 23 Sep 2012, Ming Lei wrote:
In fact, sometimes new connected device _does_ mean there will be
another new connection in the next few seconds. This happens
You should use Reply-To-All so that your messages get sent to the
mailing list as well as to me.
On Sun, 23 Sep 2012, Adrian Sandu wrote:
Thanks for the fast response in the 1st place :)
Which computer is the nettop and which is the laptop?
The nettop is an asrock 152d
You should use Reply-To-All so that your messages get sent to the
mailing list as well as to me.
Will do from now on :)
In the new file you wrote: launch cat of 9u, start copying a file to
/dev/sdb1 ( using mc for example ). Where was this file stored? Was
it on /dev/sdd1?
My reason
* Felipe Balbi ba...@ti.com [120924 06:08]:
Hi,
On Mon, Sep 24, 2012 at 03:54:22PM +0300, Philippe De Swert wrote:
Hi,
On 24/09/2012, Felipe Balbi ba...@ti.com wrote:
SoB's mail doesn't From mail.
Well still in the progress of migrating of my personal to work laptop.
Since the
On Mon, Sep 24, 2012 at 11:07 PM, Alan Stern st...@rowland.harvard.edu wrote:
It doesn't matter. Here's the scenario:
New device is plugged in.
The hub wakes up.
The hub driver tries to initialize the new device and fails.
The device disconnects itself from
On Mon, 24 Sep 2012, Ming Lei wrote:
On Mon, Sep 24, 2012 at 12:09 AM, Alan Stern st...@rowland.harvard.edu
wrote:
No, you can still handle the other case. You need to report the
condition to the PM core, say by calling pm_wakeup_event().
Good point, so kind of below code should be
On Mon, 17 Sep 2012, Alan Stern wrote:
On Mon, 17 Sep 2012, Don Zickus wrote:
I have added some in-depth analysis from our customer.
The problem is that the failing routine was called with a pointer to usbdev
in
memory that has already been freed and overwritten with the pool
On Tue, 25 Sep 2012, Ming Lei wrote:
IMO, it should be reasonable to set the device's autosuspend delay
as zero when its driver is unbound because no one can predict when
the device will be bound to a new driver.
It could be set to a low value, but it shouldn't be set to 0. There
aren't too
On Mon, Sep 24, 2012 at 12:59:51PM -0400, Alan Stern wrote:
On Mon, 17 Sep 2012, Alan Stern wrote:
On Mon, 17 Sep 2012, Don Zickus wrote:
I have added some in-depth analysis from our customer.
The problem is that the failing routine was called with a pointer to
usbdev in
On Thu, Sep 20, 2012 at 4:30 PM, Bjørn Mork bj...@mork.no wrote:
Ming Lei ming@canonical.com writes:
On Mon, Sep 17, 2012 at 4:04 PM, Oliver Neukum oneu...@suse.de wrote:
1) Does it actually save power? You are constantly waking up a CPU.
Of course, it does. I don't know it will save how
Hi,
Ajay, which host controller are you seeing the disconnect lags on? Can you
send me the output of `sudo lspci -vvv -n`?
I was on leave last week so will get the data at earliest.
Ajay
Sarah Sharp
--
To unsubscribe from this list: send the line unsubscribe linux-usb in the
body of a
On Tue, Sep 25, 2012 at 1:06 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 25 Sep 2012, Ming Lei wrote:
IMO, it should be reasonable to set the device's autosuspend delay
as zero when its driver is unbound because no one can predict when
the device will be bound to a new driver.
On Mon, Sep 24, 2012 at 07:59:40PM +0300, Kustaa Nyholm wrote:
On 24.9.2012 18.03, Greg KH gre...@linuxfoundation.org wrote:
libusbx as it's developers really don't care about their users.
A bit richt, I think, to say that libusbx developers do not care
about their users.
I don't think so.
On Mon, Sep 24, 2012 at 02:44:19PM +, Liu Shengzhou-B36685 wrote:
-Original Message-
From: Greg KH [mailto:g...@kroah.com]
Sent: 2012年9月22日 22:49
To: Kumar Gala
Cc: Liu Shengzhou-B36685; linuxppc-...@lists.ozlabs.org; linux-
u...@vger.kernel.org
Subject: Re: [PATCH v3]
On 24.9.2012 18.03, Greg KH gre...@linuxfoundation.org wrote:
libusbx as it's developers really don't care about their users.
A bit richt, I think, to say that libusbx developers do not care
about their users.
To be constructive can you name the broken programs (in addition
to the already
On Mon, Sep 24, 2012 at 09:44:31AM +0200, Nicolas Ferre wrote:
This patches fixed the issue by adding the gpio valid check.
Signed-off-by: Joachim Eastwood joachim.eastw...@jotron.com
Acked-by: Nicolas Ferre nicolas.fe...@atmel.com
Thanks a *lot* Joachim for having chased this bug!
On Mon, Sep 24, 2012 at 03:18:19PM +0200, Rafael J. Wysocki wrote:
On Saturday, September 22, 2012, Rafael J. Wysocki wrote:
On Friday, September 21, 2012, Sarah Sharp wrote:
Two weeks ago at Linux Plumbers Conference, I presented about the Intel
Lynx Point USB port power off mechanism.
On Mon, Sep 24, 2012 at 06:34:51PM +0300, Adrian Sandu wrote:
You should use Reply-To-All so that your messages get sent to the
mailing list as well as to me.
Will do from now on :)
In the new file you wrote: launch cat of 9u, start copying a file to
/dev/sdb1 ( using mc for example
I'll whip up some patches that allow you to disable USB 3.0 Link PM for
the VIA hub and we'll see if that helps. Or you could downgrade to the
3.4 kernel and see if that helps, since USB 3.0 Link PM went into 3.5.
Thanks Sarah. I tried in 3.4.11 to .. about the same thing ..
Hi,
On 09/24/2012 05:03 PM, Greg KH wrote:
On Thu, Sep 20, 2012 at 10:42:10PM +0100, Pete Batard wrote:
Hi,
It with pleasure that I would like to announce the release of
libusbx 1.0.13. This version brings the following notable changes:
* [MAJOR] Fix a typo in the API with struct
On 2012.09.24 18:24, Greg KH wrote:
I don't think so. Remember, usbutils is the _one_ libusb package that
everyone has on their system. The fact that the libusbx release wasn't
tested with that package makes me wonder how it was tested at all.
Greg,
We made the conscious decision to
Hi Greg,
On 09/24/2012 05:07 PM, Greg KH wrote:
On Mon, Sep 24, 2012 at 03:52:55PM +0200, Hans de Goede wrote:
Hi,
On 09/20/2012 11:42 PM, Pete Batard wrote:
Hi,
It with pleasure that I would like to announce the release of libusbx
1.0.13. This version brings the following notable changes:
Hi,
Is there anything else I could do to help figure this out?
Perhaps usbmon on some specific transactions or something?
Thanks,
Matthew.
On Wed, Aug 08, 2012 at 02:03:14PM -0700, Sarah Sharp wrote:
Hi Matthew,
This patch does fix the error that Gary reported. And even though it
On Mon, Sep 24, 2012 at 07:33:08PM +0100, Pete Batard wrote:
But the problem really is that libusb (and libusbx prior to v1.0.13)
has a typo that makes it deviate from the USB specs, which left
uswith 3 choices:
1. leave the typo as is, and say It's fine to deviate from the USB
specs for
On Mon, Sep 24, 2012 at 08:36:11PM +0200, Hans de Goede wrote:
Hi Greg,
On 09/24/2012 05:07 PM, Greg KH wrote:
On Mon, Sep 24, 2012 at 03:52:55PM +0200, Hans de Goede wrote:
Hi,
On 09/20/2012 11:42 PM, Pete Batard wrote:
Hi,
It with pleasure that I would like to announce the release
On 2012.09.24 19:50, Greg KH wrote:
Please fix this in libusbx, or bump the .so name so that tools can
properly know that the API has changed, and that they want to build
against the old one.
Well, if you leave us no other alternative, then I guess my vote will be
for option 2, especially as
On 24.9.2012 21.47, Greg KH g...@kroah.com wrote:
And if I'm going to be forced to change my program, and libusbx has now
shown that they don't care about their public api, well, I might as well
just rewrite it to remove that dependancy completly, as it's obvious
they don't know how to treat
On Mon, 24 Sep 2012 11:47:27 -0700, Greg KH said:
No, you are forcing me to change my program to have it build with your
change, you should do it the other way around. If you want programs to
use your library, make it so that they don't have to be changed at all.
And if I'm going to be forced
On Tue, 25 Sep 2012, Ming Lei wrote:
On Tue, Sep 25, 2012 at 1:06 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 25 Sep 2012, Ming Lei wrote:
IMO, it should be reasonable to set the device's autosuspend delay
as zero when its driver is unbound because no one can predict when
On Mon, Sep 24, 2012 at 03:20:10PM -0400, Sean McBride wrote:
On Mon, 24 Sep 2012 11:47:27 -0700, Greg KH said:
No, you are forcing me to change my program to have it build with your
change, you should do it the other way around. If you want programs to
use your library, make it so that
On Mon, Sep 24, 2012 at 09:12:56PM +0200, Hans de Goede wrote:
Hi,
On 09/24/2012 08:50 PM, Greg KH wrote:
On Mon, Sep 24, 2012 at 08:36:11PM +0200, Hans de Goede wrote:
Hi Greg,
On 09/24/2012 05:07 PM, Greg KH wrote:
On Mon, Sep 24, 2012 at 03:52:55PM +0200, Hans de Goede wrote:
Hi,
On Mon, Sep 24, 2012 at 10:16:25PM +0300, Kustaa Nyholm wrote:
On 24.9.2012 21.47, Greg KH g...@kroah.com wrote:
And if I'm going to be forced to change my program, and libusbx has now
shown that they don't care about their public api, well, I might as well
just rewrite it to remove that
On Tue, 25 Sep 2012, Ming Lei wrote:
On Tue, Sep 25, 2012 at 12:42 AM, Alan Stern st...@rowland.harvard.edu
wrote:
On Mon, 24 Sep 2012, Ming Lei wrote:
On Mon, Sep 24, 2012 at 12:09 AM, Alan Stern st...@rowland.harvard.edu
wrote:
No, you can still handle the other case. You need
On 2012.09.24 20:31, Greg KH wrote:
No one delivered any such fix, all I got was a bunch of bug reports
this morning from the distros saying that usbutils was suddenly broken.
That shows that libusbx is really the problem here, and that maybe I
shouldn't depend on it anymore.
Could you please
On Mon, Sep 24, 2012 at 08:35:07PM +0100, Pete Batard wrote:
On 2012.09.24 20:31, Greg KH wrote:
No one delivered any such fix, all I got was a bunch of bug reports
this morning from the distros saying that usbutils was suddenly broken.
That shows that libusbx is really the problem here, and
On 24.9.2012 22.31, Greg KH g...@kroah.com wrote:
Um, breaking existing applications is not indicative of that, don't you
agree?
You never make bad calls and you think this was a deliberate
attempt not to care for users? If you think it is a bug and a bad
choice, why not say it, instead of
On Mon, 24 Sep 2012, Sarah Sharp wrote:
When a device with an isochronous endpoint is behind a hub plugged into
the Intel Panther Point xHCI host controller, and the driver submits
multiple frames per URB, the xHCI driver will set the Block Event
Interrupt (BEI) flag on all but the last TD
Hi everybody,
I'd like to share one unrelated thing: I AM NOT subscribed to the libusbx
related mailing lists and I AM NOT using it in my current development.
I do appreciate the effort of all libusbx developers and I support them in
their decisions. I hope once I will contribute something to
On Mon, Sep 24, 2012 at 03:50:04PM -0400, Alan Stern wrote:
On Mon, 24 Sep 2012, Sarah Sharp wrote:
When a device with an isochronous endpoint is behind a hub plugged into
the Intel Panther Point xHCI host controller, and the driver submits
multiple frames per URB, the xHCI driver will
On Mon, Sep 24, 2012 at 10:46:30AM -0700, Greg KH wrote:
On Mon, Sep 24, 2012 at 03:18:19PM +0200, Rafael J. Wysocki wrote:
On Saturday, September 22, 2012, Rafael J. Wysocki wrote:
On Friday, September 21, 2012, Sarah Sharp wrote:
Two weeks ago at Linux Plumbers Conference, I presented
On Monday, September 24, 2012, Greg KH wrote:
On Mon, Sep 24, 2012 at 10:46:30AM -0700, Greg KH wrote:
On Mon, Sep 24, 2012 at 03:18:19PM +0200, Rafael J. Wysocki wrote:
On Saturday, September 22, 2012, Rafael J. Wysocki wrote:
On Friday, September 21, 2012, Sarah Sharp wrote:
Two
On Mon, Sep 24, 2012 at 09:13:42PM +0300, Adrian Sandu wrote:
I'll whip up some patches that allow you to disable USB 3.0 Link PM for
the VIA hub and we'll see if that helps. Or you could downgrade to the
3.4 kernel and see if that helps, since USB 3.0 Link PM went into 3.5.
Thanks
On Monday, September 24, 2012, Lan Tianyu wrote:
On 2012/9/24 21:18, Rafael J. Wysocki wrote:
On Saturday, September 22, 2012, Rafael J. Wysocki wrote:
On Friday, September 21, 2012, Sarah Sharp wrote:
Two weeks ago at Linux Plumbers Conference, I presented about the Intel
Lynx Point USB
Agreed. Please move this to the libusbx mailing list. I couldn't care less
about libusbx after the hid fiasco.
-Nathan
On Sep 24, 2012, at 9:42 PM, Jure Menart jure.men...@espros.ch wrote:
Hi everybody,
I'd like to share one unrelated thing: I AM NOT subscribed to the libusbx
related
Dear Sarah,
We noticed a couple of problems with the Linux xHCI driver:
1. There is a problem with URB cancellation for USB 2.0 device on USB
3.0 host. When we disable our device, we cancel all pending URBs by
calling ioctl with the request code of USBDEVFS_DISCARDURB. When we
re-enable our
Ok, so 3.4.11 doesn't work, and the log file was from 3.5.
If it's not LPM, I'm really out of ideas. I would suggest getting
another USB 3.0 hub, but I know that basically the VIA chipset is the
one out there, so that wouldn't be likely to help.
You might go see if your USB 3.0 hub has a
On 12/31/1969 05:00 PM, wrote:
usbhid's hid_post_reset checks the report descriptor currently
returned by the
device against a descriptor that may have been modified by a driver's
report_fixup method. That leaves some devices nonfunctional after a
resume, with
a reset_resume error 1 reported.
On Monday, September 24, 2012, Alan Stern wrote:
On Mon, 24 Sep 2012, Rafael J. Wysocki wrote:
I don't mean this.
Suppose that there are two ports on the hub, A and B, and there's only one
power resource used to put A _and_ B into D3cold. Then, when you call
acpi_bus_set_power(A,
On Mon, Sep 24, 2012 at 02:38:05PM -0700, Yuliya T wrote:
Dear Sarah,
We noticed a couple of problems with the Linux xHCI driver:
1. There is a problem with URB cancellation for USB 2.0 device on USB
3.0 host. When we disable our device, we cancel all pending URBs by
calling ioctl with the
On Tue, Sep 25, 2012 at 12:09:06AM +0200, Rafael J. Wysocki wrote:
On Monday, September 24, 2012, Alan Stern wrote:
On Mon, 24 Sep 2012, Rafael J. Wysocki wrote:
Second, I'm not sure if there's any way for user space to figure out
what
ports are connected to what sockets visible
On Mon, Sep 24, 2012 at 01:05:08PM -0700, Sarah Sharp wrote:
On Mon, Sep 24, 2012 at 03:50:04PM -0400, Alan Stern wrote:
On Mon, 24 Sep 2012, Sarah Sharp wrote:
When a device with an isochronous endpoint is behind a hub plugged into
the Intel Panther Point xHCI host controller, and the
ERROR: ezusb_fx1_ihex_firmware_download
[drivers/usb/serial/whiteheat.ko] undefined!
ERROR: ezusb_fx1_ihex_firmware_download
[drivers/usb/serial/keyspan_pda.ko] undefined!
ERROR: ezusb_fx1_set_reset [drivers/usb/serial/keyspan_pda.ko]
undefined!
ERROR: ezusb_fx1_ihex_firmware_download
On Mon, Sep 24, 2012 at 12:23 AM, Alan Stern st...@rowland.harvard.edu wrote:
It turns out that the USB-2 spec does not take into account the
possibility of the race between a hub being suspended and one of its
ports receiving a remote wakeup request from downstream. The
flowcharts and
On Tue, Sep 25, 2012 at 3:34 AM, Alan Stern st...@rowland.harvard.edu wrote:
Do we really need to? Remember, you are adding this new code only
because some Genesys Logic hubs are buggy. Is there any reason to
think other devices will have similar bugs?
Hub is a bit special because the event
On Tue, Sep 25, 2012 at 3:26 AM, Alan Stern st...@rowland.harvard.edu wrote:
By how much? That is, how many times is an unbound USB device going to
be autosuspended?
I mean if we can remove the timer for the unbound devices, why not do it
to decrease wakeup counts for CPU?
In fact, the CPU
87 matches
Mail list logo
