From: Bastien Nocera <hadess@hadess.net>
To: Icenowy Zheng <icenowy@aosc.io>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Ondrej Jirman <megous@megous.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Add support for Goodix GT917S touch controller
Date: Fri, 28 Feb 2020 10:46:06 +0100 [thread overview]
Message-ID: <c352b9e4e60a214c0f7f6b87aaf90d7fd49d5ee6.camel@hadess.net> (raw)
In-Reply-To: <20200228010146.12215-1-icenowy@aosc.io>
On Fri, 2020-02-28 at 09:01 +0800, Icenowy Zheng wrote:
> This patchset introduces support for Goodix GT917S touch controller.
>
> The major difference with other touch controllers from Goodix is that
> the ID string is no longer number-only (it contains a 'S'), so an
> additional patch is introduced for migrating the ID to a string.
>
> Icenowy Zheng (3):
> dt-bindings: input: touchscreen: add compatible string for Goodix
> GT917S
> Input: goodix - use string-based chip ID
> Input: goodix - Add support for Goodix GT917S
For the whole patchset:
Reviewed-by: Bastien Nocera <hadess@hadess.net>
Thanks!
> .../bindings/input/touchscreen/goodix.yaml | 1 +
> drivers/input/touchscreen/goodix.c | 71 +++++++++++----
> ----
> 2 files changed, 43 insertions(+), 29 deletions(-)
>
next prev parent reply other threads:[~2020-02-28 9:46 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 ` [PATCH v3 1/3] dt-bindings: input: touchscreen: add compatible string for Goodix GT917S Icenowy Zheng
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 ` Bastien Nocera [this message]
2020-03-02 10:58 ` [PATCH v3 0/3] Add support for Goodix GT917S touch controller 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=c352b9e4e60a214c0f7f6b87aaf90d7fd49d5ee6.camel@hadess.net \
--to=hadess@hadess.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=icenowy@aosc.io \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=megous@megous.com \
--cc=robh+dt@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).