From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] regulator: core: Propagate voltage changes to supply regulators
Date: Mon, 12 Oct 2015 13:42:59 +0200 [thread overview]
Message-ID: <20151012114259.GU7858@pengutronix.de> (raw)
In-Reply-To: <20151002173256.GZ12635@sirena.org.uk>
Hi Mark,
On Fri, Oct 02, 2015 at 06:32:56PM +0100, Mark Brown wrote:
> On Wed, Sep 30, 2015 at 04:05:44PM +0200, Sascha Hauer wrote:
>
> > A new min_dropout_uv field is added to struct regulator_desc. Regulators
> > can specify the minimun dropout voltage they need for proper function
> > here. Now when the voltage is changed on a regulator the regulator core
> > makes sure that
>
> Can we have this interface addition as a separate patch please? Makes
> it easier to add to other devices. I could've sworn I'd already done
> that bit but obviously never got the patch mailed out.
>
> One change I think we need here is only doing the propagation if either
> the device lacks a set_voltage() operation (in which case it's just a
> switch passing through the parent voltage)
Does the lack of a set_voltage() operation automatically mean it's a
switch passing through the parent voltage? What if the regulator is a
fixed regulator and the output can't be controlled because there is only
one voltage?
Currently we bail out int regulator_set_voltage() when we do not have a
set_voltage() or set_voltage_sel() operation. Instead of propagating the
voltage change up I would keep the current behaviour and implement voltage
propagation for switches when we need it. Then we could also introduce a
REGULATOR_IS_SWITCH flag indicating that this is a switch and not a
fixed voltage regulator.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2015-10-12 11:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 14:05 [RFC] regulator: Propagate voltage changes to supply regulators Sascha Hauer
2015-09-30 14:05 ` [PATCH 1/6] Revert "regulator: core: Handle full constraints systems when resolving supplies" Sascha Hauer
2015-09-30 18:03 ` Mark Brown
2015-09-30 14:05 ` [PATCH 2/6] regulator: core: introduce function to lock regulators and its supplies Sascha Hauer
2015-09-30 14:21 ` kbuild test robot
2015-09-30 14:05 ` [PATCH 3/6] regulator: core: create unlocked version of regulator_list_voltage Sascha Hauer
2015-09-30 22:36 ` Mark Brown
2015-10-01 11:29 ` Mark Brown
2015-09-30 14:05 ` [PATCH 4/6] regulator: core: Propagate voltage changes to supply regulators Sascha Hauer
2015-10-02 17:32 ` Mark Brown
2015-10-12 11:42 ` Sascha Hauer [this message]
2015-10-12 14:07 ` Mark Brown
2015-10-13 9:30 ` Sascha Hauer
2015-09-30 14:05 ` [PATCH 5/6] regulator: i.MX anatop: Allow supply regulator Sascha Hauer
2015-09-30 14:05 ` [PATCH 6/6] ARM: i.MX6 Phytec PFLA02: Add supplies for the SoC internal regulators Sascha Hauer
2015-10-02 17:33 ` 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=20151012114259.GU7858@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).