From: Amit Kucheria <amit.kucheria@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org,
viresh.kumar@linaro.org, edubezval@gmail.com,
andy.gross@linaro.org, tdas@codeaurora.org, swboyd@chromium.org,
dianders@chromium.org, mka@chromium.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
David Brown <david.brown@linaro.org>,
Javi Merino <javi.merino@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:CPU FREQUENCY DRIVERS" <linux-pm@vger.kernel.org>
Subject: [PATCH v2 0/9] Thermal throttling for SDM845
Date: Mon, 14 Jan 2019 15:51:02 +0530 [thread overview]
Message-ID: <cover.1547458732.git.amit.kucheria@linaro.org> (raw)
Add support for thermal throttling on SDM845.
We introduce a generic flag to be used by cpufreq drivers to tell the
cpufreq core to auto-register a thermal cooling device.
There are a few miscellaneous fixes to keep checkpatch happy.
If this approach is acceptable I can send a series converting other cpufreq
drivers to use this flag and get rid of driver code.
Amit Kucheria (9):
[ALREADY QUEUED] cpufreq: qcom-hw: Move to device_initcall
drivers: thermal: of-thermal: Print name of device node with error
drivers: cpufreq: Add thermal_cooling_device pointer to struct
cpufreq_policy
cpufreq: Add a flag to auto-register a cooling device
cpufreq: Replace open-coded << with BIT()
cpufreq: qcom-hw: Register as a cpufreq cooling device
arm64: dts: sdm845: Increase alert trip point to 95 degrees
arm64: dts: sdm845: wireup the thermal trip points to cpufreq
thermal: cpu_cooling: Clarify error message
arch/arm64/boot/dts/qcom/sdm845.dtsi | 193 +++++++++++++++++++++++----
drivers/cpufreq/cpufreq.c | 13 ++
drivers/cpufreq/qcom-cpufreq-hw.c | 5 +-
drivers/thermal/cpu_cooling.c | 2 +-
drivers/thermal/of-thermal.c | 4 +-
include/linux/cpufreq.h | 34 +++--
6 files changed, 210 insertions(+), 41 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-14 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 10:21 Amit Kucheria [this message]
2019-01-14 10:21 ` [PATCH v2 7/9] arm64: dts: sdm845: Increase alert trip point to 95 degrees Amit Kucheria
2019-01-14 10:21 ` [PATCH v2 8/9] arm64: dts: sdm845: wireup the thermal trip points to cpufreq Amit Kucheria
2019-01-14 22:01 ` Matthias Kaehlcke
2019-01-21 18:10 ` Amit Kucheria
2019-01-22 18:18 ` Matthias Kaehlcke
2019-01-14 10:27 ` [PATCH v2 0/9] Thermal throttling for SDM845 Rafael J. Wysocki
2019-01-14 10:34 ` Amit Kucheria
2019-01-14 16:52 ` Amit Kucheria
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=cover.1547458732.git.amit.kucheria@linaro.org \
--to=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=edubezval@gmail.com \
--cc=javi.merino@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=swboyd@chromium.org \
--cc=tdas@codeaurora.org \
--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).