From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Cong Yang <yangcong5@huaqin.corp-partner.google.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, dmitry.torokhov@gmail.com, jikos@kernel.org,
benjamin.tissoires@redhat.com, dianders@chromium.org,
hsinyi@google.com
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: HID: i2c-hid: ilitek: Introduce bindings for Ilitek ili9882t
Date: Fri, 9 Jun 2023 17:52:57 +0200 [thread overview]
Message-ID: <5ef644a6-4ea0-36b6-9abc-967dd45536ec@linaro.org> (raw)
In-Reply-To: <20230609063615.758676-2-yangcong5@huaqin.corp-partner.google.com>
On 09/06/2023 08:36, Cong Yang wrote:
> The ili9882t touch screen chip same as Elan eKTH6915 controller
> has a reset gpio. The difference is that ili9882t needs to use
> vccio-supply instead of vcc33-supply. Doug's series[1] allows panels
> and touchscreens to power on/off together, let's add a phandle for this.
>
> [1]: https://lore.kernel.org/r/20230607215224.2067679-1-dianders@chromium.org
>
> Signed-off-by: Cong Yang <yangcong5@huaqin.corp-partner.google.com>
> +
> + reset-gpios:
> + maxItems: 1
> + description: Reset GPIO.
> +
> + vccio-supply:
> + description: The 1.8V supply to the touchscreen.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - panel
> + - vccio-supply
> +
> +additionalProperties: false
My comment from previous version still applies.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-09 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 6:36 [PATCH v5 0/2] Add ili9882t bindings and timing Cong Yang
2023-06-09 6:36 ` [PATCH v5 1/2] dt-bindings: HID: i2c-hid: ilitek: Introduce bindings for Ilitek ili9882t Cong Yang
2023-06-09 15:52 ` Krzysztof Kozlowski [this message]
2023-06-09 16:00 ` Krzysztof Kozlowski
2023-06-14 11:02 ` cong yang
2023-06-09 6:36 ` [PATCH v5 2/2] HID: i2c-hid: elan: Add ili9882t timing Cong Yang
2023-06-09 16:14 ` Doug Anderson
2023-06-09 16:14 ` Doug Anderson
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=5ef644a6-4ea0-36b6-9abc-967dd45536ec@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=benjamin.tissoires@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hsinyi@google.com \
--cc=jikos@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yangcong5@huaqin.corp-partner.google.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 read-only IMAP folder(s) and NNTP newsgroup(s).