On Mon, 27 Sep 2004, Oliver Neukum wrote: > But snapshotting is a real system state. It has precisely defined > requirements. > -no DMA > -state in ram, not in device > You cannot translate it into a power stae, unfortunately.
Snapshotting _is_ a system state as you say, and it's also an activity. (Not an activity that drivers have to worry about though.) And yes, it's not a power state. But it could be called a policy state. > > I'm not sure what you mean here. As an example, a user would want to know > > whether a device supports remote wakeup. And the user might want to be > > able to specify whether or not remote wakeup should be disabled when the > > device is suspended. > > Impossible to give generally. The answer would be a matrix of power > state and ability to do a remote wakeup. To keep it simple, we can simply report whether the device supports remote wakeup at all, in any state. If the user wants remote wakeup enabled but the system institutes a policy where the power level doesn't allow the device to do wakeup, the driver can either report an error or just ignore the problem and leave wakeup disabled. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
