From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Collins <collinsd@codeaurora.org>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: Propagate uA_load requirements up supply chain
Date: Mon, 28 Mar 2011 19:02:55 +0100 [thread overview]
Message-ID: <20110328180255.GA28494@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1301326482-6547-3-git-send-email-collinsd@codeaurora.org>
On Mon, Mar 28, 2011 at 08:34:42AM -0700, David Collins wrote:
> regulator_set_optimum_mode currently only determines the load
> on the specified regulator. Physically however, this current
> must be provided by regulators further up the supply chain.
> Add code to handle uA_load propagation up through the regulator
> supply chain.
We can't do this - current doesn't map 1:1 through a regulator, the
power consumption will map through but obviously there's a voltage
change involved and the regulators will not be 100% efficient so there
will also be some overhead from the chipld regulator. The child
regulator needs to do the mapping in a regulator specific fashion.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] regulator: Propagate uA_load requirements up supply chain
Date: Mon, 28 Mar 2011 19:02:55 +0100 [thread overview]
Message-ID: <20110328180255.GA28494@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1301326482-6547-3-git-send-email-collinsd@codeaurora.org>
On Mon, Mar 28, 2011 at 08:34:42AM -0700, David Collins wrote:
> regulator_set_optimum_mode currently only determines the load
> on the specified regulator. Physically however, this current
> must be provided by regulators further up the supply chain.
> Add code to handle uA_load propagation up through the regulator
> supply chain.
We can't do this - current doesn't map 1:1 through a regulator, the
power consumption will map through but obviously there's a voltage
change involved and the regulators will not be 100% efficient so there
will also be some overhead from the chipld regulator. The child
regulator needs to do the mapping in a regulator specific fashion.
next prev parent reply other threads:[~2011-03-28 18:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 15:34 [PATCH 0/2] regulator: Fix regulator_enable deadlock and add uA_load propagation David Collins
2011-03-28 15:34 ` David Collins
2011-03-28 15:34 ` [PATCH 1/2] regulator: Remove possible deadlock from regulator_enable David Collins
2011-03-28 15:34 ` David Collins
2011-03-28 18:11 ` Mark Brown
2011-03-28 18:11 ` Mark Brown
2011-03-28 18:22 ` David Collins
2011-03-28 18:22 ` David Collins
2011-03-28 15:34 ` [PATCH 2/2] regulator: Propagate uA_load requirements up supply chain David Collins
2011-03-28 15:34 ` David Collins
2011-03-28 18:02 ` Mark Brown [this message]
2011-03-28 18:02 ` Mark Brown
2011-03-28 18:14 ` Russell King - ARM Linux
2011-03-28 18:14 ` Russell King - ARM Linux
2011-03-29 7:53 ` Mark Brown
2011-03-29 7:53 ` Mark Brown
2011-03-29 8:28 ` Russell King - ARM Linux
2011-03-29 8:28 ` Russell King - ARM Linux
2011-03-29 8:40 ` Mark Brown
2011-03-29 8:40 ` Mark Brown
2011-03-28 18:18 ` David Collins
2011-03-28 18:18 ` David Collins
2011-03-28 18:33 ` broonie@gmail.com
2011-03-28 18:33 ` broonie@gmail.com
2011-03-28 23:52 ` [PATCH v2 0/2] regulator: Fix regulator_enable deadlock and add uA_load propagation David Collins
2011-03-28 23:52 ` David Collins
2011-03-28 23:53 ` [PATCH v2 1/2] regulator: Remove possible deadlock from regulator_enable David Collins
2011-03-28 23:53 ` David Collins
2011-03-28 23:53 ` [PATCH v2 2/2] regulator: Propagate uA_load requirements up supply chain David Collins
2011-03-28 23:53 ` David Collins
2011-03-29 8:44 ` Mark Brown
2011-03-29 8:44 ` Mark Brown
2011-03-29 16:08 ` David Collins
2011-03-29 16:08 ` David Collins
2011-03-29 21:20 ` Mark Brown
2011-03-29 21:20 ` Mark Brown
2011-03-30 1:00 ` Mark Brown
2011-03-30 1:00 ` Mark Brown
2011-03-29 22:40 ` Mark Brown
2011-03-29 22:40 ` 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=20110328180255.GA28494@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=collinsd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.