From: Amit Kucheria <amit.kucheria@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org,
edubezval@gmail.com, andy.gross@linaro.org, tdas@codeaurora.org,
swboyd@chromium.org, dianders@chromium.org, mka@chromium.org,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: [PATCH v3 0/1] Thermal throttling for SDM845
Date: Mon, 21 Jan 2019 23:38:33 +0530 [thread overview]
Message-ID: <cover.1548093127.git.amit.kucheria@linaro.org> (raw)
Only one patch left in this series. This patch can be applied independently
but needs [1] and [2] merged to have throttling work out of the box.
Changes since v2:
- Split up the series into auto-register series for cpufreq[1] and
miscellaneous patches[2][3]. [1] and [2] are needed for this patch to
work.
- Merged the two DT patches into one. We end up with 2 passive and 1
critical trip point.
- Remove unncessary cooling map for critical trip point, we're shutting down at
that trip, duh!
[1] https://lore.kernel.org/lkml/cover.1548084260.git.amit.kucheria@linaro.org/
[2] https://lore.kernel.org/patchwork/patch/1033953/
[3] https://lore.kernel.org/patchwork/cover/1033970/
Amit Kucheria (1):
arm64: dts: sdm845: wireup the thermal trip points to cpufreq
arch/arm64/boot/dts/qcom/sdm845.dtsi | 225 +++++++++++++++++++++++++--
1 file changed, 209 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-21 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 18:08 Amit Kucheria [this message]
2019-01-21 18:08 ` [PATCH v3 1/1] arm64: dts: sdm845: wireup the thermal trip points to cpufreq Amit Kucheria
2019-01-23 2:12 ` Matthias Kaehlcke
2019-01-24 23:35 ` Matthias Kaehlcke
2019-01-25 22:20 ` Matthias Kaehlcke
2019-02-06 10:35 ` Amit Kucheria
2019-02-06 19:34 ` Matthias Kaehlcke
2019-02-07 1:57 ` Matthias Kaehlcke
2019-02-07 4:39 ` Amit Kucheria
2019-02-07 19:10 ` Matthias Kaehlcke
2019-02-06 0:04 ` Eduardo Valentin
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.1548093127.git.amit.kucheria@linaro.org \
--to=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=edubezval@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=tdas@codeaurora.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).