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 2/2] Input: ilitek_ts_i2c - add report id message validation
Date: Wed, 31 Jul 2024 12:00:31 -0700 [thread overview]
Message-ID: <ZqqJz4Jw8dU7uA7a@google.com> (raw)
In-Reply-To: <20231222183114.30775-3-francesco@dolcini.it>
On Fri, Dec 22, 2023 at 07:31:14PM +0100, Francesco Dolcini wrote:
> From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
>
> Ilitek touch IC driver answer to plain i2c read request, after it has
> generated an interrupt request, with a report id message starting
> with an identifier and a series of points.
> If a request is sent unsolicited by an interrupt request the answer
> do not contain this identifier.
> Add a test to discard these messages, making the driver robust to
> spurious interrupt requests.
>
> 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>
> ---
> v3: added reviewed by
> ---
> drivers/input/touchscreen/ilitek_ts_i2c.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/input/touchscreen/ilitek_ts_i2c.c b/drivers/input/touchscreen/ilitek_ts_i2c.c
> index 250133f0d68f..557362490244 100644
> --- a/drivers/input/touchscreen/ilitek_ts_i2c.c
> +++ b/drivers/input/touchscreen/ilitek_ts_i2c.c
> @@ -37,6 +37,8 @@
> #define ILITEK_TP_CMD_GET_MCU_VER 0x61
> #define ILITEK_TP_CMD_GET_IC_MODE 0xC0
>
> +#define ILITEK_TP_I2C_REPORT_ID 0x48
> +
> #define REPORT_COUNT_ADDRESS 61
> #define ILITEK_SUPPORT_MAX_POINT 40
>
> @@ -163,6 +165,11 @@ static int ilitek_process_and_report_v6(struct ilitek_ts_data *ts)
> goto err_sync_frame;
> }
>
> + if (buf[0] != ILITEK_TP_I2C_REPORT_ID) {
> + dev_err(dev, "get touch info failed. Wrong id: 0x%02X\n", buf[0]);
> + goto err_sync_frame;
Please rebase and use direct return once you fix the previous patch.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-07-31 19:00 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
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 [this message]
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=ZqqJz4Jw8dU7uA7a@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