Alan Stern wrote:
Unfortunately the current API doesn't allow for such distinctions; the suspend() method in usb_driver doesn't include an argument to indicate which sort of suspend is about to occur. Oddly
That's because there _is_ only one kind of "suspend"; the other is power-off!
enough, even PCI makes it difficult to tell since the two states are both level-3 suspends (D3hot vs. D3cold).
And of course, USB != PCI/ACPI.
And as a rule, I've only seen PCI report "gonna D3hot suspend". But it sometimes says "whoops, this is a resume from D3cold"; and that's for non-hotpluggable devices (not Cardbus etc).
-------------------------------------------------------
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
