mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Staudt <max@enpas.org>
To: Roderick Colenbrander <thunderbird2k@gmail.com>
Cc: Benjamin Tissoires <bentiss@kernel.org>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Roderick Colenbrander <roderick.colenbrander@sony.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] hid-playstation: DS4: Update rumble and lightbar together
Date: Sun, 11 Aug 2024 22:22:37 +0900	[thread overview]
Message-ID: <8ecac53b-daea-405a-8fe4-15cec98221c5@enpas.org> (raw)
In-Reply-To: <CAEc3jaDzvus5ZDCupDzpy1HWRAwaKHQZLpDU4gO1=jTmPUzeKA@mail.gmail.com>

Hi Roderick,

Welcome back, and thanks for replying!

Comments below :)


On 8/9/24 08:11, Roderick Colenbrander wrote:
> Preferably it would be some type of quirk.

Agreed.


> Just changing the patterns is not a good idea also in case
> hypothetically other features were get added (volume control for the
> speaker, microphone settings,..) and other features which work through
> the same output report and various of these devices probably won't
> handle (or it is hard to predict).

I think at this point the discussion and/or your concerns may have 
diverged because of misunderstandings. I do not intend to touch any 
upper bits in valid_flag0.

I've been thinking about this, and my conclusion is that both my patch 
(v1) and its description were trying too hard to squeeze in as much 
context as possible. I think they were too hard to understand - sorry!

So to make things easier to understand for everyone, I have sent a v2 of 
the patch. It's really short now, and it should be obvious that I am not 
touching any flag bits that the driver didn't touch already.

Hopefully this can get everyone on the same page - could you please have 
a look? Maybe this patch is actually fine with you.


> I have been trying to think of ways to realize a quirk. I think we
> need to search it in the HID reports. Either do some tests on reports
> we know aren't supported (ugly). It can also be that the calibration
> data is invalid (zeros, which we now initialize to a default). Or
> perhaps is the firmware/hardware version related HID report returning
> anything interesting?

I'll need to have a look, but there's a catch here: Bluetooth devices 
can't be tested for some of the quirks that USB devices have, for 
example the MAC address report that clones usually don't implement. I 
wish to fix both classes of devices, since I've seen a quirky BT device 
some (longer) time ago.


Could you please look at the new PATCHv2 first? Maybe that one is fine 
with you, and it all boils down to me just not presenting things well in v1.



Thanks :)

Max


  reply	other threads:[~2024-08-11 13:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 16:30 Max Staudt
2024-06-17 23:01 ` Roderick Colenbrander
2024-06-20 19:26   ` Max Staudt
2024-07-08 16:07     ` Roderick Colenbrander
2024-07-10 15:35       ` Max Staudt
2024-07-17  0:26         ` Roderick Colenbrander
2024-07-21 14:33           ` Max Staudt
2024-07-22  3:40             ` Max Staudt
2024-07-22 16:49               ` Benjamin Tissoires
2024-07-22 19:30                 ` Max Staudt
2024-08-08 23:11                   ` Roderick Colenbrander
2024-08-11 13:22                     ` Max Staudt [this message]
2024-07-22 16:46             ` Benjamin Tissoires
2024-07-22 19:24               ` 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=8ecac53b-daea-405a-8fe4-15cec98221c5@enpas.org \
    --to=max@enpas.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=bentiss@kernel.org \
    --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

all inboxes | Powered by JetHome®