From: Quentin Perret <quentin.perret@arm.com>
To: rjw@rjwysocki.net, viresh.kumar@linaro.org, sudeep.holla@arm.com,
liviu.dudau@arm.com, lorenzo.pieralisi@arm.com,
robh+dt@kernel.org, mark.rutland@arm.com, nm@ti.com,
sboyd@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dietmar.eggemann@arm.com, mka@chromium.org,
quentin.perret@arm.com
Subject: [PATCH 0/7] Register an Energy Model for Arm reference platforms
Date: Mon, 28 Jan 2019 16:55:15 +0000 [thread overview]
Message-ID: <20190128165522.31749-1-quentin.perret@arm.com> (raw)
The Energy Model (EM) framework feeds interested subsystems (the
scheduler/EAS as of now) with power costs provided by drivers. Yet, no
driver is actually doing that upstream yet. This series updates a set of
CPUFreq drivers and DT files in order to register power costs in the EM
framework for some of the Arm reference platforms for EAS: Hikey960,
Juno and TC2.
The series is split as follows:
* Patch 01 introduces in PM_OPP a helper function which estimates the
CPU power using the P=CV²f equation also used by IPA. It should be
noted that this introduces duplicate code with IPA, which will
eventually be fixed by migrating IPA to using PM_EM. The ideal plan
would be to do so later, in a separate patch series. I would indeed
prefer to keep the thermal and CPUFreq discussion separate at this
stage, if deemed acceptable.
* Patches 02-04 make use of that PM_OPP helper function from the
following CPUFreq drivers: cpufreq-dt, scpi-cpufreq and
arm_big_little.
* Patch 05 modifies the SCMI cpufreq driver to pass the power costs
obtained from firmware to PM_EM.
* Patches 06-07 provide the dynamic-power-coefficient values for Juno
and TC2.
Thanks,
Quentin
Dietmar Eggemann (3):
cpufreq: arm_big_little: Register an Energy Model
arm64: dts: juno: Add cpu dynamic-power-coefficient information
arm: dts: vexpress-v2p-ca15_a7: Add cpu dynamic-power-coefficient
information
Quentin Perret (4):
PM / OPP: Introduce a power estimation helper
cpufreq: dt: Register an Energy Model
cpufreq: scpi: Register an Energy Model
cpufreq: scmi: Register an Energy Model
arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts | 5 ++
arch/arm64/boot/dts/arm/juno-r2.dts | 6 +++
arch/arm64/boot/dts/arm/juno.dts | 6 +++
drivers/cpufreq/arm_big_little.c | 10 ++++
drivers/cpufreq/cpufreq-dt.c | 7 ++-
drivers/cpufreq/scmi-cpufreq.c | 36 ++++++++++++-
drivers/cpufreq/scpi-cpufreq.c | 8 ++-
drivers/opp/of.c | 60 ++++++++++++++++++++++
include/linux/pm_opp.h | 5 ++
9 files changed, 140 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-28 16:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 16:55 Quentin Perret [this message]
2019-01-28 16:55 ` [PATCH 1/7] PM / OPP: Introduce a power estimation helper Quentin Perret
2019-01-28 19:02 ` Matthias Kaehlcke
2019-01-29 9:03 ` Quentin Perret
2019-01-29 17:52 ` Matthias Kaehlcke
2019-01-29 5:10 ` Viresh Kumar
2019-01-29 9:09 ` Quentin Perret
2019-01-28 16:55 ` [PATCH 2/7] cpufreq: dt: Register an Energy Model Quentin Perret
2019-01-28 19:36 ` Matthias Kaehlcke
2019-01-29 5:21 ` Viresh Kumar
2019-01-29 9:15 ` Quentin Perret
2019-01-30 5:18 ` Viresh Kumar
2019-01-30 9:12 ` Quentin Perret
2019-01-30 10:17 ` Viresh Kumar
2019-01-30 10:20 ` Quentin Perret
2019-01-29 5:30 ` Viresh Kumar
2019-01-29 9:10 ` Quentin Perret
2019-01-28 16:55 ` [PATCH 3/7] cpufreq: scpi: " Quentin Perret
2019-01-29 5:31 ` Viresh Kumar
2019-01-28 16:55 ` [PATCH 4/7] cpufreq: arm_big_little: " Quentin Perret
2019-01-28 16:55 ` [PATCH 5/7] cpufreq: scmi: " Quentin Perret
2019-01-28 16:55 ` [PATCH 6/7] arm64: dts: juno: Add cpu dynamic-power-coefficient information Quentin Perret
2019-01-29 15:27 ` Sudeep Holla
2019-01-30 10:23 ` Quentin Perret
2019-01-28 16:55 ` [PATCH 7/7] arm: dts: vexpress-v2p-ca15_a7: " Quentin Perret
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=20190128165522.31749-1-quentin.perret@arm.com \
--to=quentin.perret@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).