From: Punit Agrawal <punit.agrawal@arm.com>
To: devicetree@vger.kernel.org
Cc: Punit Agrawal <punit.agrawal@arm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
edubezval@gmail.com, dawei.chien@mediatek.com,
javi.merino@arm.com
Subject: [PATCH v4 0/3] Dynamic power model from device tree
Date: Mon, 16 Nov 2015 19:30:22 +0000 [thread overview]
Message-ID: <1447702225-13323-1-git-send-email-punit.agrawal@arm.com> (raw)
Hi,
This patchset adds support to build a single-coefficient dynamic power
model for a CPU. The model is used by the CPU cooling device to
provide an estimate of power consumption and also translate allocated
power to performance cap.
Changes from previous posting -
v3 -> v4:
arm_big_little: Migrated to using static arrays
arm_big_little: Updated Kconfig to support building thermal as module
Patch 1 extends the CPU nodes binding to provide an optional dynamic
power coefficient which can be used to create a dynamic power model
for the CPUs. This model is used to constrain device power consumption
(using power_allocator governor) when the system is thermally
constrained.
Patches 2-3 extends the cpufreq-dt and arm_big_little driver to
register cpu cooling devices with the dynamic coefficient when
provided.
The patches were previously posted at [0][1][2]. Mediatek platform
8173 builds on these bindings to build the power model.
If there are no objections, I'd appreciate Acks from device tree
bindings maintainers.
Thanks,
Punit
[0] http://thread.gmane.org/gmane.linux.kernel/2002152
[1] http://thread.gmane.org/gmane.linux.kernel/2011466
[2] http://marc.info/?l=linux-kernel&m=144709020014884&w=2
Punit Agrawal (3):
devicetree: bindings: Add optional dynamic-power-coefficient property
cpufreq-dt: Supply power coefficient when registering cooling devices
cpufreq: arm_big_little: Add support to register a cpufreq cooling
device
Documentation/devicetree/bindings/arm/cpus.txt | 17 +++++++++++++
drivers/cpufreq/Kconfig.arm | 2 ++
drivers/cpufreq/arm_big_little.c | 35 ++++++++++++++++++++++++++
drivers/cpufreq/cpufreq-dt.c | 9 +++++--
4 files changed, 61 insertions(+), 2 deletions(-)
--
2.6.2
next reply other threads:[~2015-11-16 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 19:30 Punit Agrawal [this message]
2015-11-16 19:30 ` [PATCH v4 1/3] devicetree: bindings: Add optional dynamic-power-coefficient property Punit Agrawal
2015-11-16 23:23 ` Rob Herring
2015-11-17 4:36 ` Viresh Kumar
[not found] ` <1447702225-13323-1-git-send-email-punit.agrawal-5wv7dgnIgG8@public.gmane.org>
2015-11-16 19:30 ` [PATCH v4 2/3] cpufreq-dt: Supply power coefficient when registering cooling devices Punit Agrawal
2015-11-16 19:30 ` [PATCH v4 3/3] cpufreq: arm_big_little: Add support to register a cpufreq cooling device Punit Agrawal
[not found] ` <1447702225-13323-4-git-send-email-punit.agrawal-5wv7dgnIgG8@public.gmane.org>
2015-11-17 4:43 ` Viresh Kumar
2015-11-17 10:58 ` Punit Agrawal
2015-11-17 4:35 ` [PATCH v4 0/3] Dynamic power model from device tree Viresh Kumar
2015-11-17 10:05 ` Punit Agrawal
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=1447702225-13323-1-git-send-email-punit.agrawal@arm.com \
--to=punit.agrawal@arm.com \
--cc=dawei.chien@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=javi.merino@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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