From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: linux-pm@lists.linux-foundation.org, Liam Girdwood <lrg@ti.com>
Subject: Re: how to best map device regulators
Date: Fri, 2 Sep 2011 13:49:17 +0100 [thread overview]
Message-ID: <20110902124916.GB27415@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201109021142.01057.heiko@sntech.de>
On Fri, Sep 02, 2011 at 11:42:00AM +0200, Heiko Stübner wrote:
> My first candidate is a "GMT G9093", i.e. two fixed voltage regulators in one ic
> controlled via GPIOs. Here intuition suggest to simply use two instances of
> the fixed-driver - no use in duplicating its function. Correct?
Seems sensible.
> Second, more complex chip, is a TI tps650240, i.e. 3 fixed voltage regulators,
> 1 regulator switchable between 2 voltages - all controllable via GPIOs - and
> two regulators whose enabled-state is controlled by one gpio only.
> Here I'm torn between (1) building a new driver and (2) using fixed voltage
> drivers and building a switch-driver for the two voltage-regulator (here I'm
> also not sure if this should be crammed into the fixed-driver, as I think it is
A separate driver for one that can select voltages seems sensible.
> called fixed for a reason). For (2) I'm also not sure, on how to implement
> support for the two regulators controlled by one gpio.
That's not really well supported but from a system integration point of
view it's usually fine since the design tends to be such that the two
are always enabled together so you can just give the enable to one of
the regulators and ignore the fact that it's actually controlling both
and software actually works fine even if it's not truly correct.
prev parent reply other threads:[~2011-09-02 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 9:42 how to best map device regulators Heiko Stübner
2011-09-02 12:49 ` Mark Brown [this message]
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=20110902124916.GB27415@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=heiko@sntech.de \
--cc=linux-pm@lists.linux-foundation.org \
--cc=lrg@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).