Comment 315 for bug 85488

I think for the sake of sanity we should include kernel versions if possible when we make comments if something work or not.

It seems the autosuspend went through 3 iterations.

 1. No disable possible, unless you recompile with USB_SUSPEND disabled
 2. autosuspend can be set, with 0 = disable *see note 1.
 3. autosuspend can be set, with negative value to disable, 0= as soon as possible. (at least in 2.6.22)

AFAIK option 2 and 3 will only be available if you compiled your own kernel from kernel.org sources
Option 1 is the option for Feisty kernels
Can't comment on Gutsy

note 1: It might be that this was never the case, but some confusion based on the fact that USB device drivers have a autosuspend that if 1 indicate device can suspend, and if 0, device cannot cannot be suspended. Is it possible that this is being confused for the global setting in kernel parameters?

@Michael, I have no idea what different negative values would do, from KERNEL-PARAMETERS.TXT (2.6.22):

 usbcore.autosuspend=
   [USB] The autosuspend time delay (in seconds) used
   for newly-detected USB devices (default 2). This
   is the time required before an idle device will be
   autosuspended. Devices for which the delay is set
   to a negative value won't be autosuspended at all.
Having a look through the source code it seems the check is if autosuspend_delay < 0 then it is disabled.

@SilverLoz, what kernel version are you using?