On Thu, 13 Mar 2014, Oliver Neukum wrote: > On Wed, 2014-03-12 at 15:18 +0000, Poulain, Loic wrote: > > My thought was to fix the usbcore rebind issue (with pm_runtime) > > to let the core unbind and rebind the device's interfaces for drivers > > with no reset_resume callback (not only btusb). > > Those functions seem to be independent. Which functions are you referring to? > Even if you have > reset_resume() it can still fail and the kernel needs to > deal with that. Sure. > > Implementing the btusb reset_resume seems risky, > > a patch implementing this callback has been previously reverted due to > > HID dual mode device regression. (cf https://lkml.org/lkml/2013/11/26/347) > > Alan, perhaps the core code should honor QUIRK_RESET and unbind > if it is set. Then hid2hci could set the flag. You mean, if QUIRK_RESET is set then don't bother doing a reset-resume? Just logically disconnect the device? Why would that be better than unbinding and rebinding the driver? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
