From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Liam Girdwood <lrg@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: boot_on regulator constraint vs. regulator-boot-on DT property
Date: Thu, 21 Jun 2012 10:12:03 +0100 [thread overview]
Message-ID: <20120621091202.GF4037@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FE27835.5070705@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Wed, Jun 20, 2012 at 07:26:13PM -0600, Stephen Warren wrote:
> On 06/20/2012 05:46 PM, Mark Brown wrote:
> > There's no great inconsistency between the two, this is only
> > supposed to be used for supplies which are already enabled on boot
> Hmm. Perhaps I was misreading machine.h, and "when the system is
> initially started" refers to the first firmware start, rather than
> when /Linux/ starts. If so, then yes I can see it isn't really
> inconsistent.
Yes, that's the idea - it's for telling the core that everything has
been done on the basis that the initial power up state of the system
(possibly after some intervention by the bootloader) should be whatever,
it's not supposed to be an instruction to Linux itself. Linux should be
using consumers or always on.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-21 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 20:55 boot_on regulator constraint vs. regulator-boot-on DT property Stephen Warren
2012-06-20 23:46 ` Mark Brown
2012-06-21 1:26 ` Stephen Warren
2012-06-21 9:12 ` Mark Brown [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=20120621091202.GF4037@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=swarren@wwwdotorg.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