On Sat, 26 Jun 2004, Oliver Neukum wrote: > > It's a "we're about to enter USB suspend". The "save state" > > is not necessary (since the device isn't allowed to lose state!). > > The "quiet down" is driver-specific. And usbcore will prevent > > any further requests from getting to the device. > > There seems to be major confusion on my part. > Are you saying that suspend() will be called only in case of _USB_ > specific suspend? That is, things like suspend to disk will _not_ call it?
No, that's not right. Suspend() will be called whenever the device is about to be suspended for any reason. That's the intention, anyway -- the current PM implementation leaves something to be desired in this respect. And I admit, I don't know how suspend-to-disk is supposed to work. The _method_ by which the device will be suspended is of course a normal USB port suspend. In that sense, every suspend looks to the device driver and the device like a USB-specific suspend. But it can be initiated by a number of different paths. 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
