From: Mark Brown <broonie@kernel.org>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Harald Geyer <harald@ccbib.org>,
devicetree@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] regulator: gpio: Reword the binding document
Date: Mon, 18 Feb 2019 18:01:08 +0000 [thread overview]
Message-ID: <20190218180108.GE10794@sirena.org.uk> (raw)
In-Reply-To: <7a993282-9137-caf4-ca0b-b2c01ea9959c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
On Sun, Feb 17, 2019 at 10:57:26PM +0100, Marek Vasut wrote:
> On 2/17/19 9:00 PM, Harald Geyer wrote:
> > If this is the case, why would we need to set an initial state instead
> > of just waiting what the first consumer requests. I still don't see
> > a use case (aside from don't accidentally shut down something important
> > during probing).
> Possibly to prevent a state which might be harmful until the first
> consumer comes up. However this is rather theoretical.
This is the GPIO API restrictions again - there was a big push at one
point to try to ensure that we set the output state when requesting
output GPIOs, and a lot of the time requesting will set a state anyway
when it puts things into output mode so it may as wel be one we know
about.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-18 18:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 17:48 [PATCH] regulator: gpio: Reword the binding document marek.vasut
2019-02-16 20:20 ` Harald Geyer
2019-02-16 21:37 ` Marek Vasut
2019-02-17 14:26 ` Harald Geyer
2019-02-17 14:45 ` Marek Vasut
2019-02-17 20:00 ` Harald Geyer
2019-02-17 21:57 ` Marek Vasut
2019-02-18 10:04 ` Harald Geyer
2019-02-18 18:58 ` Marek Vasut
2019-02-18 22:18 ` Harald Geyer
2019-02-19 2:51 ` Marek Vasut
2019-02-19 10:10 ` Harald Geyer
2019-03-02 14:55 ` Marek Vasut
2019-03-03 16:07 ` Harald Geyer
2019-03-03 16:08 ` Marek Vasut
2019-02-18 18:01 ` Mark Brown [this message]
2019-02-18 17:56 ` Mark Brown
2019-02-18 17:54 ` Mark Brown
2019-02-18 9:30 ` Geert Uytterhoeven
2019-02-18 18:36 ` Marek Vasut
2019-02-18 19:21 ` Geert Uytterhoeven
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=20190218180108.GE10794@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=harald@ccbib.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=robh@kernel.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).