Re: hid powersave by autosuspend #2
Oliver Neukum <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
> > We go to considerable lengths to present interfaces as devices. Each > > interface would be its own input device to user space. We should not > > make it important which logical devices are grouped together physically. > > Taken to its logical conclusion, your argument says that the inactivity > delay shouldn't be set at the USB layer at all -- it should be set at the > input layer and propagated up somehow. Indeed. Now we could again debate whether autosuspend belongs into USB at all. [..] > autosuspend_delay > 0 && test_and_clear_bit(DEVICE_BUSY, ...) == 0 > > where autosuspend_delay <= 0 means the user wants the interface never to > be autosuspended. If any of the test_and_clear_bit() checks fail, you > want the routine to set the next timeout to the maximum of the > corresponding autosuspend_delay values. Yes. > All this in addition to the standard device-wide autosuspend delay, which > will also be settable via sysfs. The initial timeout value should be set > to the maximum of the device-wide delay and the interface delays. > > Is that right? Yes. 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel