From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-input@vger.kernel.org, Nick Dyer <nick@shmanahar.org>,
Stephan Gerhold <stephan@gerhold.net>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3 v2] Input: atmel_mxt_ts - Convert bindings to YAML and extend
Date: Sun, 22 Nov 2020 22:48:44 -0800 [thread overview]
Message-ID: <20201123064844.GA2034289@dtor-ws> (raw)
In-Reply-To: <20201104153032.1387747-2-linus.walleij@linaro.org>
On Wed, Nov 04, 2020 at 04:30:31PM +0100, Linus Walleij wrote:
> This converts the Armel MXT touchscreen bindings to YAML
> format and extends them with the following two properties:
>
> - vdda-supply: the optional analog supply voltage
> - vdd-supply: the optional digital supply voltage
>
> I also explained about the reset-gpios property that this
> better be flagged as active high (0) despite actually
> being active low, because all current device trees and
> drivers assume that this is the case and will actively
> drive the line low to assert RESET.
>
> Tested the schema with all in-tree users and they verify
> fine.
>
> Cc: Nick Dyer <nick@shmanahar.org>
> Cc: Stephan Gerhold <stephan@gerhold.net>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2020-11-23 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 15:30 [PATCH 1/3 v2] Input: atmel_mxt_ts - Fix up inverted RESET handler Linus Walleij
2020-11-04 15:30 ` [PATCH 2/3 v2] Input: atmel_mxt_ts - Convert bindings to YAML and extend Linus Walleij
2020-11-09 17:30 ` Rob Herring
2020-11-23 6:48 ` Dmitry Torokhov [this message]
2020-11-04 15:30 ` [PATCH 3/3 v2] Input: atmel_mxt_ts - Support regulator supplies Linus Walleij
2020-11-23 6:48 ` Dmitry Torokhov
2020-11-04 15:59 ` [PATCH 1/3 v2] Input: atmel_mxt_ts - Fix up inverted RESET handler Philippe Schenker
2020-11-05 8:09 ` Krzysztof Kozlowski
2020-11-23 6:48 ` Dmitry Torokhov
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=20201123064844.GA2034289@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=nick@shmanahar.org \
--cc=stephan@gerhold.net \
/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).