From: David Heidelberg <david@ixit.cz>
To: Caleb Connolly <caleb.connolly@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
Vincent Huang <vincent.huang@tw.synaptics.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
methanal <baclofen@tuta.io>
Subject: Re: [PATCH v3 0/7] Subject: [PATCH v3 0/7] Input: synaptics-rmi4: add quirks for third party touchscreen controllers
Date: Mon, 10 Mar 2025 11:47:12 +0100 [thread overview]
Message-ID: <eb4aec7f-3c2f-4c6b-aa84-7798d7ff57a8@ixit.cz> (raw)
In-Reply-To: <53224260-4f3a-447b-9e7b-f68c5c4ba05e@linaro.org>
Hello Caleb,
I'm very sorry about that. Next time I include your patches in the
series I'll definitely send you heads up.
David
On 10/03/2025 11:04, Caleb Connolly wrote:
> Hi David,
>
> Please at least give me a heads up if you're going to resend a patch
> series of mine. I understand it's an old series but I don't think that
> courtesy is too much to ask.
>
> On 3/8/25 14:08, David Heidelberg via B4 Relay wrote:
>> With the growing popularity of running upstream Linux on mobile devices,
>> we're beginning to run into more and more edgecases. The OnePlus 6 is a
>> fairly well supported 2018 era smartphone, selling over a million units
>> in it's first 22 days. With this level of popularity, it's almost
>> inevitable that we get third party replacement displays, and as a
>> result, replacement touchscreen controllers.
>>
>> The OnePlus 6 shipped with an extremely usecase specific touchscreen
>> driver, it implemented only the bare minimum parts of the highly generic
>> rmi4 protocol, instead hardcoding most of the register addresses.
>> As a result, the third party touchscreen controllers that are often
>> found in replacement screens, implement only the registers that the
>> downstream driver reads from. They additionally have other restrictions
>> such as heavy penalties on unaligned reads.
>> This series attempts to implement the necessary workaround to support
>> some of these chips with the rmi4 driver. Although it's worth noting
>> that at the time of writing there are other unofficial controllers in
>> the wild that don't work even with these patches.
>> We have been shipping these patches in postmarketOS for the last several
>> months, and they are known to not cause any regressions on the OnePlus
>> 6/6T (with the official Synaptics controller), however I don't own any
>> other rmi4 hardware to further validate this.
>>
>> ---
>> Changes since v2:
>> - reworded dt-bindings property description
>> - fixed the rmi_driver_of_probe definition for non device-tree builds.
>> - fixed some indentation issues reported by checkpatch
>> - change rmi_pdt_entry_is_valid() variable to unsigned
>> - Link to v2: https://patchwork.kernel.org/project/linux-input/
>> cover/20230929-caleb-rmi4-quirks-v2-0-b227ac498d88@linaro.org/
>
> Please use lore links
>>
>> Changes since v1:
>> - Improve dt-bindings patch (thanks Rob)
>> - Add missing cast in patch 5 to fix the pointer arithmetic
>> - Link to v1: https://lore.kernel.org/r/20230929-caleb-rmi4-quirks-
>> v1-0-cc3c703f022d@linaro.org
>>
>> ---
>> Caleb Connolly (2):
>> dt-bindings: input: syna,rmi4: document syna,pdt-fallback-desc
>> Input: synaptics-rmi4 - handle duplicate/unknown PDT entries
>>
>> methanal (5):
>> Input: synaptics-rmi4 - f12: use hardcoded values for
>> aftermarket touch ICs
>> Input: synaptics-rmi4 - f55: handle zero electrode count
>> Input: synaptics-rmi4 - don't do unaligned reads in IRQ context
>> Input: synaptics-rmi4 - read product ID on aftermarket touch ICs
>> Input: synaptics-rmi4 - support fallback values for PDT
>> descriptor bytes
>>
>> .../devicetree/bindings/input/syna,rmi4.yaml | 18 +++
>> drivers/input/rmi4/rmi_driver.c | 140 +++++++++++
>> ++++++----
>> drivers/input/rmi4/rmi_driver.h | 8 ++
>> drivers/input/rmi4/rmi_f01.c | 14 +++
>> drivers/input/rmi4/rmi_f12.c | 117 +++++++++++
>> ++----
>> drivers/input/rmi4/rmi_f55.c | 5 +
>> include/linux/rmi.h | 3 +
>> 7 files changed, 258 insertions(+), 47 deletions(-)
>> ---
>> base-commit: 0a2f889128969dab41861b6e40111aa03dc57014
>> change-id: 20250308-synaptics-rmi4-c832b2f73ceb
>>
>> Best regards,
>
--
David Heidelberg
prev parent reply other threads:[~2025-03-10 10:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 14:08 David Heidelberg via B4 Relay
2025-03-08 14:08 ` [PATCH v3 1/7] dt-bindings: input: syna,rmi4: document syna,pdt-fallback-desc David Heidelberg via B4 Relay
2025-03-10 9:45 ` Krzysztof Kozlowski
2025-03-24 18:00 ` David Heidelberg
2025-03-25 7:36 ` Krzysztof Kozlowski
2025-03-25 13:23 ` Caleb Connolly
2025-03-26 6:57 ` Krzysztof Kozlowski
2025-03-26 10:26 ` Caleb Connolly
2025-03-28 22:45 ` David Heidelberg
2025-03-29 9:56 ` Caleb Connolly
2025-03-08 14:08 ` [PATCH v3 2/7] Input: synaptics-rmi4 - handle duplicate/unknown PDT entries David Heidelberg via B4 Relay
2025-03-10 19:10 ` Dmitry Torokhov
2025-03-11 12:22 ` Caleb Connolly
2025-04-02 18:54 ` David Heidelberg
2025-03-08 14:08 ` [PATCH v3 3/7] Input: synaptics-rmi4 - f12: use hardcoded values for aftermarket touch ICs David Heidelberg via B4 Relay
2025-03-08 14:08 ` [PATCH v3 4/7] Input: synaptics-rmi4 - f55: handle zero electrode count David Heidelberg via B4 Relay
2025-03-10 19:00 ` Dmitry Torokhov
2025-03-08 14:08 ` [PATCH v3 5/7] Input: synaptics-rmi4 - don't do unaligned reads in IRQ context David Heidelberg via B4 Relay
2025-03-08 14:08 ` [PATCH v3 6/7] Input: synaptics-rmi4 - read product ID on aftermarket touch ICs David Heidelberg via B4 Relay
2025-03-08 14:08 ` [PATCH v3 7/7] Input: synaptics-rmi4 - support fallback values for PDT descriptor bytes David Heidelberg via B4 Relay
2025-03-10 10:04 ` [PATCH v3 0/7] Subject: [PATCH v3 0/7] Input: synaptics-rmi4: add quirks for third party touchscreen controllers Caleb Connolly
2025-03-10 10:47 ` David Heidelberg [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=eb4aec7f-3c2f-4c6b-aa84-7798d7ff57a8@ixit.cz \
--to=david@ixit.cz \
--cc=Jason@zx2c4.com \
--cc=baclofen@tuta.io \
--cc=caleb.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vincent.huang@tw.synaptics.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®