On Saturday, July 28, 2012, Alan Stern wrote:
On Sat, 28 Jul 2012, Rafael J. Wysocki wrote:
On Saturday, July 28, 2012, Alan Stern wrote:
On Fri, 27 Jul 2012, Rafael J. Wysocki wrote:
+ if (parent)
+ pm_runtime_put(parent);
You should
On Sun, 29 Jul 2012, Rafael J. Wysocki wrote:
The difference is, if you use _put_sync(), you need to wait the extra 10 ms
for local_pci_probe() to return (if the parent is actually suspended),
although you might not need to wait for it if you used _put(), right?
Yes, that's the difference.
On 07/29/12 10:50, Alan Stern wrote:
On Sun, 29 Jul 2012, James wrote:
I have 3.5.0+
How can I find out what the problem is with my USB UPS?
Your logs indicate that the UPS repeatedly disconnects from and
reconnects to the USB bus. At least, that's what it looks like -- it's
hard to
Hi Alan,
Here is the full log . During a reboot the usb device is
enumerated in High speed (480 Mb/s) . The it change status to full
Speed (12 Mb/s) followed by a disconnect . After this the device
is again enumerated back in High speed .
[0.971658]
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
The semantic patch (http://coccinelle.lip6.fr/) used in generating this
patch is as follows. Some manual cleanup may be required. This improves
on the previous version in that more devm functions are treated.
virtual after_start
virtual returned
virtual returnedDup
virtual arg
virtual all_args
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
A new label name is
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
From: Julia Lawall julia.law...@lip6.fr
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia
On Sun, Jul 29, 2012 at 8:25 PM, Alan Stern st...@rowland.harvard.edu wrote:
For me there's also an issue of style: If you do a synchronous get then it
looks odd not to do a synchronous put. My feeling has always been that
the async routines are for use in non-process contexts, where the sync
Alexey Filin wrote:
On Sat, Jul 28, 2012 at 8:50 PM, Clemens Ladisch clem...@ladisch.de wrote:
Alexey Filin wrote:
On Fri, Jul 27, 2012 at 5:04 PM, Peter Stuge pe...@stuge.se wrote:
If you require consumer interfaces and you want neither USB nor
Ethernet then I guess there is only FireWire
On Thu, Jul 26, 2012 at 7:47 PM, Alan Stern st...@rowland.harvard.edu wrote:
You can do this only by hacking up a special driver of your own.
Since transfer completions would not be reported by IRQs in time, you
would have to poll for transfer completions at microsecond intervals.
This would
On Sun, 29 Jul 2012, Rajaram R wrote:
The ep list doesn't belong to the gadget driver; it belongs to the UDC
driver. The maxpacket has to be adjusted to match the value stored in
the descriptor so that the UDC will tell the hardware to use the right
maxpacket value.
The ep list is
On Sun, 29 Jul 2012, James wrote:
It noticeably slows down booting.
It shouldn't interfere appreciably with booting, unless you're waiting
for some other USB device to be detected. All the USB communication
should happen in the background.
It does wait until the UPS is stable, I
On Mon, 30 Jul 2012, Jassi Brar wrote:
On Sun, Jul 29, 2012 at 8:25 PM, Alan Stern st...@rowland.harvard.edu wrote:
For me there's also an issue of style: If you do a synchronous get then it
looks odd not to do a synchronous put. My feeling has always been that
the async routines are
Hi Alen,
This error is intermittent . It doesn't happen always .
Regards,
Shaiju.
-Original Message-
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Sunday, July 29, 2012 2:39 PM
To: shaiju shaiju
Cc: 'Sadasivan Shaiju'; 'Peter Chen'; 'USB list'
Subject: RE: usb
On Mon, 30 Jul 2012, Alexey Filin wrote:
On Thu, Jul 26, 2012 at 7:47 PM, Alan Stern st...@rowland.harvard.edu wrote:
You can do this only by hacking up a special driver of your own.
Since transfer completions would not be reported by IRQs in time, you
would have to poll for transfer
On Sun, 29 Jul 2012, shaiju shaiju wrote:
Hi Alen,
This error is intermittent . It doesn't happen always .
Then there may not be any way to determine the cause. Perhaps the
firmware in the USB device intermittently crashes.
Alan Stern
--
To unsubscribe from this list: send the
Hi Bhupesh,
Thanks for the patches.
Just a quick mail to tell you that I'm not forgetting about them, but I'm
currently travelling with limited time available for patch review. I'll try to
address these in the next couple of days.
On Thursday 26 July 2012 10:42:48 Bhupesh Sharma wrote:
This
The patch is doing a little bit more than what patch subject says.
Please either come up with a better subject and commit message or
split the patch to have it match the subject.
On Thu, Jul 26, 2012 at 06:35:15PM +0800, Richard Zhao wrote:
Signed-off-by: Richard Zhao richard.z...@freescale.com
Hi Ido,
Some more comments.
-Original Message-
From: Ido Shayevitz [mailto:i...@codeaurora.org]
Sent: Sunday, July 29, 2012 9:55 PM
To: Anton Tikhomirov
Subject: RE: [RFC/PATCH v3] usb: dwc3: Introduce OTG driver for dwc3
Hi Anton,
Thanks,
Fixed and will be sent soon,
Ido
The hub is always supposed to support reset and its persist is enabled.
So hub doesn't need attribute avoid_reset_quirk. The patch is to take
attribute avoid_reset_quirk out of usb device's attribute group and
add or remove it in the usb_create/remove_sysfs_dev_files() if the device
is not a usb
24 matches
Mail list logo
