From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Cameron Gutman <aicommander@gmail.com>
Cc: rojtberg@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] Input: xpad - send rumble on Xbox One init to fix PowerA pads
Date: Mon, 6 Feb 2017 14:13:53 -0800 [thread overview]
Message-ID: <20170206221353.GF17441@dtor-ws> (raw)
In-Reply-To: <20170205003002.28160-4-aicommander@gmail.com>
On Sat, Feb 04, 2017 at 04:30:00PM -0800, Cameron Gutman wrote:
> Some PowerA pads require a rumble packet to start sending
> input reports.
>
> Signed-off-by: Cameron Gutman <aicommander@gmail.com>
> ---
> drivers/input/joystick/xpad.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
> index 3f19f32b..13f298d 100644
> --- a/drivers/input/joystick/xpad.c
> +++ b/drivers/input/joystick/xpad.c
> @@ -358,6 +358,13 @@ static const struct xpad_output_packet xone_init_pkt[] = {
> * or later firmware installed (or present from the factory).
> */
> {{0x05, 0x20, 0x00, 0x01, 0x00}, 5, true},
> +
> + /*
> + * A rumble packet is required for some PowerA pads to start
> + * sending input reports. One of those pads is (0x24c6:0x543a).
> + */
> + {{0x09, 0x00, 0x00, 0x09, 0x00, 0x0F, 0x00, 0x00,
> + 0x00, 0x00, 0x00, 0x00, 0x00}, 13, true},
I am uncomfortable with us just blasting random commands to random
controllers. Can we make it device-dependent. I.e:
struct xboxone_init_packet = {
u16 idVendor;
u16 idProduct;
const u8 *data;
size_t len;
};
static const u8 xboxone_powera_init[] = {
0x09, 0x00, 0x00, 0x09, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00
};
#define XBOXONE_INIT_PKT(_vid, _pid, _data) \
{ \
.idVendor = (_vid), \
.idProduct = (_pid), \
.data = (_data), \
.len = ARRAY_SIZE(data), \
}
...
static const struct xboxone_init_packet xboxone_init_packets[] = {
...
XBOXONE_INIT_PKT(0x24c6, 0x543a, xboxone_powera_init),
...
With 0/0 VID/PID being "catch all" entry.
BTW, why do we set "pending" on these ones? I do not think it is needed.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-02-06 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 0:29 [PATCH 0/5] Correctly support some quirky Xbox One pads Cameron Gutman
2017-02-05 0:29 ` [PATCH 1/5] Input: xpad - use a packet array to start " 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 [this message]
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: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=20170206221353.GF17441@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aicommander@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 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).