From: Javi Merino <javi.merino@arm.com>
To: linux-pm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, cw00.choi@samsung.com,
edubezval@gmail.com, Javi Merino <javi.merino@arm.com>
Subject: [PATCH v6 0/5] Devfreq cooling device
Date: Thu, 10 Sep 2015 18:09:27 +0100 [thread overview]
Message-ID: <1441904972-5809-1-git-send-email-javi.merino@arm.com> (raw)
This series introduces a devfreq cooling device in the thermal
framework. Devfreq is used for DVFS for devices other than the CPUs.
With a devfreq cooling device, the thermal framework can throttle them
to control temperature. The cooling device has the power extensions,
so it can be used by all governors in the thermal framework, including
the power allocator governor.
Changes since v5:
- s/enable_disable_opps()/partition_enable_opps()
- Check the state in devfreq_cooling_state2power()
- Make the printing of the dynamic power table a dev_dbg printk
- Remove the warning of simple ondemand devfreq governor from the
code and document it in the Kconfig entry.
- Change the name of the cooling device to thermal-devfreq-X
- s/EXPORT_SYMBOL/EXPORT_SYMBOL_GPL/
- Use a simple dynamic power model if no dynamic power model is
supplied.
Changes since v4:
- Don't introduce a new function in the OPP library and instead fix
dev_pm_opp_get_voltage() as suggested by Viresh Kumar
- Don't allocate memory under RCU
- Don't call dev_pm_opp_enable/disable under RCU
- Generate the frequency table even if the power extensions were
not provided
Changes since v3:
- Made devfreq_update_stats() a static inline function
- Add dev_pm_get_voltage_always() to get the voltage even for
disabled OPPs
- Don't rely on freq_table from the devfreq->profile being present
and create our own
- Don't use devm_k* to allocate memory
- Move struct devfreq_cooling_register to devfreq_cooling.c
Javi Merino (4):
PM / devfreq: cache the last call to get_dev_status()
PM / OPP: get the voltage for all OPPs
devfreq_cooling: add trace information
PM / devfreq: drop comment about thermal setting max_freq
Ørjan Eide (1):
thermal: Add devfreq cooling
drivers/base/power/opp.c | 4 +-
drivers/devfreq/devfreq.c | 6 +-
drivers/devfreq/governor_simpleondemand.c | 33 +-
drivers/thermal/Kconfig | 14 +
drivers/thermal/Makefile | 3 +
drivers/thermal/devfreq_cooling.c | 569 ++++++++++++++++++++++++++++++
include/linux/devfreq.h | 15 +
include/linux/devfreq_cooling.h | 81 +++++
include/trace/events/thermal.h | 53 +++
9 files changed, 758 insertions(+), 20 deletions(-)
create mode 100644 drivers/thermal/devfreq_cooling.c
create mode 100644 include/linux/devfreq_cooling.h
--
1.9.1
next reply other threads:[~2015-09-10 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 17:09 Javi Merino [this message]
2015-09-10 17:09 ` [PATCH v6 1/5] PM / devfreq: cache the last call to get_dev_status() Javi Merino
2015-09-10 17:09 ` [PATCH v6 2/5] PM / OPP: get the voltage for all OPPs Javi Merino
2015-09-10 17:09 ` [PATCH v6 3/5] thermal: Add devfreq cooling Javi Merino
2015-09-10 17:09 ` [PATCH v6 4/5] devfreq_cooling: add trace information Javi Merino
2015-09-10 17:19 ` Steven Rostedt
2015-09-18 13:55 ` Javi Merino
2015-09-18 14:04 ` Steven Rostedt
2015-10-14 11:53 ` Javi Merino
2015-10-14 13:22 ` Steven Rostedt
2015-09-10 17:09 ` [PATCH v6 5/5] PM / devfreq: drop comment about thermal setting max_freq Javi Merino
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=1441904972-5809-1-git-send-email-javi.merino@arm.com \
--to=javi.merino@arm.com \
--cc=cw00.choi@samsung.com \
--cc=edubezval@gmail.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