On Monday 26 November 2012 12:06:21 Alan Stern wrote:
> Still, this is an important consideration. It means that remote wakeup
> doesn't need to be enabled when the driver isn't present. Which means
> that the cdc-acm driver is indeed the right place to fix this problem
> -- although the way you did it isn't the right way. The right way is
> to have cdc-acm turn on the needs_remote_wakeup flag in the
> usb_interface structure.
Well, no. You cannot be sure that the device is quiet if no driver is bound.
It is perfectly possible to access a device through usbfs and cause lasting
effects.
We could use RESET_RESUME, but it seems wrong to use that quirk
while gentler alternatives are available.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
