From: Daniel Golle <daniel@makrotopia.org>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Daniel Golle" <daniel@makrotopia.org>,
"Hendrik Noack" <hendrik-noack@gmx.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Ferass El Hafidi" <funderscore@postmarketos.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Oleh Kuzhylnyi" <kuzhylol@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Chad Monroe <chad@monroe.io>, John Crispin <john@phrozen.org>
Subject: [PATCH v2 0/5] Input: hynitron-cst816x: axes, gesture keys and panel power
Date: Fri, 2 Oct 2026 13:47:08 +0100 [thread overview]
Message-ID: <cover.1790944534.git.daniel@makrotopia.org> (raw)
This series improves the hynitron-cst816x touchscreen driver. It makes
the driver respect the common touchscreen axis properties, which are
now documented in the binding as well, it keeps gesture keys from
getting stuck, and it lets the controller follow the panel it is
mounted on.
The gesture key is reported with the controller's touch flag as its
value, so the key stays pressed once the controller stops reporting
the gesture code. The controller has no lift event to offer, so the
keys are now released on the first report carrying no gesture code, or
40 ms after the last one that carried a code, whichever comes first.
Boards which mount the controller on the panel feed it from the
panel's rail, so the reset and the interrupt now wait for the panel to
be prepared, which the common 'panel' phandle asks for.
Changes since v1:
- the binding allows touchscreen-min-x/y, touchscreen-size-x/y and
touchscreen-fuzz-x/y as well, which touchscreen_parse_properties()
already honours; the 240x240 default is unchanged
- the binding allows the 'panel' phandle, and patch 5 is new: it
follows the panel's power sequence
- the binding commit message carries a justification (Conor Dooley)
- keycodes above KEY_MAX are rejected, which keeps the gesture key
lookup inside the input core's key bitmap (Sashiko AI review)
- the timed release is skipped when the interrupt handler re-armed the
timer while the timer callback waited for the lock (Sashiko AI
review)
- the Sashiko AI review also asked about additionalProperties next to
a $ref, which stays, as this binding allows a subset of
touchscreen.yaml (writing-schema.rst)
Link: https://lore.kernel.org/r/cover.1790851590.git.daniel@makrotopia.org
Daniel Golle (5):
dt-bindings: input: touchscreen: hynitron,cst816x: axes and panel
Input: hynitron-cst816x: respect touchscreen DT properties
Input: hynitron-cst816x: release gesture keys
Input: hynitron-cst816x: time out gesture key release
Input: hynitron-cst816x: power sequence with the panel
.../input/touchscreen/hynitron,cst816x.yaml | 16 ++
drivers/input/touchscreen/Kconfig | 2 +
drivers/input/touchscreen/hynitron-cst816x.c | 182 +++++++++++++++---
3 files changed, 171 insertions(+), 29 deletions(-)
base-commit: 6474fa070f2b8013b4b87350b775b8c3be6e8aac
--
2.55.0
next reply other threads:[~2026-10-02 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 12:47 Daniel Golle [this message]
2026-10-02 12:47 ` [PATCH v2 1/5] dt-bindings: input: touchscreen: hynitron,cst816x: axes and panel Daniel Golle
2026-10-04 7:24 ` Krzysztof Kozlowski
2026-10-04 7:29 ` Daniel Golle
2026-10-04 7:33 ` Krzysztof Kozlowski
2026-10-02 12:47 ` [PATCH v2 2/5] Input: hynitron-cst816x: respect touchscreen DT properties Daniel Golle
2026-10-04 20:30 ` Oleh Kuzhylnyi
2026-10-02 12:47 ` [PATCH v2 3/5] Input: hynitron-cst816x: release gesture keys Daniel Golle
2026-10-04 21:36 ` Oleh Kuzhylnyi
[not found] ` <XXX-PASTE-MESSAGE-ID-OF-OLEHS-MAIL>
2026-10-05 17:07 ` Daniel Golle
2026-10-02 12:48 ` [PATCH v2 4/5] Input: hynitron-cst816x: time out gesture key release Daniel Golle
2026-10-02 12:48 ` [PATCH v2 5/5] Input: hynitron-cst816x: power sequence with the panel Daniel Golle
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=cover.1790944534.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=arnd@arndb.de \
--cc=chad@monroe.io \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=funderscore@postmarketos.org \
--cc=hendrik-noack@gmx.de \
--cc=john@phrozen.org \
--cc=krzk+dt@kernel.org \
--cc=kuzhylol@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.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®