Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken

[Oliver Neukum <oneukum@suse.de>]

Am Montag, 15. Januar 2007 17:03 schrieb Alan Stern:
> On Mon, 15 Jan 2007, Oliver Neukum wrote:

> > 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.

If you want to ask with a lot of bug reports which blacklist was loaded,
then we could.
 
> 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.

Do those who can be brought back with a reset need to be listed at all?
Error handling is not a bad idea.

	Regards
		Oliver