On Thursday 02 August 2007, Alan Stern wrote: > Also, building something this sweeping into a kernel driver feels like > a mistake. It ought to be more easily configurable from userspace, say > via a sysfs file.
Yeah, I could have sworn there was extensive discussion over the creation of a sysfs .../power/autususpend attribute which can enable or disable autosuspend on a per-device basis. Seems to me it ought to be practical to organize a database that can be consulted by an outcall from udev, disabling autosuspend on devices which are known to be broken. The "modules.usbmap" syntax is an obvious place to start (painful though it is), and I'm sure there are folk who would prefer web-accessible/updatable databases. It'd need people to maintain that, of course, along with whatever tools consult it. But that's a solvable problem, and it would keep the problem properly outside of the kernel. Long term, of course, this is just a pile of bugs for device vendors to fix in their next revisions ... so they don't end up on the list of "devices to avoid buying" for use with Linux systems. - Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
