Oliver Neukum wrote:
The "prepare for suspend" doesn't mean "you're gonna get a resume, buddy". It means "shut down, but keep enough state to make restarting be fast ... in case you get a resume() instead of disconnect()". That's true for any hot-unpluggable device.
So can you resume() from a sleep state that powers down the bus or not?
Nope; as I said, that's disconnect()ville.
If you get a disconnect() on a storage device without a previous unmount bad things will happen.
And it's sure not the responsibility of usbcore, an HCD, or the storage driver to protect against such things ...
Is powering down a bus a suspension or a disconnect?
For almost all busses, including USB, it's not a suspension unless there's still power to preserve essential state. And as I said, when USB VBUS drops, that's disconnect. (In fact, see the USB spec on that topic...)
Or are you proposing that disconnect() have a different meaning after suspend()?
Not at all, and I don't see how you could infer such a notion from what I did say. Which wasn't a proposal, BTW, it was just saying how things work right now.
- 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
