From: Akhil P Oommen <quic_akhilpo@quicinc.com>
To: <neil.armstrong@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sm8650: setup gpu thermal with higher temperatures
Date: Thu, 16 Jan 2025 00:39:25 +0530 [thread overview]
Message-ID: <82f44295-a3c9-487c-98db-916cdc30fc4f@quicinc.com> (raw)
In-Reply-To: <c09192f4-30ae-4dd8-bc88-2aaf02088374@linaro.org>
On 1/13/2025 4:15 PM, Neil Armstrong wrote:
> Hi,
>
> On 13/01/2025 11:28, Akhil P Oommen wrote:
>> On 1/10/2025 4:06 PM, Neil Armstrong wrote:
>>> On the SM8650, the dynamic clock and voltage scaling (DCVS) for the GPU
>>> is done in an hardware controlled loop by the GPU Management Unit (GMU).
>>>
>>> Since the GMU does a better job at maintaining the GPUs temperature
>>> in an
>>> acceptable range by taking in account more parameters like the die
>>> characteristics or other internal sensors, it makes no sense to try
>>> and reproduce a similar set of constraints with the Linux devfreq
>>> thermal
>>> core.
>>
>> Just FYI, this description is incorrect. SM8650's GMU doesn't do any
>> sort of thermal management.
>
> Ok, thx for confirming this, in our tests the temperature steadily stayed
> at a max trip point when setting them higher. But perhaps it's a side
> effect
> of other mitigations.
>
> Are the new trip points still ok ? they are derived from the downstream DT.
I don't have expertise on the thermal side. But in my non-expert
opinion, it is fine to use a similar configuration from downstream.
-Akhil.
>
> Thanks,
> Neil
>
>>
>> -Akhil.
>>
>>>
>>> Instead, set higher temperatures in the GPU trip points corresponding to
>>> the temperatures provided by Qualcomm in the dowstream source, which
>>> will
>>> trigger the devfreq thermal core if the GMU cannot handle the
>>> temperature
>>> surge, and try our best to avoid reaching the critical temperature trip
>>> point which should trigger an inevitable thermal shutdown.
>>>
>>> Fixes: 497624ed5506 ("arm64: dts: qcom: sm8650: Throttle the GPU when
>>> overheating")
>>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>>> ---
>>> arch/arm64/boot/dts/qcom/sm8650.dtsi | 48 +++++++++++++++++
>>> +------------------
>>> 1 file changed, 24 insertions(+), 24 deletions(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/sm8650.dtsi b/arch/arm64/boot/
>>> dts/qcom/sm8650.dtsi
>>> index
>>> 95509ce2713d4fcc3dbe0c5cd5827312d5681af4..e9fcf05cb084b7979ecf0f4712fed332e9f4b07a 100644
>>> --- a/arch/arm64/boot/dts/qcom/sm8650.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/sm8650.dtsi
>>> @@ -6173,19 +6173,19 @@ map0 {
>>> trips {
>>> gpu0_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6206,19 +6206,19 @@ map0 {
>>> trips {
>>> gpu1_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6239,19 +6239,19 @@ map0 {
>>> trips {
>>> gpu2_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6272,19 +6272,19 @@ map0 {
>>> trips {
>>> gpu3_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6305,19 +6305,19 @@ map0 {
>>> trips {
>>> gpu4_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6338,19 +6338,19 @@ map0 {
>>> trips {
>>> gpu5_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6371,19 +6371,19 @@ map0 {
>>> trips {
>>> gpu6_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>> @@ -6404,19 +6404,19 @@ map0 {
>>> trips {
>>> gpu7_alert0: trip-point0 {
>>> - temperature = <85000>;
>>> + temperature = <95000>;
>>> hysteresis = <1000>;
>>> type = "passive";
>>> };
>>> trip-point1 {
>>> - temperature = <90000>;
>>> + temperature = <115000>;
>>> hysteresis = <1000>;
>>> type = "hot";
>>> };
>>> trip-point2 {
>>> - temperature = <110000>;
>>> + temperature = <125000>;
>>> hysteresis = <1000>;
>>> type = "critical";
>>> };
>>>
>>
>
next prev parent reply other threads:[~2025-01-15 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 10:36 [PATCH v2 0/2] arm64: dts: qcom: sm8650: rework CPU & GPU thermal zones Neil Armstrong
2025-01-10 10:36 ` [PATCH v2 1/2] arm64: dts: qcom: sm8650: drop cpu thermal passive trip points Neil Armstrong
2025-01-10 10:36 ` [PATCH v2 2/2] arm64: dts: qcom: sm8650: setup gpu thermal with higher temperatures Neil Armstrong
2025-01-13 10:28 ` Akhil P Oommen
2025-01-13 10:45 ` Neil Armstrong
2025-01-15 19:09 ` Akhil P Oommen [this message]
2025-01-16 21:20 ` Konrad Dybcio
2025-01-22 14:09 ` Akhil P Oommen
2025-01-23 11:59 ` Konrad Dybcio
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=82f44295-a3c9-487c-98db-916cdc30fc4f@quicinc.com \
--to=quic_akhilpo@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@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