From: Icenowy Zheng <icenowy@aosc.io>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Bastien Nocera <hadess@hadess.net>,
Ondrej Jirman <megous@megous.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Icenowy Zheng <icenowy@aosc.io>,
Rob Herring <robh@kernel.org>
Subject: [PATCH v3 1/3] dt-bindings: input: touchscreen: add compatible string for Goodix GT917S
Date: Fri, 28 Feb 2020 09:01:44 +0800 [thread overview]
Message-ID: <20200228010146.12215-2-icenowy@aosc.io> (raw)
In-Reply-To: <20200228010146.12215-1-icenowy@aosc.io>
Goodix GT917S is a new touchscreen chip from Goodix.
Add its compatible string to the device tree binding.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Acked-by: Rob Herring <robh@kernel.org>
---
No changes in v3.
Changes in v2:
- Adapted for the new YAML-based binding.
- Added Rob's ACK.
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 d7c3262b2494..109e5ca8d6e8 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,gt917s
- goodix,gt927
- goodix,gt9271
- goodix,gt928
--
2.24.1
next prev parent reply other threads:[~2020-02-28 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 1:01 [PATCH v3 0/3] Add support for Goodix GT917S touch controller Icenowy Zheng
2020-02-28 1:01 ` Icenowy Zheng [this message]
2020-02-28 1:01 ` [PATCH v3 2/3] Input: goodix - use string-based chip ID Icenowy Zheng
2020-02-28 1:01 ` [PATCH v3 3/3] Input: goodix - Add support for Goodix GT917S Icenowy Zheng
2020-02-28 9:46 ` [PATCH v3 0/3] Add support for Goodix GT917S touch controller Bastien Nocera
2020-03-02 10:58 ` Bastien Nocera
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=20200228010146.12215-2-icenowy@aosc.io \
--to=icenowy@aosc.io \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=megous@megous.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).