On Mon, 15 Jan 2007, Oliver Neukum wrote: > Am Sonntag, 14. Januar 2007 20:47 schrieb [EMAIL PROTECTED]: > > > Can anyone suggest another approach? > > > > > > Alan Stern > > > > Just a thought, you could use both a blacklist approach, and a module > > paramater, or something in sysfs, to allow specifying devices that won't > > be suspend and resume compatible. > > Upon further thought, a module parameter won't do as the problem > will arise without a driver loaded. A sysfs parameter turns the whole > affair into a race condition. Will you set the guard parameter before the > autosuspend logic strikes? > Unfortunately this leaves only the least attractive solution.
There could be a mixed approach: a builtin blacklist that is extensible via a procfs- or sysfs-based interface. Note that we actually have two problems to contend with. Some devices must never be autosuspended at all (they disconnect when resuming), and others need a reset after resuming. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
