From: Mark Brown <broonie@kernel.org>
To: Graeme Gregory <gg@slimlogic.co.uk>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
sameo@linux.intel.com, ian@slimlogic.co.uk,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/3] regulator: palmas: support for external regulator through control outputs
Date: Wed, 17 Apr 2013 15:06:14 +0100 [thread overview]
Message-ID: <20130417140614.GO13687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <516EA8E6.8040403@slimlogic.co.uk>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On Wed, Apr 17, 2013 at 02:51:34PM +0100, Graeme Gregory wrote:
> This looks good to me with one proviso!
> SYSEN1/2 are not necessarily for regulators as given by the name, they
> are more for use indicating to other chips that power is now
> available/stable.
> But it will not break things to have them exposed in regulator API so I
> shall leave this to Mark.
It's probably reasonable given that things like this normally end up
being part of the power sequencing or used for external regulators.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-17 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 9:43 [PATCH 1/3] regulator: palmas: clear sleep bits if not selected Laxman Dewangan
2013-04-17 9:43 ` [PATCH 2/3] regulator: palmas: support for external regulator through control outputs Laxman Dewangan
2013-04-17 13:51 ` Graeme Gregory
2013-04-17 14:06 ` Mark Brown [this message]
2013-04-17 9:43 ` [PATCH 3/3] regulator: palmas: add support for LDO8 tracking mode Laxman Dewangan
2013-04-17 13:54 ` Graeme Gregory
2013-04-17 16:14 ` Laxman Dewangan
2013-04-17 14:06 ` Mark Brown
2013-04-17 13:53 ` [PATCH 1/3] regulator: palmas: clear sleep bits if not selected Graeme Gregory
2013-04-17 14:03 ` 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=20130417140614.GO13687@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=gg@slimlogic.co.uk \
--cc=ian@slimlogic.co.uk \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).