From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Michael Bohan <mbohan@codeaurora.org>
Cc: rnayak@ti.com, lrg@ti.com, LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: Regulator supplies when using Device Tree
Date: Mon, 2 Apr 2012 22:22:33 +0100 [thread overview]
Message-ID: <20120402212232.GA3160@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F79E35A.5040908@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Mon, Apr 02, 2012 at 10:35:22AM -0700, Michael Bohan wrote:
> On 3/30/2012 3:36 AM, Mark Brown wrote:
> >The support for regulator-regulator supplies has always been problematic
> >and infrequently used -
> Hmm, I'd be interested to know the history there.
git logs should be instructive. The use part is just because most board
designs end up thinking of better things to do with their DCDCs than
drop the supply for LDOs.
> >Please be more specific about what you're actually trying to physically
> >accomplish here. It would be *extremely* unusual to see a regulator
> Some of our regulators take inputs from other regulators. Some
> regulators take their input from the battery. We support both types
Oh, if that's all it is that's totally normal and unsurprising. Just
tell the regulator API about the battery supply, typically people use
a fixed regulator for this. You don't have to specify a voltage when
you use them.
> I don't disagree that the new scheme makes supplies more like normal
> supplies. I'm just pointing out the solution doesn't appear perfect
> since extraneous code is put in the driver in this case.
To repeat yet again if you're putting code for this in the driver you've
got a clear abstraction failure.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-02 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 1:17 Regulator supplies when using Device Tree Michael Bohan
2012-03-26 13:00 ` Mark Brown
2012-03-28 1:38 ` Michael Bohan
2012-03-28 10:09 ` Mark Brown
2012-03-28 19:19 ` Michael Bohan
2012-03-28 19:33 ` Mark Brown
2012-03-29 0:06 ` Michael Bohan
2012-03-29 4:44 ` Rajendra Nayak
2012-03-29 11:08 ` Mark Brown
2012-03-29 11:11 ` Mark Brown
2012-03-30 1:18 ` Michael Bohan
2012-03-30 10:36 ` Mark Brown
2012-04-02 17:35 ` Michael Bohan
2012-04-02 21:22 ` Mark Brown [this message]
2012-04-03 1:53 ` Michael Bohan
2012-04-03 12:25 ` 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=20120402212232.GA3160@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mbohan@codeaurora.org \
--cc=rnayak@ti.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).