From: Max Staudt <max@enpas.org>
To: Roderick Colenbrander <thunderbird2k@gmail.com>,
Jiri Kosina <jikos@kernel.org>
Cc: Roderick Colenbrander <roderick.colenbrander@sony.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] hid-playstation: DS4: Update rumble and lightbar together
Date: Wed, 21 Aug 2024 17:22:28 +0200 [thread overview]
Message-ID: <0b58bf46-503e-48c6-ad1c-e54a5c13e7a2@enpas.org> (raw)
In-Reply-To: <CAEc3jaD6sv=O+MbH5XtHvpXgXyzBROfLDYX2rGoa+3QCOJ-Srw@mail.gmail.com>
On 8/21/24 17:03, Roderick Colenbrander wrote:
> Ideally I would like some type of quirk, but I have no good way of
> verifying (also across different 'clone' devices) how reliable this
> current check would be. It feels a bit too much towards a magical
> value. I don't see why the reports would differ besides some engineer
> having made a typo.
The descriptors differ in several ways - why, I don't know.
- Across a few DS4 2.0 that I have looked at, they seemed to all have
the same descriptors.
- Quite a few clones seemed to expose the exact same descriptor on
USB, and those didn't need this quirk either.
- I have seen two controllers that need this quirk, and they both have
the *same* descriptor, which is close to, but still notably different
from, the DS4 v2.0 descriptor.
So, while I don't have a large base to infer from, it seems like this
particular "magic" descriptor and the quirk are correlated.
Do you have another idea for a specific enough difference that I could
look for?
> My gut feeling is that the previous fix is less fragile, so let's opt
> for that one.
Let me know if you wish for me to resend v2 with a Signed-off-by. Or, I
guess Jiri might just manually patch it in - please see this as
permission to do so if you prefer this.
Max
next prev parent reply other threads:[~2024-08-21 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 14:25 [PATCH v4] hid-playstation: DS4: Update rumble and lightbar together Max Staudt
2024-08-21 14:33 ` Jiri Kosina
2024-08-21 15:03 ` Roderick Colenbrander
2024-08-21 15:22 ` Max Staudt [this message]
2024-08-21 22:25 ` Jiri Kosina
2024-08-22 11:38 ` Max Staudt
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=0b58bf46-503e-48c6-ad1c-e54a5c13e7a2@enpas.org \
--to=max@enpas.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roderick.colenbrander@sony.com \
--cc=thunderbird2k@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).