From: David Heidelberg <david@ixit.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Henrik Rydberg <rydberg@bitmath.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Petr Hodina <petr.hodina@protonmail.com>,
linux-input@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
phone-devel@vger.kernel.org, stable@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Abel Vesa <abel.vesa@oss.qualcomm.com>,
Miro Mraz <mraz.miro@seznam.cz>
Subject: Re: [PATCH v8 0/5] Input: support for STM FTS5
Date: Mon, 2 Nov 2026 10:40:49 +0100 [thread overview]
Message-ID: <1eca9b3f-3b61-4663-b52f-4e2dba38ca21@ixit.cz> (raw)
In-Reply-To: <4590302cb7f26ea6173018f5d7083977@gmail.com>
On 02/11/2026 04:18, Dmitry Torokhov wrote:
> Hi David,
>
> On Fri, Sep 25, 2026 at 11:22:18PM +0200, David Heidelberg wrote:
>> Used on various phones. Minimal viable driver.
>>
>> Includes device-tree enabling touchscreen on Pixel 3.
>> Also, tested on Xiaomi Mi 8 (device-tree is not yet inside the mainline).
>
> I applied patches 1 through 4 (leaving patch 5/5 for the Qualcomm SoC
> tree) with a few small adjustments folded in:
>
> - In patch 1/5, added a missing trailing newline to the reset timeout
> error message and fixed a typo in the comment in stmfts_power_on().
> - In patch 3/5, wrapped "const: st,stmfts5" under "contains:" in the
> allOf condition so the check keeps working if a fallback compatible
> is added later.
> - In patch 4/5:
> - moved ABS_MT_TOOL_TYPE setup from stmfts_setup_input() to
> stmfts5_setup_input() since FTS4 does not report tool types;
> - dropped the undocumented "stylus-enabled" property check so stylus
> contacts unconditionally report MT_TOOL_PEN;
> - checked X and Y resolutions independently before applying the
> 10 units/mm fallback;
> - added a check for !sdata->ops in stmfts_probe();
> - fixed the GPIO name in the "mode-switch" error message and a couple
> of minor comment/log formatting nits.
>
> I will also send out a few separate follow-up patches shortly: one
> teaching touchscreen_parse_properties() to parse touchscreen-x-mm and
> touchscreen-y-mm directly so drivers do not have to open-code resolution
> handling, plus a few fixes in stmfts (not aborting FIFO parsing early on
> non-touch events, validating the 4-bit slot ID against
> STMFTS_MAX_FINGERS, and switching coordinate reporting to
> touchscreen_report_pos() so axis inversion and swapping properties are
> honored).
Hello Dmitry.
Thank you so much for improvements and merging stmfts5, I'll pick up the patches
back to my sdm845 tree so we can apply followup improvements easily :)
David
>
> Thanks.
>
prev parent reply other threads:[~2026-11-02 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 21:22 David Heidelberg via B4 Relay
2026-09-25 21:22 ` [PATCH v8 1/5] Input: stmfts - wait for controller ready after reset David Heidelberg via B4 Relay
2026-09-25 22:18 ` Dmitry Torokhov
2026-09-25 21:22 ` [PATCH v8 2/5] dt-bindings: input: touchscreen: st,stmfts: Improve example David Heidelberg via B4 Relay
2026-09-29 8:28 ` Krzysztof Kozlowski
2026-09-25 21:22 ` [PATCH v8 3/5] dt-bindings: input: touchscreen: st,stmfts: Introduce STM FTS5 David Heidelberg via B4 Relay
2026-09-29 8:40 ` Krzysztof Kozlowski
2026-09-25 21:22 ` [PATCH v8 4/5] Input: stmfts - support FTS5 David Heidelberg via B4 Relay
2026-09-25 21:22 ` [PATCH v8 5/5] arm64: dts: qcom: sdm845-google: Add STM FTS touchscreen support David Heidelberg via B4 Relay
2026-11-02 3:18 ` [PATCH v8 0/5] Input: support for STM FTS5 Dmitry Torokhov
2026-11-02 9:40 ` 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=1eca9b3f-3b61-4663-b52f-4e2dba38ca21@ixit.cz \
--to=david@ixit.cz \
--cc=abel.vesa@oss.qualcomm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dmitry.torokhov@gmail.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mraz.miro@seznam.cz \
--cc=petr.hodina@protonmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rydberg@bitmath.org \
--cc=stable@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
all inboxes | Powered by JetHome®