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?
There are two levels you're conflating:
- device-specific suspend, which for usb devices always means "prepare for usb suspend" ... there is no other hardware suspend mechanism available that maintains bus connectivity.
- system-wide suspend, which involves shutting down all devices (in what's presumably a smart/safe order) and also stuff like CPUs and high frequency clocks
So usbdev->suspend() is, yes, only called to mean that specific USB device is being suspended. And that doesn't imply anything about whether any other devices are being suspended right now, as in the case of a system-wide suspend.
- Dave
-------------------------------------------------------
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
