From: Bastien Nocera <hadess@hadess.net>
To: Yannick Fertre <yannick.fertre@st.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Benjamin Gaignard <benjamin.gaignard@st.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: touchscreen: goodix: support of gt9147
Date: Sat, 29 Feb 2020 20:06:00 +0100 [thread overview]
Message-ID: <409fce621796948d630e1988e3f8a178e8803344.camel@hadess.net> (raw)
In-Reply-To: <1582898271-21073-1-git-send-email-yannick.fertre@st.com>
On Fri, 2020-02-28 at 14:57 +0100, Yannick Fertre wrote:
> Add support for it by adding compatible.
> The chip data on GT9147 is similar to GT912, like
> - config data register has 0x8047 address
> - config data register max len is 240
> - config data checksum has 8-bit
>
> Signed-off-by: Yannick Fertre <yannick.fertre@st.com>
> ---
> Documentation/devicetree/bindings/input/touchscreen/goodix.yaml | 1
> +
> 1 file changed, 1 insertion(+)
>
> diff --git
> a/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> b/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> index d7c3262..9f65d67 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> @@ -21,6 +21,7 @@ properties:
> - goodix,gt911
> - goodix,gt9110
> - goodix,gt912
> + - goodix,gt9147
It's not going to be much help if you don't have a driver patch that
adds that string to the OF match table. And please CC: the driver
maintainer as well.
> - goodix,gt927
> - goodix,gt9271
> - goodix,gt928
prev parent reply other threads:[~2020-02-29 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 13:57 [PATCH] dt-bindings: touchscreen: goodix: support of gt9147 Yannick Fertre
2020-02-29 19:06 ` Bastien Nocera [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=409fce621796948d630e1988e3f8a178e8803344.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@st.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).