From: Linus Walleij <linus.walleij@linaro.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Subject: Re: [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs
Date: Fri, 9 Jun 2017 15:53:10 +0200 [thread overview]
Message-ID: <CACRpkdY2ECd6e=kE3HWOP3xJFUm6VbrF+0Ds10ax7XsybRkQLA@mail.gmail.com> (raw)
In-Reply-To: <20170604101049.4592-1-uwe@kleine-koenig.org>
On Sun, Jun 4, 2017 at 12:10 PM, Uwe Kleine-König <uwe@kleine-koenig.org> wrote:
> - 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.
> +- output-inactive: A property specifying to set the GPIO direction as output
> + using the inactive level as value.
> +- output-active: A property specifying to set the GPIO direction as output
> + using the active level as value.
> +- output-low A deprecated alias for "output-inactive".
> +- output-high A deprecated alias for "output-active".
Wouldn't "output-asserted" / "output-deasserted" be more to the point?
If the majority prefers "active" I can live with that too.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-06-09 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 10:10 [RFC PATCH] gpio: use "output-active" and "output-inactive" for gpio-hogs Uwe Kleine-König
[not found] ` <20170604101049.4592-1-uwe-rXY34ruvC2xidJT2blvkqNi2O/JbrIOy@public.gmane.org>
2017-06-08 22:33 ` Rob Herring
2017-06-09 7:10 ` Nikita Yushchenko
2017-06-09 14:42 ` Linus Walleij
2017-06-09 13:53 ` Linus Walleij [this message]
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='CACRpkdY2ECd6e=kE3HWOP3xJFUm6VbrF+0Ds10ax7XsybRkQLA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andrew.smirnov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-gpio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nikita.yoush@cogentembedded.com \
--cc=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.org \
/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).