From: Punit Agrawal <punit.agrawal@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, edubezval@gmail.com,
viresh.kumar@linaro.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] dt-binding: arm/cpus.txt: fix dynamic-power-coefficient unit
Date: Wed, 22 Aug 2018 11:11:22 +0100 [thread overview]
Message-ID: <87ftz6ww1h.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <1534869685-22221-1-git-send-email-vincent.guittot@linaro.org> (Vincent Guittot's message of "Tue, 21 Aug 2018 18:41:25 +0200")
Hi Vincent,
Thanks for the patch. One comment about the choice of units below.
Vincent Guittot <vincent.guittot@linaro.org> writes:
> The unit of dynamic-power-coefficient is described as mW/MHz/uV^2 whereas
> its usage in the code assumes that unit is mW/GHz/V^2
Instead of choosing GHz as the base, I'd prefer to use uW/MHz/V^2. It'll
avoid introducing fractional GHz value for frequency calculations.
> In drivers/thermal/cpu_cooling.c, the code is :
>
> power = (u64)capacitance * freq_mhz * voltage_mv * voltage_mv;
> do_div(power, 1000000000);
>
> which can be summarized as :
> power (mW) = capacitance * freq_mhz/1000 * (voltage_mv/1000)^2
Which would then translate to -
power (mW) = power (uW) / 1000 = capacitance * freq_mhz * (voltage_mv/1000)^2
Thanks,
Punit
>
> Furthermore, if we test basic values like :
> voltage_mv = 1000mV = 1V
> freq_mhz = 1000Mhz = 1Ghz
>
> The minimum possible power, when dynamic-power-coefficient equals 1, will
> be :
> min power = 1 * 1000 * (1000000)^2 = 10^15 mW
> which is not realistic
>
> With the unit used by the code, the min power is
> min power = 1 * 1 * 1^2 = 1mW which is far more realistic
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> Documentation/devicetree/bindings/arm/cpus.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt
> index 29e1dc5..0148d7d 100644
> --- a/Documentation/devicetree/bindings/arm/cpus.txt
> +++ b/Documentation/devicetree/bindings/arm/cpus.txt
> @@ -274,7 +274,7 @@ described below.
> Usage: optional
> Value type: <prop-encoded-array>
> Definition: A u32 value that represents the running time dynamic
> - power coefficient in units of mW/MHz/uV^2. The
> + power coefficient in units of mW/GHz/V^2. The
> coefficient can either be calculated from power
> measurements or derived by analysis.
>
> @@ -285,7 +285,7 @@ described below.
>
> Pdyn = dynamic-power-coefficient * V^2 * f
>
> - where voltage is in uV, frequency is in MHz.
> + where voltage is in V, frequency is in GHz.
>
> Example 1 (dual-cluster big.LITTLE system 32-bit):
next prev parent reply other threads:[~2018-08-22 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 16:41 Vincent Guittot
2018-08-22 10:11 ` Punit Agrawal [this message]
2018-08-22 14:32 ` Vincent Guittot
2018-08-28 14:42 ` Punit Agrawal
2018-08-29 6:48 ` Vincent Guittot
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=87ftz6ww1h.fsf@e105922-lin.cambridge.arm.com \
--to=punit.agrawal@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®