Bug 16421

Summary: Acrux gamepad probably requires PM fix
Product: Drivers Reporter: Stephen Kitt (steve)
Component: Input DevicesAssignee: drivers_input-devices
Status: RESOLVED OBSOLETE    
Severity: normal CC: alan, dmitry.torokhov, jikos, oliver
Priority: P1    
Hardware: All   
OS: Linux   
URL: https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/448446
Kernel Version: 2.6.31 Subsystem:
Regression: No Bisected commit-id:

Description Stephen Kitt 2010-07-20 06:39:27 UTC
Hi,

Dmitry suggested I submit this bug to get a proper fix rather than my nasty workaround (see the Launchpad info on https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/448446).

Acrux gamepads (USB ID 0x1a34:0x0802), as supported by Sergei Kolzun's new HID driver, seem to require specific support on the USB side of things. I thought it was a PM problem a while ago (https://bugs.launchpad.net/ubuntu/+source/joystick/+bug/448446/comments/8) but the result of my test was inconclusive (which probably says more about my test than about the bug), so I knocked together a workaround to allow the original bug reporter to use his gameped. Sergei has also seen some other problems when initialising the device:

> On Sun, 18 Jul 2010 10:13:20 +1100, x0r<x0r@dv-life.ru>  wrote:
>> I have some new investigations about ACRUX gamepad, when i turn on PC
>> with connected gamepad, i have "looping" kernel with this message:
>>
>> [   32.430271] drivers/hid/usbhid/hid-core.c: can't reset device,
>> 0000:00:1a.2-1/input0, status -32
>> [   32.446271] drivers/hid/usbhid/hid-core.c: can't reset device,
>> 0000:00:1a.2-1/input0, status -32
>> [   32.462271] drivers/hid/usbhid/hid-core.c: can't reset device,
>> 0000:00:1a.2-1/input0, status -32
>> [   32.478272] drivers/hid/usbhid/hid-core.c: can't reset device,
>> 0000:00:1a.2-1/input0, status -32
>>
>> This messages continues before i reconnect gamepad. I think this is real
>> reason of ACRUX incorrect behavior under linux. I've tested this device
>> under Windows XP - it works correctly, even after turning on PC with
>> connected device.

I'll point Sergei to this bug too since he has one of these devices and can doubtless help debug this problem!

Once this bug is fixed I'll remove jskeepalive of course (at least once the fixed kernel is in Debian and Ubuntu, with a version check in the meantime to avoid using it when unnecessary).

Regards,

Stephen