linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>, Oliver Neukum <oliver@neukum.org>
Cc: x0r <x0r@dv-life.ru>, Linux Input <linux-input@vger.kernel.org>,
	Linux USB <linux-usb@vger.kernel.org>
Subject: ACRUX gamepads not happy with autosuspend?
Date: Mon, 19 Jul 2010 17:17:45 -0700	[thread overview]
Message-ID: <20100720001745.GA17910@core.coreip.homeip.net> (raw)
In-Reply-To: <4C44E3A2.8080301@dv-life.ru>

Jiri, Oliver,

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 states that once device is plugged in the light ion it turns on
briefly and then goes off and from that point on nothing comes from
the device. They deal with it by having an application open the jsX
device as soon as it appears and that makes gamepad work - but it
is obviously not a solution.

It looks like we either need to disable autosuspend for these devices
or maybe kick the device harder when userspace tries to open it so
that it wakes up if it went to sleep.

(Sergei, have you tried disabling autosuspend on your box if it is
enabled?)

Also, if one attempts to boot the box with gamepad already connected
then the driver gets confused and will attempt to reset the device
indefinitely:

[   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

Under Windows the device works well with the standard driver; no
vendor specific drivers is required... Any ideas?

Thanks!

-- 
Dmitry

       reply	other threads:[~2010-07-20  0:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C3F8A90.3020308@dv-life.ru>
     [not found] ` <20100716080200.GA14120@core.coreip.homeip.net>
     [not found]   ` <4C44D236.40002@dv-life.ru>
     [not found]     ` <201007191630.07475.dmitry.torokhov@gmail.com>
     [not found]       ` <4C44E3A2.8080301@dv-life.ru>
2010-07-20  0:17         ` Dmitry Torokhov [this message]
2010-07-20  8:07           ` ACRUX gamepads not happy with autosuspend? Oliver Neukum
     [not found]             ` <201007201007.04518.oneukum-l3A5Bk7waGM@public.gmane.org>
2010-07-20  8:58               ` Jiri Kosina
2010-07-20 10:03                 ` Oliver Neukum
     [not found]                   ` <201007201203.43573.oneukum-l3A5Bk7waGM@public.gmane.org>
2010-07-20 12:14                     ` x0r
2010-07-20 12:24                       ` Oliver Neukum
2010-07-24  7:51                         ` Dmitry Torokhov
     [not found]                           ` <20100724075112.GB3615-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2010-07-25  0:58                             ` x0r

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100720001745.GA17910@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=x0r@dv-life.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).