On Tue, Jul 20, 2010 at 02:24:20PM +0200, Oliver Neukum wrote:

Am Dienstag, 20. Juli 2010, 14:14:13 schrieb x0r:

quoted

В Втр, 20/07/2010 в 12:03 +0200, Oliver Neukum пишет:

quoted

Am Dienstag, 20. Juli 2010, 10:58:50 schrieb Jiri Kosina:

quoted

On Tue, 20 Jul 2010, Oliver Neukum wrote:

quoted

quoted

It looks like ACRUX game controllers do not like autopm. There is
a bug report over at Ubuntu's launchpad:

	https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/448446

That report shows that the symptoms are consistent with autosuspend,
but it doesn't show that autosuspend was on.

That would be my first question -- who enabled autosuspend, if it was 
really on? I thought it should be still off by default, shouldn't it?

It is off by default, but that doesn't stop Ubuntu having a udev rule to
switch it on or patching the kernel, so it might be on. We simply need
to know.

	Regards
		Oliver

x0r@desktop:~$ cat /sys/bus/usb/devices/5-1/power/autosuspend
2

Does it mean that autosuspend is enabled?

No, this means that if it is enabled a heuristic timeout of 2s is used.
That is if your device has been being idle for 2s, it will be autosuspend.

Whether it is autosuspended at all all is controlled in the "level" attribute.

on = no autosuspend
auto = autosuspend activated

Hmm, Sergei says that fiddling with autosuspend values (nor disabling it
altogether by recompiling without CONFIG_USB_SUSPEND) helps. If device
left unopened then attempts to open it (and thus start traffic) at a
later time fail.

Sergei, what happens if you have the device plugged and compile HID as a
module and then unload/reload the driver and try opening the device
right away? Does it work or is it still dead?

Thanks.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html