Am Montag, 28. Juni 2004 01:11 schrieb David Brownell:
> >>No, if the bus powers off the call sequence seen by that driver
> >>will be suspend()->disconnect() rather than suspend()->resume().
> >
> >
> > This will do horrible things if the attached device has considerable state.
>
> Only if the suspend() method is deeply stupid, right?
> I mean, here's this code which KNOWS it may never have
> another chance to save that state -- not saving it?
Saving is not the issue. If it gets a disconnect() it must act on that.
> 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?
If you get a disconnect() on a storage device without a previous unmount
bad things will happen.
Is powering down a bus a suspension or a disconnect?
Or are you proposing that disconnect() have a different meaning after
suspend()?
Regards
Oliver
-------------------------------------------------------
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
