From: Mark Brown <broonie@kernel.org>
To: Tushar Behera <tushar.behera@linaro.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rob@landley.net, olof@lixom.net
Subject: Re: [PATCH 2/2] regulator: core: Add reg_ignore_unused to keep boot time regulators enabled
Date: Fri, 28 Mar 2014 10:22:20 +0000 [thread overview]
Message-ID: <20140328102220.GU30768@sirena.org.uk> (raw)
In-Reply-To: <1395984022-8284-3-git-send-email-tushar.behera@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
On Fri, Mar 28, 2014 at 10:50:22AM +0530, Tushar Behera wrote:
> Keep all regulators already enabled by bootloader on, even if no
> driver has claimed them. This is useful for debug and development, but
> should not be needed on a platform with proper driver support.
That's already the default on non-DT systems so I'd expect that if we
were doing this the code would be joined up with the code for that. I'm
not sure this is a terribly good idea though - we already display a
message just before we power off the regulator and having an option like
this feels like it's going to encourage people to write bad DTs and tell
people to add this to their command line.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-28 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 5:20 [PATCH 0/2] Add reg_ignore_unused and pd_ignore_unused Tushar Behera
2014-03-28 5:20 ` [PATCH 1/2] PM / Domains: Add pd_ignore_unused to keep power domains enabled Tushar Behera
2014-03-28 5:20 ` [PATCH 2/2] regulator: core: Add reg_ignore_unused to keep boot time regulators enabled Tushar Behera
2014-03-28 10:22 ` Mark Brown [this message]
2014-04-01 13:29 ` Tushar Behera
2014-04-01 15:58 ` 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=20140328102220.GU30768@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rob@landley.net \
--cc=tushar.behera@linaro.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
all inboxes | Powered by JetHome®