From: Rob Herring <robh@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
kernel@pengutronix.de,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Kent Gibson <warthog618@gmail.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: gpio: introduce hog properties with less ambiguity
Date: Wed, 7 Jun 2023 15:09:59 -0600 [thread overview]
Message-ID: <20230607210959.GA4013738-robh@kernel.org> (raw)
In-Reply-To: <20230530151946.2317748-2-u.kleine-koenig@pengutronix.de>
On Tue, May 30, 2023 at 05:19:45PM +0200, Uwe Kleine-König wrote:
> For active low lines the semantic of output-low and output-high is hard
> to grasp because there is a double negation involved and so output-low
> is actually a request to drive the line high (aka inactive).
>
> So introduce output-inactive and output-active with the same semantic as
> output-low and output-high respectively have today, but with a more
> sensible name.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Documentation/devicetree/bindings/gpio/gpio.txt | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
Please add this to the schemas in dtschema. Everything in gpio.txt
should be removed. If that hasn't been done, it's because what's here
needs to be relicensed. Looks like you need TI's and Geert's permission
for the hog part. Anything from Grant, Linaro or NVIDIA I've gotten
permission for as well.
Rob
next prev parent reply other threads:[~2023-06-07 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 15:19 [PATCH v2 0/2] gpio: introduce hog properties with less ambiguity Uwe Kleine-König
2023-05-30 15:19 ` [PATCH v2 1/2] dt-bindings: " Uwe Kleine-König
2023-05-30 22:20 ` Conor Dooley
2023-05-31 7:03 ` Uwe Kleine-König
2023-05-31 9:37 ` Conor Dooley
2023-05-31 6:18 ` Alexander Stein
2023-05-31 7:01 ` Uwe Kleine-König
2023-06-08 6:50 ` Geert Uytterhoeven
2023-06-07 21:09 ` Rob Herring [this message]
2023-05-30 15:51 ` [PATCH v2 0/2] " Kent Gibson
2023-05-30 19:15 ` Bartosz Golaszewski
2023-05-31 0:55 ` Kent Gibson
2023-05-31 8:15 ` Bartosz Golaszewski
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=20230607210959.GA4013738-robh@kernel.org \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=warthog618@gmail.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 NNTP newsgroup(s).