Am Montag, 23. November 2009 18:43:09 schrieb Alan Stern: > there was a disconnection. And the hub driver realizes that something > went wrong because it tries to carry out a reset-resume -- and this > time it succeeded with not XactErr problem, thanks to the mdelay. > Unfortunately the cdc-acm and cdc-ether drivers don't have reset-resume > handlers, so the drivers were unbound and rebound anyway. 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. 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. Regards Oliver -- 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
