From: Mark Brown <broonie@kernel.org>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Question about fixed regulator DT properties
Date: Wed, 26 Nov 2014 17:53:04 +0000 [thread overview]
Message-ID: <20141126175304.GM7712@sirena.org.uk> (raw)
In-Reply-To: <54760D6A.9080306@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Wed, Nov 26, 2014 at 07:27:06PM +0200, Vladimir Zapolskiy wrote:
> On 25.11.2014 14:17, Mark Brown wrote:
> b) "regulator-boot-on" does not mean that the regulator is controlled by
> bootloader or firmware exclusively.
That's correct...
> >>> Should documentation be updated to reflect "regulator-boot-on" role that
> >>> a regulator is re-enabled by the kernel?
> > I'm confused about this. That's the sole purpose of the flag and as far
> > as I can tell it's what the documentation says.
> Documentation/devicetree/bindings/regulator/regulator.txt says:
> - regulator-boot-on: bootloader/firmware enabled regulator
> I would suggest to add Linux kernel to that list of regulator
> controllers, if it is the intention. In its current state the
> documentation makes an impression that "regulator-boot-on" property
> instructs the kernel to ignore regulator setup, since it is already
> controlled by bootloader or firmware.
No, not at all. It's referring to the state when Linux starts.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-26 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 15:00 Question about Vladimir Zapolskiy
2014-11-19 14:38 ` Question about fixed regulator DT properties Vladimir Zapolskiy
2014-11-25 12:17 ` Mark Brown
2014-11-26 17:27 ` Vladimir Zapolskiy
2014-11-26 17:53 ` Mark Brown [this message]
2014-11-26 19:13 ` Vladimir Zapolskiy
2014-11-26 19:20 ` Mark Brown
2014-11-26 19:57 ` Vladimir Zapolskiy
2014-11-26 20:36 ` Mark Brown
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=20141126175304.GM7712@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vladimir_zapolskiy@mentor.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
all inboxes | Powered by JetHome®