From: Hans de Goede <hansg@kernel.org>
To: Gianluca Boiano <morf3089@gmail.com>
Cc: dmitry.torokhov@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] input: touchscreen: novatek-nvt-ts: Add support for NT36672A e7t variant
Date: Wed, 21 Jan 2026 13:04:17 +0100 [thread overview]
Message-ID: <b4113f8c-0fbd-4a96-9cf6-9675f837ac91@kernel.org> (raw)
In-Reply-To: <20260120193600.1089458-2-morf3089@gmail.com>
Hi Gianluca,
On 20-Jan-26 20:36, Gianluca Boiano wrote:
> Add support for the Novatek NT36672A touchscreen variant found on the
> Xiaomi Redmi Note 6 Pro (tulip) which uses a different wake_type value
> (0x02 instead of 0x01).
>
> The touchscreen was failing to initialize with error -5 due to the
> wake_type parameter mismatch during probe. This adds a new chip data
> structure for the e7t variant with the correct wake_type value.
>
> Closes: https://github.com/sdm660-mainline/linux/issues/155
> Signed-off-by: Gianluca Boiano <morf3089@gmail.com>
Thank you for your patch.
I don't think that adding a new compatible + a new nvt_ts_i2c_chip_data
struct is the right approach here.
I guess the wake-type byte simply encodes some IRQ config settings,
which may indeed be different in different applications using
the some touchscreen controller.
Instead of adding a new compatible my suggestion to fix this would
be to simply drop the wake_type check as well as drop the wake_type
member from struct nvt_ts_i2c_chip_data.
This way you can fix the driver not working on the Xiaomi Redmi
Note 6 Pro by removing code instead of adding code :)
And supporting other models also becomes easier.
Regards,
Hans
> ---
> drivers/input/touchscreen/novatek-nvt-ts.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/input/touchscreen/novatek-nvt-ts.c b/drivers/input/touchscreen/novatek-nvt-ts.c
> index 44b58e0dc1ad..b1c379d87de0 100644
> --- a/drivers/input/touchscreen/novatek-nvt-ts.c
> +++ b/drivers/input/touchscreen/novatek-nvt-ts.c
> @@ -323,9 +323,15 @@ static const struct nvt_ts_i2c_chip_data nvt_nt36672a_ts_data = {
> .chip_id = 0x08,
> };
>
> +static const struct nvt_ts_i2c_chip_data nvt_nt36672a_e7t_ts_data = {
> + .wake_type = 0x02,
> + .chip_id = 0x08,
> +};
> +
> static const struct of_device_id nvt_ts_of_match[] = {
> { .compatible = "novatek,nt11205-ts", .data = &nvt_nt11205_ts_data },
> { .compatible = "novatek,nt36672a-ts", .data = &nvt_nt36672a_ts_data },
> + { .compatible = "novatek,nt36672a-e7t-ts", .data = &nvt_nt36672a_e7t_ts_data },
> { }
> };
> MODULE_DEVICE_TABLE(of, nvt_ts_of_match);
> @@ -333,6 +339,7 @@ MODULE_DEVICE_TABLE(of, nvt_ts_of_match);
> static const struct i2c_device_id nvt_ts_i2c_id[] = {
> { "nt11205-ts", (unsigned long) &nvt_nt11205_ts_data },
> { "nt36672a-ts", (unsigned long) &nvt_nt36672a_ts_data },
> + { "nt36672a-e7t-ts", (unsigned long) &nvt_nt36672a_e7t_ts_data },
> { }
> };
> MODULE_DEVICE_TABLE(i2c, nvt_ts_i2c_id);
next prev parent reply other threads:[~2026-01-21 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 19:35 [PATCH 1/2] dt-bindings: input: novatek,nvt-ts: Add nt36672a-e7t-ts compatible Gianluca Boiano
2026-01-20 19:36 ` [PATCH 2/2] input: touchscreen: novatek-nvt-ts: Add support for NT36672A e7t variant Gianluca Boiano
2026-01-21 8:18 ` Krzysztof Kozlowski
2026-01-21 12:04 ` Hans de Goede [this message]
2026-01-22 0:09 ` Gianluca Boiano
2026-01-21 8:18 ` [PATCH 1/2] dt-bindings: input: novatek,nvt-ts: Add nt36672a-e7t-ts compatible Krzysztof Kozlowski
2026-01-21 21:41 ` [PATCH v2 0/2] input: touchscreen: novatek-nvt-ts: Add NT36672A e7t variant Gianluca Boiano
2026-01-21 21:41 ` [PATCH v2 1/2] dt-bindings: input: novatek,nvt-ts: Add nt36672a-e7t-ts compatible Gianluca Boiano
2026-01-21 22:10 ` Rob Herring
2026-01-21 21:41 ` [PATCH v2 2/2] input: touchscreen: novatek-nvt-ts: Add support for NT36672A e7t variant Gianluca Boiano
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=b4113f8c-0fbd-4a96-9cf6-9675f837ac91@kernel.org \
--to=hansg@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morf3089@gmail.com \
--cc=robh@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