On 10/16/06, Alan Stern <[EMAIL PROTECTED]> wrote: > On Mon, 16 Oct 2006, Oliver Neukum wrote: > > > 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? > > It means that the input core is in a better position to know when an input > device should be suspended than the USB HID core is. For now it's okay to > do this at the USB level, but eventually the inactivity timers and other > paraphernalia should be pushed down into the input level. Note that then > the same mechanisms could apply to other non-USB sor+ts of input devices as > well. >
I don't agree. I think that power management should be left to drivers working with hardware and not be placed into input core. There will be different rules and different decisions, based on the type of device (USB, PS/2, serial, etc, etc). Input layer should not be concerned with these. -- Dmitry ------------------------------------------------------------------------- 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
