From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data
Date: Fri, 4 Nov 2011 21:29:10 +0000 [thread overview]
Message-ID: <20111104212910.GB8266@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111104212216.GA5756@quad.lixom.net>
On Fri, Nov 04, 2011 at 02:22:16PM -0700, Olof Johansson wrote:
> On Fri, Nov 04, 2011 at 09:14:48PM +0000, Mark Brown wrote:
> > The name will be fixed by the individual device bindings, this is
> > specifying the general form of a supply property. Each device binding
> > will define the set of supplies that the device can use.
> Ah, ok. It shouldn't be a part of this binding then and instead be added
> to the bindings for the consumers.
I think it's useful to define how consumers are supposed to do this
somewhere - it is actually part of the core binding how consumers are
supposed to do this.
There's also a bit of magic here for chained supplies with one regulator
supplying another (eg, using a DCDC to drop the system supply down to a
lower voltage to supply a bunch of LDOs for improved efficiency).
next prev parent reply other threads:[~2011-11-04 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 13:24 [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data Rajendra Nayak
2011-11-04 20:29 ` Olof Johansson
2011-11-04 21:14 ` Mark Brown
2011-11-04 21:22 ` Olof Johansson
2011-11-04 21:29 ` Mark Brown [this message]
2011-11-04 21:34 ` Olof Johansson
2011-11-04 21:46 ` Mark Brown
2011-11-04 22:16 ` Olof Johansson
2011-11-04 22:35 ` Mark Brown
2011-11-04 22:50 ` Olof Johansson
2011-11-07 6:27 ` Rajendra Nayak
2011-11-07 6:27 ` Rajendra Nayak
2011-11-07 6:23 ` Rajendra Nayak
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=20111104212910.GB8266@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).