From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, Joe Hung <joe_hung@ilitek.com>,
devicetree@vger.kernel.org, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] dt-bindings: input: touchscreen: ilitek_ts_i2c: Absorb ili2xxx bindings
Date: Wed, 16 Jun 2021 12:02:43 -0600 [thread overview]
Message-ID: <20210616180243.GA3624758@robh.at.kernel.org> (raw)
In-Reply-To: <c381ee2526074e02b6058c489f85cfdaee582713.1623419587.git.geert+renesas@glider.be>
On Fri, 11 Jun 2021 15:54:27 +0200, Geert Uytterhoeven wrote:
> While Linux uses a different driver, the Ilitek
> ILI210x/ILI2117/ILI2120/ILI251x touchscreen controller Device Tree
> binding documentation is very similar.
>
> - Drop the fixed reg value, as some controllers use a different
> address,
> - Make reset-gpios optional, as it is not always wired.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../bindings/input/ilitek,ili2xxx.txt | 27 -------------------
> .../input/touchscreen/ilitek_ts_i2c.yaml | 7 +++--
> 2 files changed, 5 insertions(+), 29 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/input/ilitek,ili2xxx.txt
>
One driver or 2, I don't care from a binding perspective if sharing
works.
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-06-16 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 13:54 [PATCH] dt-bindings: input: touchscreen: ilitek_ts_i2c: Absorb ili2xxx bindings Geert Uytterhoeven
2021-06-11 14:20 ` Marek Vasut
2021-06-11 18:23 ` Geert Uytterhoeven
2021-06-11 18:32 ` Dmitry Torokhov
2021-06-11 21:49 ` Marek Vasut
2021-06-12 5:52 ` Joe Hung (洪銘陽)
2021-06-13 19:43 ` Marek Vasut
2021-06-16 18:02 ` Rob Herring [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=20210616180243.GA3624758@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=joe_hung@ilitek.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marex@denx.de \
--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).