Re: [PATCH 2/2] regulator: Propagate uA_load requirements upsupply chain

From: Russell King - ARM Linux
Date: Mon Mar 28 2011 - 14:14:37 EST


On Mon, Mar 28, 2011 at 07:02:55PM +0100, Mark Brown wrote:
> 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.

That's not true. Firstly, *all* regulators are not 100% efficient. They
lose *power* in the form of heat. So power into the regulator will always
be more than power out.

For linear regulators, the current flowing into a regulator is the sum
of the output current and the regulators operating current (which may
itself depend on the output current.) The input voltage will always be
greater than the output voltage. Therefore, from P=IV, power in will
always be greater than power out. So, if you have a 5V regulator
connected to a 10V supply, supplying 1A to a load, then:

Power out = 5V * 1A = 5W
Power in = 10V * (1A + operating current) = >10W
Power lost = >10W - 5W = >5W which will be in the form of heat.

For switching regulators, you have power lost again in the form of heat,
generated from the current required to run the regulators electronics
and the need to charge and discharge capacitances. Although these are
much more efficient than linear regulators, they don't get you to 100%
efficiency.

Note that also because P=IV, if the current doesn't map 1:1 through a
regulator, the power certainly won't either.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/