On Tue, 29 Jun 2004, Oliver Neukum wrote: > > > This has nothing to do with considering disconnect() as anything other > > than a binding change. And you certainly don't want to switch to > > altsetting 0 immediately after the suspend() callback returns, because > > that will confuse the driver in the common case where it remains bound to > > the device. > > No. Of course you have to restore the altsetting before resume() > But the driver must not touch the device after suspend(), so usbcore > can manage altsettings between suspend() and resume().
It may seem that way, but we really shouldn't change altsettings without the driver's knowledge. That's because the Set-Interface request is liable to reinitialize a lot of device state. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
