On Mon, Dec 17, 2001 at 10:38:17AM +0100, Martin Diehl wrote: > > > Nope, it's a definition. Suspend/resume involves preserving > > > state. If they didn't keep power, they couldn't keep that state, > > > and they had to (re)initialize. Just like unplug/replug. > > > > > > If you want such devices to get initialized the same way every > > > time, that's a different issue -- not suspend/resume, since the > > > device isn't getting resumed. > > > > Yes, it's basically unplug/replug, which should preserve the > > confuguration as much as possible, too. > > Well, as explained in the other posting, suspend/resume is pretty much > different from unplug/replug because a suspended device is still drawing > some power from the suspended USB. This way even a buspowered device can > keep its state and the host can be sure, it's still the same device which > he will resume later on.
How? The host will not be notified when the device is unplugged and replugged while suspended. > For unplug/replug OTOH I agree it's a good idea to have the device keep > its state as much as it makes sense - but the host _must not_ make any > assumption here because the replugged device might just be a different one > or might have been plugged to a different host meanwhile. The host should pass all the relevant information to an userspace agent, which can then decide (even can let the user decide if really needed) whether it is the same device and should be used as such or not. You usually will want a replacement device just work without having to restart all the programs using it. -- Vojtech Pavlik SuSE Labs _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
