BUG: USB Reset-Resume Mechanism does not work for runtime resume

2014-03-05 Thread Poulain, Loic
Hi, I think there is an issue with the reset-resume mechanism during USB runtime resume, leaving the interfaces suspended forever. - Context: Android platform, running a 3.13 + Google AOSP patches kernel. I'm facing a USB issue with the bsusb driver. btusb driver has the USB runtime suspend en

RE: BUG: USB Reset-Resume Mechanism does not work for runtime resume

2014-03-06 Thread Poulain, Loic
other solution found (logical disconnect, reset_resume mandatory...). But I think this dead end should be fixed. Regards, Loic Poulain From: Peter Chen [peter.c...@freescale.com] Sent: Thursday, March 06, 2014 2:10 AM To: Alan Stern Cc: Poulain, Loic; linux

[PATCH] rebind: Add rebind mechanism for runtime-resume

2014-03-10 Thread Poulain, Loic
Despite the needs_rebind flag, the interface rebind was never done for the PM runtime resume. This patch fixes this issue by triggering the rebind in usb runtime resume. The rebind procedure needs to be called with the device lock. However, depending the call path (remote wakeup, local resume), th

[PATCHv2] rebind: Add rebind mechanism for runtime-resume

2014-03-11 Thread Poulain, Loic
Despite the needs_rebind flag, the interface rebind was never done for the PM runtime resume. This patch fixes this issue by triggering the rebind in usb runtime resume. The rebind procedure needs to be called with the device lock. However, depending the call path (remote wakeup, local resume), th

RE: [PATCHv2] rebind: Add rebind mechanism for runtime-resume

2014-03-11 Thread Poulain, Loic
them all. Regarding, the rebind patch itself, it's ok for me with the forced software failure test. But should be completed with an other patch or new patchset for the btusb driver (at least). Regards, Loic Poulain From: Alan Stern [st...@rowland.har

RE: [PATCHv2] rebind: Add rebind mechanism for runtime-resume

2014-03-12 Thread Poulain, Loic
Hello Alan, I applied your patch, then reworked mine in order to use usb_unbind_and_rebind_marked_interfaces. It works great with the combination of this two fixes. I even reproduced the btusb runtime-resume hardware issue which is now handled correctly, interfaces are unbind/rebind. I can pro

[PATCHv3] rebind: Add rebind mechanism for runtime-resume

2014-03-12 Thread Poulain, Loic
Despite the needs_binding flag, the interface rebind was never done for the PM runtime resume. This patch fixes this issue by triggering the rebind in usb runtime resume. The rebind procedure needs to be called with the device lock. However, depending the call path (remote wakeup, local resume), t

RE: reset_resume() for btusb

2014-03-12 Thread Poulain, Loic
erted due to HID dual mode device regression. (cf https://lkml.org/lkml/2013/11/26/347) Regards, Loic Poulain From: Oliver Neukum [oneu...@suse.de] Sent: Wednesday, March 12, 2014 12:03 PM To: Poulain, Loic Cc: linux-usb@vger.kernel.org Subject: reset_resume(

[PATCHv4] rebind: Add rebind mechanism for runtime-resume

2014-04-02 Thread Poulain, Loic
Despite the needs_binding flag, the interface rebind was never done for the PM runtime resume. This patch fixes this issue by triggering the rebind in usb runtime resume. The rebind procedure needs to be called with the device lock. However, depending the call path (remote wakeup, local resume), t

RE: [PATCHv4] rebind: Add rebind mechanism for runtime-resume

2014-04-02 Thread Poulain, Loic
Same content, It's just a rebase on the master + 1 indent update. Regards, Loic Poulain From: Alan Stern [st...@rowland.harvard.edu] Sent: Wednesday, April 02, 2014 2:42 PM To: Poulain, Loic Cc: linux-usb@vger.kernel.org; gre...@linuxfoundation.org Su