linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	kernel@pengutronix.de, alkml@pengutronix.de
Subject: Re: [RFC] regulator: Propagate voltage changes to supply regulators
Date: Wed, 30 Sep 2015 16:07:47 +0200	[thread overview]
Message-ID: <20150930140747.GD7858@pengutronix.de> (raw)
In-Reply-To: <1443621474-2191-1-git-send-email-s.hauer@pengutronix.de>

Please do not answer to this series, it contains a wrong address for the
linux-arm-kernel list. I just resent this with the correct addres. Sorry
for the noise.

Sascha

On Wed, Sep 30, 2015 at 03:57:48PM +0200, Sascha Hauer wrote:
> Until now changing the voltage of a regulator only ever effected the
> regulator itself, but never its supplies. It's a common pattern though
> to put LDO regulators behind switching regulators. The switching
> regulators efficiently drop the input voltage but have a high ripple on
> their output. The output is then cleaned up by the LDOs. For higher
> energy efficiency the voltage drop at the LDOs should be minimized. This
> patch adds support for such a scenario.
> 
> 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
> a) before increasing the voltage on the current regulator the supply
>    provides at least the desired voltage plus the minimum dropout
> b) after decreasing the voltage on the current regulator the supply
>    is optimized to the minimum required voltage within the needs of
>    the consumers of the supply.
> 
> Calculating the optimum voltage for the supply regulator is a bit tricky
> since the simple approach of just adding the desired minimum voltage and
> the minimum dropout is not enough. It may happen that the current
> regulator does not support the desired minimum voltage, but only a
> higher one. This means we have to figure out the lowest voltage
> supported by the regulator that is higher than the minimum desired
> voltage. The regulator_get_voltage_floor introduced with this series
> does
> exactly that.
> 
> This is a first RFC for this series which probably has some rough edges,
> but it was already tested successfully on a Phytec PFLA02 i.MX6 board.
> 
> Please review, any input welcome.
> 
> 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 |

  parent reply	other threads:[~2015-09-30 14:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 13:57 [RFC] regulator: Propagate voltage changes to supply regulators Sascha Hauer
2015-09-30 13:57 ` [PATCH 1/6] Revert "regulator: core: Handle full constraints systems when resolving supplies" Sascha Hauer
2015-09-30 18:02   ` Mark Brown
2015-09-30 18:48     ` Sascha Hauer
2015-09-30 19:26       ` Mark Brown
2015-09-30 13:57 ` [PATCH 2/6] regulator: core: introduce function to lock regulators and its supplies Sascha Hauer
2015-09-30 13:57 ` [PATCH 3/6] regulator: core: create unlocked version of regulator_list_voltage Sascha Hauer
2015-09-30 13:57 ` [PATCH 4/6] regulator: core: Propagate voltage changes to supply regulators Sascha Hauer
2015-09-30 13:57 ` [PATCH 5/6] regulator: i.MX anatop: Allow supply regulator Sascha Hauer
2015-09-30 13:57 ` [PATCH 6/6] ARM: i.MX6 Phytec PFLA02: Add supplies for the SoC internal regulators Sascha Hauer
2015-09-30 14:07 ` Sascha Hauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-30 14:05 [RFC] regulator: Propagate voltage changes to supply regulators Sascha Hauer

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=20150930140747.GD7858@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alkml@pengutronix.de \
    --cc=broonie@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.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).