From: Cameron Gutman <aicommander@gmail.com>
To: dmitry.torokhov@gmail.com, rojtberg@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Cameron Gutman <aicommander@gmail.com>
Subject: [PATCH 0/5] Correctly support some quirky Xbox One pads
Date: Sat, 4 Feb 2017 16:29:57 -0800 [thread overview]
Message-ID: <20170205003002.28160-1-aicommander@gmail.com> (raw)
There are a bunch of quirky Xbox One pads that depend on weird
initialization things that the Microsoft pads don't. In this series,
I've incorporated quirk handling from Valve's Steam Link driver[0]
and the 360Controller project[1] for macOS.
Patches 1 - 3 are split that way in case 2 or 3 introduce regressions
that need to be bisected. The new packet in patch 2 has been in Pavel's
xpad repository[2] for a little over a month without complaints, and
patch 3 just sends a rumble packet on init, so I don't expect regressions.
Patch 2 was tested by a GitHub user with a Hori pad[3]. I've tested patch 3
on a previously non-working PowerA pad that I got my hands on.
I folded Patch 4 into this series as it was previously submitted alone.
It is unchanged from its original submission.
Patch 5 was a patch I had previously dropped from a previous series, but it
turns out to still be needed for Xbox One S pads on the latest firmware. It
has also been in Pavel's repository for months without complaints.
[0]: https://github.com/ValveSoftware/steamlink-sdk/blob/master/kernel/drivers/input/joystick/xpad.c
[1]: https://github.com/360Controller/360Controller
[2]: https://github.com/paroj/xpad
[3]: https://github.com/paroj/xpad/issues/59
Cameron Gutman (5):
Input: xpad - use a packet array to start Xbox One pads
Input: xpad - add init packet for Hori and Titanfall 2 pads
Input: xpad - send rumble on Xbox One init to fix PowerA pads
Input: xpad - restore LED state after device resume
Input: xpad - fix stuck mode button on Xbox One S pad
drivers/input/joystick/xpad.c | 102 ++++++++++++++++++++++++++++++++++++------
1 file changed, 88 insertions(+), 14 deletions(-)
--
2.9.3
next reply other threads:[~2017-02-05 0:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 0:29 Cameron Gutman [this message]
2017-02-05 0:29 ` [PATCH 1/5] Input: xpad - use a packet array to start Xbox One pads Cameron Gutman
2017-02-05 0:29 ` [PATCH 2/5] Input: xpad - add init packet for Hori and Titanfall 2 pads Cameron Gutman
2017-02-05 0:30 ` [PATCH 3/5] Input: xpad - send rumble on Xbox One init to fix PowerA pads Cameron Gutman
2017-02-06 22:13 ` Dmitry Torokhov
2017-02-05 0:30 ` [PATCH 4/5] Input: xpad - restore LED state after device resume Cameron Gutman
2017-02-05 1:17 ` kbuild test robot
2017-02-05 1:17 ` kbuild test robot
2017-02-05 1:47 ` Cameron Gutman
2017-02-06 22:05 ` Dmitry Torokhov
2017-02-06 22:57 ` Cameron Gutman
2017-02-05 0:30 ` [PATCH 5/5] Input: xpad - fix stuck mode button on Xbox One S pad Cameron Gutman
2017-02-06 22:03 ` 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=20170205003002.28160-1-aicommander@gmail.com \
--to=aicommander@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rojtberg@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.