mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Heidelberg <david@ixit.cz>, Andi Shyti <andi.shyti@kernel.org>
Cc: Petr Hodina <petr.hodina@protonmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Input: stmfts - event parsing and coordinate reporting fixes
Date: Tue,  3 Nov 2026 14:58:40 -0800	[thread overview]
Message-ID: <20261103225923.3892612-1-dmitry.torokhov@gmail.com> (raw)

This series addresses a few issues in the stmfts touchscreen driver's
event handling and coordinate reporting for both FTS4 and FTS5
controllers.

First, it updates the FIFO event parsing loops so that non-touch events
(such as controller-ready, status, user-report, or debug events) do not
abort processing of subsequent touch events already read in the same
FIFO batch. Next, it validates the 4-bit slot ID extracted from event
payloads against STMFTS_MAX_FINGERS before calling input_mt_slot().
Finally, it switches contact and hover coordinate reporting to use
touchscreen_report_pos() so that axis inversion and swapping properties
parsed by touchscreen_parse_properties() are respected.

Dmitry Torokhov (3):
  Input: stmfts - do not abort event parsing on non-touch events
  Input: stmfts - validate slot ID in touch events
  Input: stmfts - use touchscreen_report_pos() for coordinates

 drivers/input/touchscreen/stmfts.c | 49 ++++++++++++++++++++++--------
 1 file changed, 36 insertions(+), 13 deletions(-)

-- 
2.56.0.385.gac671c819a-goog


             reply	other threads:[~2026-11-03 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 22:58 Dmitry Torokhov [this message]
2026-11-03 22:58 ` [PATCH 1/3] Input: stmfts - do not abort event parsing on non-touch events Dmitry Torokhov
2026-11-03 22:58 ` [PATCH 2/3] Input: stmfts - validate slot ID in touch events Dmitry Torokhov
2026-11-03 22:58 ` [PATCH 3/3] Input: stmfts - use touchscreen_report_pos() for coordinates Dmitry Torokhov

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=20261103225923.3892612-1-dmitry.torokhov@gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=david@ixit.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petr.hodina@protonmail.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®