From: Amit Daniel Kachhap <amit.kachhap@linaro.org>
To: linux-pm@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, mjg59@srcf.ucam.org,
linux-acpi@vger.kernel.org, lenb@kernel.org, rui.zhang@intel.com,
linaro-dev@lists.linaro.org, amit.kachhap@linaro.org,
patches@linaro.org
Subject: [RFC PATCH 0/2] thermal: Add generic cpu cooling devices according to thermal framework
Date: Tue, 13 Dec 2011 20:43:14 +0530 [thread overview]
Message-ID: <1323789196-4942-1-git-send-email-amit.kachhap@linaro.org> (raw)
PATCH 1) [thermal: Add a new trip type to use cooling device instance number]
This patch adds a new trip type THERMAL_TRIP_STATE_ACTIVE which passes
cooling device instance number and may be helpful for cpufreq cooling devices
to take the correct cooling action.
PATCH 2) [thermal: Add generic cpu cooling implementation]
This patch adds generic cpu cooling low level implementation through frequency
clipping and cpu hotplug. In future, other cpu related cooling devices may be
added here. An ACPI version of this already exists(drivers/acpi/processor_thermal.c).
But this will be useful for platforms like ARM using the generic thermal interface
along with the generic cpu cooling devices. The cooling device registration API's
return cooling device pointers which can be easily binded with the thermal zone
trip points.
Amit Daniel Kachhap (2):
thermal: Add a new trip type to use cooling device instance number
thermal: Add generic cpu cooling implementation
Documentation/thermal/cpu-cooling-api.txt | 52 +++++
Documentation/thermal/sysfs-api.txt | 4 +-
drivers/thermal/Kconfig | 11 +
drivers/thermal/Makefile | 1 +
drivers/thermal/cpu_cooling.c | 302 +++++++++++++++++++++++++++++
drivers/thermal/thermal_sys.c | 27 +++-
include/linux/cpu_cooling.h | 45 +++++
include/linux/thermal.h | 1 +
8 files changed, 440 insertions(+), 3 deletions(-)
create mode 100644 Documentation/thermal/cpu-cooling-api.txt
create mode 100644 drivers/thermal/cpu_cooling.c
create mode 100644 include/linux/cpu_cooling.h
next reply other threads:[~2011-12-13 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 15:13 Amit Daniel Kachhap [this message]
2011-12-13 15:13 ` [RFC PATCH 1/2] thermal: Add a new trip type to use cooling device instance number Amit Daniel Kachhap
2011-12-20 12:37 ` [linux-pm] " Vincent Guittot
[not found] ` <CAK44p232PbvGRXKB7_3TYn0Q3iqgRJg6Qv81W_EwXCHL+79baA@mail.gmail.com>
2011-12-21 5:11 ` Amit Kachhap
2012-01-11 8:12 ` Rob Lee
2012-01-13 4:02 ` Amit Kachhap
2012-02-01 14:49 ` Matthew Garrett
2012-02-02 7:16 ` Amit Kachhap
2011-12-13 15:13 ` [RFC PATCH 2/2] thermal: Add generic cpu cooling implementation Amit Daniel Kachhap
2012-01-11 8:02 ` Rob Lee
2012-01-13 3:50 ` Amit Kachhap
2012-01-16 14:13 ` Rob Lee
2012-02-01 14:57 ` Matthew Garrett
2012-02-02 9:16 ` Amit Kachhap
2012-02-07 8:25 ` [linux-pm] " Eduardo Valentin
2012-02-07 18:21 ` Amit Kachhap
2012-02-07 19:34 ` Eduardo Valentin
2012-01-19 9:17 ` [RFC PATCH 0/2] thermal: Add generic cpu cooling devices according to thermal framework Amit Kachhap
2012-02-03 7:12 ` Zhang Rui
2012-02-03 12:13 ` Amit Kachhap
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=1323789196-4942-1-git-send-email-amit.kachhap@linaro.org \
--to=amit.kachhap@linaro.org \
--cc=lenb@kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg59@srcf.ucam.org \
--cc=patches@linaro.org \
--cc=rui.zhang@intel.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 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).