From: Francesco Dolcini <francesco@dolcini.it>
To: Emanuele Ghidoli <ghidoliemanuele@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Joe Hung <joe_hung@ilitek.com>
Subject: Re: [PATCH v2 1/2] Input: ilitek_ts_i2c - avoid wrong input subsystem sync
Date: Tue, 26 Sep 2023 10:15:38 +0200 [thread overview]
Message-ID: <ZRKTKrH/75/++bVE@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20230920074650.922292-2-ghidoliemanuele@gmail.com>
On Wed, Sep 20, 2023 at 09:46:49AM +0200, Emanuele Ghidoli wrote:
> From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
>
> For different reasons i2c transaction may fail or
> report id message content may be wrong.
> Avoid sync the input subsystem if message cannot be parsed.
> An input subsystem sync without points is interpreted as
> "nothing is touching the screen" while normally this is not the case.
>
> Fixes: 42370681bd46 ("Input: Add support for ILITEK Lego Series")
> Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Francesco
next prev parent reply other threads:[~2023-09-26 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 7:46 [PATCH v2 0/2] Input: ilitek_ts_i2c - Fix spurious input events Emanuele Ghidoli
2023-09-20 7:46 ` [PATCH v2 1/2] Input: ilitek_ts_i2c - avoid wrong input subsystem sync Emanuele Ghidoli
2023-09-26 8:15 ` Francesco Dolcini [this message]
2023-09-20 7:46 ` [PATCH v2 2/2] Input: ilitek_ts_i2c - add report id message validation Emanuele Ghidoli
2023-09-26 8:14 ` Francesco Dolcini
2023-09-20 7:54 ` [PATCH v2 0/2] Input: ilitek_ts_i2c - Fix spurious input events Emanuele Ghidoli
2023-10-22 15:13 ` Francesco Dolcini
2023-11-21 14:00 ` Francesco Dolcini
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=ZRKTKrH/75/++bVE@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=dmitry.torokhov@gmail.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=ghidoliemanuele@gmail.com \
--cc=joe_hung@ilitek.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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