Am Montag, 16. Oktober 2006 16:34 schrieb Alan Stern:
> This intricate strategy points out a fact which should have been mentioned
> earlier. For HID devices that are registered with the input core (is that
> all of them?), autosuspend should not be initiated by the USB core. It
> should be initiated by the input core and handed up to the USB level.
Is that meaningful difference given that the driver controls the
usage count? Doesn't it boil down to a request for autosuspend without
a delay?
> > Do you have mice that do not require button push to wake up?
>
> It doesn't matter. The mouse descriptors don't specify whether motion is
> a wakeup event, so we have to assume that any mouse will send a wakeup
> request only when a button is pressed. This makes it impossible to do
> idle-time suspending.
That is a bit strong. I'd say this should mean that idle-time suspending
isn't the default, but for those devices that readily wake, it still can save
energy.
Regards
Oliver
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
