From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] mfd: axp20x: add AXP221 PMIC support
Date: Wed, 28 May 2014 21:46:54 +0200 [thread overview]
Message-ID: <53863D2E.7050008@free-electrons.com> (raw)
In-Reply-To: <20140527194932.GD12304@sirena.org.uk>
Hello Mark,
On 27/05/2014 21:49, Mark Brown wrote:
> On Tue, May 27, 2014 at 11:38:49AM +0200, Boris BREZILLON wrote:
>
>> I'm still waiting for inputs regarding the ipsout regulator representation:
> If you've got questions you need an answer to urgently it's possibly
> best to highlight them outside of a series like this doing that helps
> make it more obvious.
Noted. I'll take care to send a separate mail next time.
BTW, I don't if you've noticed, but patch 5 of this series implements
helper functions to register several regulators from a regulator_desc
and an of_regulator_match table (as you suggested).
>> * The ipsout regulator is currently represented as a fixed regulator
>> providing a 5v output, and this is not exactly the case.
>> AFAIU (here's is the datasheet traduction if you want to check [1]), the
>> ipsout output is a multiplexer that choose among vbus (5V), acin (12V
>> which is then converted to 5V) and the battery power supply (3,5 -> 4,2 V).
>> This means the output voltage of ipsout vary between 3,5V and 5V.
>> How can we express this kind of muxer in the regulator framework (is there
>> already something available ?) ?
>> Note that the power supply selection is automatic, though we could force
>> one power supply, but then we loose the ability to unplug one power supply
>> without impacting the system.
> This sounds like it may as well just be represented as an unregulated
> supply - it's just the system root supply really. Nothing can rely on
> the voltage anyway as it's going to vary randomly depending on what the
> user does power wise and typically it'd only be used as a supply for
> things that don't care about the specific voltage.
Okay, I'm fine with that.
Thanks.
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2014-05-28 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 9:38 [PATCH v3 0/6] mfd: axp20x: add AXP221 PMIC support Boris BREZILLON
2014-05-27 9:38 ` [PATCH v3 1/6] " Boris BREZILLON
2014-05-27 10:05 ` Lee Jones
2014-05-27 10:14 ` Boris BREZILLON
2014-05-27 9:38 ` [PATCH v3 2/6] regulator: axp20x: prepare support for multiple AXP chip families Boris BREZILLON
2014-05-27 9:38 ` [PATCH v3 3/6] regulator: axp20x: add support for AXP221 regulators Boris BREZILLON
2014-05-27 9:38 ` [PATCH v3 4/6] regulator: axp20x: reset probe data before each probe Boris BREZILLON
2014-05-27 9:38 ` [PATCH v3 5/6] regulator: add support for regulator set registration Boris BREZILLON
2014-06-10 13:40 ` Boris BREZILLON
2014-06-16 8:08 ` Lee Jones
2014-06-16 13:24 ` Boris BREZILLON
2014-05-27 9:38 ` [PATCH v3 6/6] regulator: axp20x: make use of devm_regulator_set_register Boris BREZILLON
2014-05-27 19:49 ` [PATCH v3 0/6] mfd: axp20x: add AXP221 PMIC support Mark Brown
[not found] ` <9ed19670-7a2e-4324-a201-6d3c8514bdb3@googlegroups.com>
2014-05-28 17:49 ` Mark Brown
2014-05-28 19:46 ` Boris BREZILLON [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=53863D2E.7050008@free-electrons.com \
--to=boris.brezillon@free-electrons.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).