From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v3 1/2] Input: ilitek_ts_i2c - avoid wrong input subsystem sync
Date: Wed, 31 Jul 2024 11:59:27 -0700 [thread overview]
Message-ID: <ZqqJjyo-8dJPqXe3@google.com> (raw)
In-Reply-To: <20231222183114.30775-2-francesco@dolcini.it>
Hi Francesco,
On Fri, Dec 22, 2023 at 07:31:13PM +0100, Francesco Dolcini 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")
> Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
If you are adding your sign-off you do not need to have your
reviewed-by, it is assumed that you reviewed the code you are passing
on.
> ---
> v3: added reviewed by
> ---
> drivers/input/touchscreen/ilitek_ts_i2c.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/ilitek_ts_i2c.c b/drivers/input/touchscreen/ilitek_ts_i2c.c
> index fc4e39b6651a..250133f0d68f 100644
> --- a/drivers/input/touchscreen/ilitek_ts_i2c.c
> +++ b/drivers/input/touchscreen/ilitek_ts_i2c.c
> @@ -203,9 +203,9 @@ static int ilitek_process_and_report_v6(struct ilitek_ts_data *ts)
> ilitek_touch_down(ts, id, x, y);
> }
>
> -err_sync_frame:
> input_mt_sync_frame(input);
> input_sync(input);
> +err_sync_frame:
You are not syncing the frame, so that label is wrong. If you do not
want to release the contacts just change "goto err_sync_frame" to
direct returns and remove the label.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-07-31 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 18:31 [PATCH v3 0/2] Input: ilitek_ts_i2c - Fix spurious input events Francesco Dolcini
2023-12-22 18:31 ` [PATCH v3 1/2] Input: ilitek_ts_i2c - avoid wrong input subsystem sync Francesco Dolcini
2024-07-31 18:59 ` Dmitry Torokhov [this message]
2023-12-22 18:31 ` [PATCH v3 2/2] Input: ilitek_ts_i2c - add report id message validation Francesco Dolcini
2024-07-31 19:00 ` Dmitry Torokhov
2024-07-31 9:26 ` [PATCH v3 0/2] Input: ilitek_ts_i2c - Fix spurious input events 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=ZqqJjyo-8dJPqXe3@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--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;
as well as URLs for NNTP newsgroup(s).