On Mon, 26 Nov 2012, Oliver Neukum wrote: > 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. True, but you can blame the bad effects on the program that configured the modem via usbfs and then didn't unconfigure the modem when it was finished. Of course, there would still be a problem if the system was suspended while this program was running and using the modem. There's no way to tell usbfs that remote wakeup is required. 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
