From: Dmitry Osipenko <digetx@gmail.com>
To: Jiada Wang <jiada_wang@mentor.com>,
dmitry.torokhov@gmail.com, robh+dt@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com
Cc: nick@shmanahar.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
erosca@de.adit-jv.com, andrew_gabbasov@mentor.com
Subject: Re: [PATCH v2 3/3] ARM: tegra: add mXT1386 compatible
Date: Sat, 26 Sep 2020 00:02:06 +0300 [thread overview]
Message-ID: <60afbb5b-0890-a0b0-2682-d5302e8e9130@gmail.com> (raw)
In-Reply-To: <20200925135257.21138-4-jiada_wang@mentor.com>
25.09.2020 16:52, Jiada Wang пишет:
> Add mXT1386 compatible for "touchscreen@4c".
>
> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
> ---
> arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
> index 2d683c9a1a5d..7915b6e9190e 100644
> --- a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
> +++ b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
> @@ -428,7 +428,7 @@
> };
>
> touchscreen@4c {
> - compatible = "atmel,maxtouch";
> + compatible = "atmel,mXT1386", "atmel,maxtouch";
> reg = <0x4c>;
>
> atmel,cfg_name = "maxtouch-acer-iconia-tab-a500.cfg";
>
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
Tested-by: Dmitry Osipenko <digetx@gmail.com>
prev parent reply other threads:[~2020-09-25 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 13:52 [PATCH v2 0/3] implement I2C retries for mXT1368 Jiada Wang
2020-09-25 13:52 ` [PATCH v2 1/3] dt-bindings: input: atmel: add compatible for mXT1386 Jiada Wang
2020-09-25 21:01 ` Dmitry Osipenko
2020-09-28 6:59 ` Thierry Reding
2020-09-30 14:22 ` Wang, Jiada
2020-09-25 13:52 ` [PATCH v2 2/3] Input: atmel_mxt_ts - implement I2C retries for mXT1368 Jiada Wang
2020-09-25 21:01 ` Dmitry Osipenko
2020-09-25 13:52 ` [PATCH v2 3/3] ARM: tegra: add mXT1386 compatible Jiada Wang
2020-09-25 21:02 ` Dmitry Osipenko [this message]
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=60afbb5b-0890-a0b0-2682-d5302e8e9130@gmail.com \
--to=digetx@gmail.com \
--cc=andrew_gabbasov@mentor.com \
--cc=dmitry.torokhov@gmail.com \
--cc=erosca@de.adit-jv.com \
--cc=jiada_wang@mentor.com \
--cc=jonathanh@nvidia.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nick@shmanahar.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).