From: Yuri Khan <yurivkhan@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, Yuri Khan <yurivkhan@gmail.com>
Subject: [PATCH 0/1] Input: xpad - Add a variation of Mad Catz Beat Pad
Date: Fri, 6 Jul 2012 23:32:03 +0700 [thread overview]
Message-ID: <1341592324-665-1-git-send-email-yurivkhan@gmail.com> (raw)
Hello all,
I have a dance pad that has the vendor and product IDs of a Mad Catz
Beat Pad (0738:4540), but it doesn't get handled by xpad.ko because xpad
expects (a) interface class and subclass of 'X':'B', or (b) interface
class 255, subclass 93, protocol 1 or 129; while my device identifies as
interface class 3 (HID), subclass 0, protocol 0. As a result, usbhid
grabs it and it sort of works, but the diagonal pads are not mapped.
When I add a usbhid option quirks=0x0738:0x4540:0x4 (so that usbhid does
not attempt to handle this device) and rebuild the xpad module with the
following patch, the device works as expected. Dmitry Torokhov, the
current maintainer of input drivers, suggested that I include a change
to add the usbhid quirk in my patch.
Yuri Khan (1):
Input: xpad - Add a variation of Mad Catz Beat Pad
drivers/hid/hid-ids.h | 3 +++
drivers/hid/usbhid/hid-quirks.c | 2 ++
drivers/input/joystick/xpad.c | 2 ++
3 files changed, 7 insertions(+)
--
1.7.9.5
next reply other threads:[~2012-07-06 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 16:32 Yuri Khan [this message]
2012-07-06 16:32 ` [PATCH 1/1] Input: xpad - Add a variation of Mad Catz Beat Pad Yuri Khan
2012-07-06 16:57 ` [PATCH 0/1] " Yuri Khan
2012-07-06 17:03 ` Dmitry Torokhov
2012-07-08 5:49 ` [PATCH v2 1/1] Input: xpad - Handle all variations " Yuri Khan
2012-07-09 14:08 ` Jiri Kosina
2012-07-09 15:52 ` Yuri Khan
2012-07-10 17:33 ` [PATCH v3 " Yuri Khan
2012-07-10 20:05 ` Jiri Kosina
2012-07-10 20:42 ` Dmitry Torokhov
2012-07-11 7:02 ` [PATCH v4 " Yuri Khan
2012-07-11 7:57 ` Dmitry Torokhov
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=1341592324-665-1-git-send-email-yurivkhan@gmail.com \
--to=yurivkhan@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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).