From: Mark Brown <broonie@kernel.org>
To: Harald Geyer <harald@ccbib.org>
Cc: Marek Vasut <marek.vasut@gmail.com>,
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 17:56:35 +0000 [thread overview]
Message-ID: <20190218175635.GD10794@sirena.org.uk> (raw)
In-Reply-To: <E1gvNOx-0000Kc-Dc@stardust.g4.wien.funkfeuer.at>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
On Sun, Feb 17, 2019 at 03:26:39PM +0100, Harald Geyer wrote:
> If continuous operation of the regulator is important, I'd expect
> we don't touch whatever the firmware setup instead of by default
> setting all gpios to low.
> However as we can't change this now, there isn't much point in
> discussin this further.
The issue here is that the GPIO API does not allow us to read back the
state of output GPIOs (even though for almost all hardware this is
supported by the underlying hardware). With the GPIO API as it stands
it is unfortunately not possible to preserve the state, if the API were
fixed we'd preserve state.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-18 17:56 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
2019-02-18 17:56 ` Mark Brown [this message]
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=20190218175635.GD10794@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).