On Tue, 24 Nov 2009, Oliver Neukum wrote: > Alan, > > on fourth thought this is dangerous. Remote wakeup generally means > that a device has data available. A reset will wipe out this data. For this > reason the core checks for QUIRK_RESET_RESUME if remote wakeup > is requested. Actually, if the quirk is set then the core will disallow autosuspend if any of the drivers doesn't support reset-resume or any of them needs remote wakeup. > For this reason drivers are written with the expectation that reset_resume() > will not be called as a result of a remote wakeup. I think usbcore should > not attempt to use reset_resume() if a remote wakeup leads to a reset. How is calling a reset_resume method any worse than going through an unbind/rebind cycle? Either way, the device's data will be lost. 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
