From: jouni.hogander@nokia.com (Högander Jouni)
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Valentin Eduardo \(Nokia-D\/Helsinki\)"
<eduardo.valentin@nokia.com>,
"De-Schrijver Peter \(Nokia-D\/Helsinki\)"
<Peter.De-Schrijver@nokia.com>,
"Keski-Saari Juha.1 \(EXT-Teleca\/Helsinki\)"
<ext-juha.1.keski-saari@nokia.com>,
LKML <linux-kernel@vger.kernel.org>,
"lrg\@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: Doubt about Regulator Framework and VBAT use case
Date: Wed, 02 Dec 2009 13:32:06 +0200 [thread overview]
Message-ID: <87iqcpk3wp.fsf@trdhcp146196.ntc.nokia.com> (raw)
In-Reply-To: <20091130114515.GB10968@rakim.wolfsonmicro.main> (ext Mark Brown's message of "Mon\, 30 Nov 2009 12\:45\:15 +0100")
ext Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
> On Mon, Nov 30, 2009 at 12:41:02PM +0200, Eduardo Valentin wrote:
>
>> I'm writing to ask about VBAT use case. What is the expected
>> way to use regulator framework in case of rail coming from battery?
>> Should it be added to the regulator framework at all?
>
> ...
>
>> However, drivers for devices on that rail would require their regulator anyway.
>> And I guess the point would be that drivers should not be aware that they are on VBAT
>> or any other rail.
>
> I'd add it as a fixed voltage regulator and either not specify the
> voltage or specify the nominal voltage.
I was preparing patch for this when I noticed that fixed voltage
regulator can control only one regulator. Are you aware of any ongoing
work to enable control for multiple regulators in
fixed-voltage-regulator?
--
Jouni Högander
next prev parent reply other threads:[~2009-12-02 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 10:41 Eduardo Valentin
2009-11-30 10:43 ` Eduardo Valentin
2009-11-30 11:45 ` Mark Brown
2009-12-02 11:32 ` Högander Jouni [this message]
2009-12-02 12:02 ` Mark Brown
2009-12-02 13:55 ` Högander Jouni
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=87iqcpk3wp.fsf@trdhcp146196.ntc.nokia.com \
--to=jouni.hogander@nokia.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eduardo.valentin@nokia.com \
--cc=ext-juha.1.keski-saari@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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®