From: "Heiko Stübner" <heiko@sntech.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] ARM: dts: rockchip: Add dynamic-power-coefficient for rk3288
Date: Fri, 12 Apr 2019 12:08:21 +0200 [thread overview]
Message-ID: <9063550.zi1cCdPW0A@diego> (raw)
In-Reply-To: <20190412000158.248080-1-mka@chromium.org>
Am Freitag, 12. April 2019, 02:01:58 CEST schrieb Matthias Kaehlcke:
> The value was determined with the following method:
>
> - take CPUs 1-3 offline
> - for each OPP
> - set cpufreq min and max freq to OPP freq
> - start dhrystone benchmark
> - measure CPU power consumption during 10s
> - calculate Cx for OPPx
> - Cx = (Px - P1) / (Vx²fx - V1²f1) [1]
> using the following units: mW / Ghz / V [2]
> - C = avg(C2, ..., Cn)
>
> [1] see commit 4daa001a1773 ("arm64: dts: juno: Add cpu
> dynamic-power-coefficient information")
> [2] https://patchwork.kernel.org/patch/10493615/#22158551
>
> FTR, these are the values for the different OPPs:
>
> freq (kHz) mV Px (mW) Cx
>
> 126000 900 39
> 216000 900 66 370
> 312000 900 95 372
> 408000 900 122 363
> 600000 900 177 359
> 696000 950 230 363
> 816000 1000 297 361
> 1008000 1050 404 362
> 1200000 1100 528 362
> 1416000 1200 770 377
> 1512000 1300 984 385
> 1608000 1350 1156 394
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
I've applied this for 5.2 but moved the new entries
below the clock properties for some more alphabetic ordering.
Heiko
prev parent reply other threads:[~2019-04-12 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 0:01 [PATCH] ARM: dts: rockchip: Add dynamic-power-coefficient for rk3288 Matthias Kaehlcke
2019-04-12 10:08 ` Heiko Stübner [this message]
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=9063550.zi1cCdPW0A@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--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=mka@chromium.org \
--cc=robh+dt@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).