From: Heiko Stuebner <heiko@sntech.de>
To: Caesar Wang <wxt@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Douglas Anderson <dianders@chromium.org>,
William wu <wulf@rock-chips.com>,
Elaine Zhang <zhangqing@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
Brian Norris <briannorris@chromium.org>,
linux-kernel@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Roger Chen <roger.chen@rock-chips.com>
Subject: Re: [PATCH] arm64: dts: rockchip: update dynamic-power-coefficient for rk3399
Date: Tue, 01 Aug 2017 01:02:04 +0200 [thread overview]
Message-ID: <1954724.bYQfYcfQLC@phil> (raw)
In-Reply-To: <1500974575-2244-1-git-send-email-wxt@rock-chips.com>
Am Dienstag, 25. Juli 2017, 17:22:55 CEST schrieb Caesar Wang:
> This patch updates the dynamic-power-coefficient for big cluster on
> rk3399 SoCs.
>
> The dynamic power consumption of the CPU is proportional to the square of
> the Voltage (V) and the clock frequency (f). The coefficient is used to
> calculate the dynamic power as below -
> Pdyn = dynamic-power-coefficient * V^2 * f
> Where Voltage is in uV, frequency is in MHz.
>
> As the following is the tested data on rk3399's big cluster.
> frequency(MHz) Voltage(V) Current(mA) Dynamic-power-coefficient
> 24 0.8 15
> 48 0.8 23 ~417
> 96 0.8 40 ~443
> 216 0.8 82 ~438
> 312 0.8 115 ~430
> 408 0.8 150 ~455
> So the dynamic-power-coefficient average value is about 436.
>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
applied for 4.14 and thanks for that very nice and informative commit
message explaining the testing methodology.
Heiko
> ---
>
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> index 9d02006..5d54a06 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> @@ -150,7 +150,7 @@
> enable-method = "psci";
> #cooling-cells = <2>; /* min followed by max */
> clocks = <&cru ARMCLKB>;
> - dynamic-power-coefficient = <100>;
> + dynamic-power-coefficient = <436>;
> };
>
> cpu_b1: cpu@101 {
> @@ -159,7 +159,7 @@
> reg = <0x0 0x101>;
> enable-method = "psci";
> clocks = <&cru ARMCLKB>;
> - dynamic-power-coefficient = <100>;
> + dynamic-power-coefficient = <436>;
> };
> };
>
>
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: rockchip: update dynamic-power-coefficient for rk3399
Date: Tue, 01 Aug 2017 01:02:04 +0200 [thread overview]
Message-ID: <1954724.bYQfYcfQLC@phil> (raw)
In-Reply-To: <1500974575-2244-1-git-send-email-wxt@rock-chips.com>
Am Dienstag, 25. Juli 2017, 17:22:55 CEST schrieb Caesar Wang:
> This patch updates the dynamic-power-coefficient for big cluster on
> rk3399 SoCs.
>
> The dynamic power consumption of the CPU is proportional to the square of
> the Voltage (V) and the clock frequency (f). The coefficient is used to
> calculate the dynamic power as below -
> Pdyn = dynamic-power-coefficient * V^2 * f
> Where Voltage is in uV, frequency is in MHz.
>
> As the following is the tested data on rk3399's big cluster.
> frequency(MHz) Voltage(V) Current(mA) Dynamic-power-coefficient
> 24 0.8 15
> 48 0.8 23 ~417
> 96 0.8 40 ~443
> 216 0.8 82 ~438
> 312 0.8 115 ~430
> 408 0.8 150 ~455
> So the dynamic-power-coefficient average value is about 436.
>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
applied for 4.14 and thanks for that very nice and informative commit
message explaining the testing methodology.
Heiko
> ---
>
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> index 9d02006..5d54a06 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> @@ -150,7 +150,7 @@
> enable-method = "psci";
> #cooling-cells = <2>; /* min followed by max */
> clocks = <&cru ARMCLKB>;
> - dynamic-power-coefficient = <100>;
> + dynamic-power-coefficient = <436>;
> };
>
> cpu_b1: cpu at 101 {
> @@ -159,7 +159,7 @@
> reg = <0x0 0x101>;
> enable-method = "psci";
> clocks = <&cru ARMCLKB>;
> - dynamic-power-coefficient = <100>;
> + dynamic-power-coefficient = <436>;
> };
> };
>
>
next prev parent reply other threads:[~2017-07-31 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 9:22 [PATCH] arm64: dts: rockchip: update dynamic-power-coefficient for rk3399 Caesar Wang
2017-07-25 9:22 ` Caesar Wang
2017-07-31 23:02 ` Heiko Stuebner [this message]
2017-07-31 23:02 ` Heiko Stuebner
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=1954724.bYQfYcfQLC@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=roger.chen@rock-chips.com \
--cc=shawn.lin@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=wulf@rock-chips.com \
--cc=wxt@rock-chips.com \
--cc=zhangqing@rock-chips.com \
/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.