On Fri, 3 Aug 2007, Matthew Garrett wrote: > Windows will autosuspend hubs, bluetooth devices, HID devices and CDC > devices, so I think we're safe suspending those by default.
And we know that we're not safe suspending scanners and many printers by default. But that leaves plenty of other device classes unaccounted for. > I'm not so > enthusiastic about the "Increase the timeout case" - it doesn't avoid > any races, just makes them less likely. USB is likely to get loaded in > the initramfs, but we may not have a full set of udev rules until the > root fs is up and that can take an effectively arbitrarily large amount > of time. If it takes longer than 15 minutes, something is wrong. At that point the user will have worse things to worry about than whether some USB devices got suspended. And 15 minutes is a perfectly reasonable autosuspend timeout for devices that might be plugged in all day long. Alan Stern ------------------------------------------------------------------------- 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
