From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
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: Thu, 8 Jun 2023 08:50:27 +0200 [thread overview]
Message-ID: <CAMuHMdWu4KZbBkvEofUV2wuA1g2S=XHHM3RUN1cNrcZBkhsPZA@mail.gmail.com> (raw)
In-Reply-To: <4491320.LvFx2qVVIh@steina-w>
Hi Alexander,
On Wed, May 31, 2023 at 8:19 AM Alexander Stein
<alexander.stein@ew.tq-group.com> wrote:
> Am Dienstag, 30. Mai 2023, 17:19:45 CEST schrieb Uwe Kleine-König:
> > 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(-)
> >
> > diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt
> > b/Documentation/devicetree/bindings/gpio/gpio.txt index
> > d82c32217fff..2f037bbd3ffa 100644
> > --- a/Documentation/devicetree/bindings/gpio/gpio.txt
> > +++ b/Documentation/devicetree/bindings/gpio/gpio.txt
> > @@ -209,15 +209,21 @@ Required properties:
> > - gpios: Store the GPIO information (id, flags, ...) for each GPIO to
> > affect. Shall contain an integer multiple of the number of
> cells
> > specified in its parent node (GPIO controller node).
> > +
> > 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-inactive: 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-active: A property specifying to set the GPIO direction as
> > output + with the active value.
>
> I know this is essentially just renaming currently existing properties.
> But these mutual exclusive (boolean) properties make it impossible to change
> them in DT overlay. Any ideas how to support changing the output level onGPIO
> hogs in DT overlay?
That's a good point. And despite it not working, people do try to
stick e.g. /delete-node/ in .dtso files...
I assume you can sort of remove the existing hog subnode by adding
status = "disabled" in the DT overlay, and adding a new subnode to
configure the new output level?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-06-08 6:50 UTC|newest]
Thread overview: 20+ 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 [this message]
2023-06-07 21:09 ` Rob Herring
2023-05-30 15:19 ` [PATCH v2 2/2] gpio: use "active" and "inactive" instead of "high" and "low" for output hogs Uwe Kleine-König
2023-05-30 21:51 ` Andy Shevchenko
2023-05-31 6:58 ` Uwe Kleine-König
2023-05-31 9:51 ` Andy Shevchenko
2023-05-31 10:06 ` Uwe Kleine-König
2023-05-31 12:21 ` Andy Shevchenko
2023-05-31 12:23 ` Andy Shevchenko
2023-05-30 15:51 ` [PATCH v2 0/2] gpio: introduce hog properties with less ambiguity 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='CAMuHMdWu4KZbBkvEofUV2wuA1g2S=XHHM3RUN1cNrcZBkhsPZA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=alexander.stein@ew.tq-group.com \
--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=robh+dt@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).