From: Kent Gibson <warthog618@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org, kernel@pengutronix.de,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: gpio: introduce hog properties with less ambiguity
Date: Tue, 4 May 2021 10:55:46 +0800 [thread overview]
Message-ID: <20210504025546.GA13356@sol> (raw)
In-Reply-To: <20210503210526.43455-1-u.kleine-koenig@pengutronix.de>
On Mon, May 03, 2021 at 11:05:26PM +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).
>
+1 on clarifying the naming.
> 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.
>
You use active/inactive here, but then asserted/deasserted in the patch.
My preference would be the active/inactive, which has more of a level
feel, over the asserted/deasserted which feels more like an edge.
And you still use active/inactive in the descriptions, so now we have all
three naming schemes in the mix.
What made you change?
Cheers,
Kent.
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
>
> I already sent this patch back in July and Linus (Walleij) liked the
> patch but asked for an implementation. For that I added the second patch
> now.
>
> Best regards
> Uwe
>
> Documentation/devicetree/bindings/gpio/gpio.txt | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt b/Documentation/devicetree/bindings/gpio/gpio.txt
> index a8895d339bfe..1061c346a619 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio.txt
> +++ b/Documentation/devicetree/bindings/gpio/gpio.txt
> @@ -196,11 +196,16 @@ Only one of the following properties scanned in the order shown below.
> This means that when multiple properties are present they will be searched
> in the order presented below and the first match is taken as the intended
> configuration.
> -- input: A property specifying to set the GPIO direction as input.
> -- output-low A property specifying to set the GPIO direction as output with
> - the value low.
> -- output-high A property specifying to set the GPIO direction as output with
> - the value high.
> +- input: A property specifying to set the GPIO direction as input.
> +- output-deasserted: A property specifying to set the GPIO direction as output
> + with the inactive value (depending on the line's polarity,
> + which is active-high by default)
> +- output-asserted: A property specifying to set the GPIO direction as output
> + with the active value.
> +
> +For backwards compatibility "output-low" and "output-high" should be supported
> +as aliases for "output-deasserted" and "output-asserted" respectively. Their
> +usage is misleading for active-low outputs, so their use is discouraged.
>
> Optional properties:
> - line-name: The GPIO label name. If not present the node name is used.
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-05-04 2:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 21:05 [PATCH 1/2] dt-bindings: gpio: introduce hog properties with less ambiguity Uwe Kleine-König
2021-05-03 21:05 ` [PATCH 2/2] gpio: use "asserted" and "deasserted" instead of "high" and "low" Uwe Kleine-König
2021-05-04 2:55 ` Kent Gibson [this message]
2021-05-04 9:14 ` [PATCH 1/2] dt-bindings: gpio: introduce hog properties with less ambiguity Uwe Kleine-König
2021-05-04 10:24 ` Kent Gibson
2021-05-04 10:56 ` Uwe Kleine-König
2021-05-06 12:35 ` Linus Walleij
2021-05-06 15:34 ` Kent Gibson
2021-05-06 12:37 ` Linus Walleij
2021-05-06 18:31 ` Rob Herring
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=20210504025546.GA13356@sol \
--to=warthog618@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.