From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Cameron Gutman <aicommander@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: xpad - fix input from Covert Forces Xbox One controller
Date: Wed, 9 Dec 2015 22:47:43 -0800 [thread overview]
Message-ID: <20151210064743.GC35505@dtor-ws> (raw)
In-Reply-To: <5663EB97.7020103@gmail.com>
Hi Cameron,
On Sun, Dec 06, 2015 at 12:02:31AM -0800, Cameron Gutman wrote:
> The Covert Forces edition of the Xbox One controller requires the full 5
> byte initialization packet to work at all. The 5 byte packet was known to
> be needed for proper rumble support, but it looks like it's needed even
> without rumble on these controllers.
I already have a patch that does this and rumble for these controllers
in my queue (in xpad branch) so this one is not needed.
Thank you.
>
> Signed-off-by: Cameron Gutman <aicommander@gmail.com>
> ---
> drivers/input/joystick/xpad.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
> index fd4100d..de89de0 100644
> --- a/drivers/input/joystick/xpad.c
> +++ b/drivers/input/joystick/xpad.c
> @@ -1052,7 +1052,10 @@ static int xpad_open(struct input_dev *dev)
> /* Xbox one controller needs to be initialized. */
> xpad->odata[0] = 0x05;
> xpad->odata[1] = 0x20;
> - xpad->irq_out->transfer_buffer_length = 2;
> + xpad->odata[2] = 0x00;
> + xpad->odata[3] = 0x01;
> + xpad->odata[4] = 0x00;
> + xpad->irq_out->transfer_buffer_length = 5;
> return usb_submit_urb(xpad->irq_out, GFP_KERNEL);
> }
>
> --
> 2.5.0
--
Dmitry
prev parent reply other threads:[~2015-12-10 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 8:02 [PATCH] Input: xpad - fix input from Covert Forces Xbox One controller Cameron Gutman
2015-12-10 6:47 ` Dmitry Torokhov [this message]
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=20151210064743.GC35505@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aicommander@gmail.com \
--cc=linux-input@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).