From: Szymon Janc <szymon.janc@codecoup.pl>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <jikos@kernel.org>
Subject: Re: [PATCH] HID: sony: Fix SHANWAN pad rumbling on USB
Date: Thu, 09 Nov 2017 09:24:21 +0100 [thread overview]
Message-ID: <2042668.WNNEdIESQl@ix> (raw)
In-Reply-To: <20171107142447.11810-1-hadess@hadess.net>
Hi,
On Tuesday, 7 November 2017 15:24:47 CET Bastien Nocera wrote:
> The SHANWAN PS3 clone joypad will start its rumble motors as soon as
> it is plugged in via USB. As the additional USB interrupt does nothing on
> the original PS3 Sixaxis joypads, and makes a number of other
> clone joypads actually start sending data, disable that call for
> the SHANWAN so the rumble motors aren't started on plug.
>
> Signed-off-by: Bastien Nocera <hadess@hadess.net>
> ---
> drivers/hid/hid-sony.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
> index d03203a82e8f..b9dc3ac4d4aa 100644
> --- a/drivers/hid/hid-sony.c
> +++ b/drivers/hid/hid-sony.c
> @@ -1439,10 +1439,16 @@ static int sixaxis_set_operational_usb(struct
> hid_device *hdev) goto out;
> }
>
> - ret = hid_hw_output_report(hdev, buf, 1);
> - if (ret < 0) {
> - hid_info(hdev, "can't set operational mode: step 3, ignoring\n");
> - ret = 0;
> + /*
> + * But the USB interrupt would cause SHANWAN controllers to
> + * start rumbling non-stop.
> + */
> + if (strcmp(hdev->name, "SHANWAN PS3 GamePad")) {
> + ret = hid_hw_output_report(hdev, buf, 1);
> + if (ret < 0) {
> + hid_info(hdev, "can't set operational mode: step 3, ignoring\n");
> + ret = 0;
> + }
> }
>
> out:
Works for me!
Tested-by: Szymon Janc <szymon.janc@codecoup.pl>
--
pozdrawiam
Szymon Janc
next prev parent reply other threads:[~2017-11-09 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 14:24 [PATCH] HID: sony: Fix SHANWAN pad rumbling on USB Bastien Nocera
2017-11-09 8:24 ` Szymon Janc [this message]
2017-11-09 12:32 ` Jiri Kosina
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=2042668.WNNEdIESQl@ix \
--to=szymon.janc@codecoup.pl \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 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.