Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>,
	andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: quic_srichara@quicinc.com, quic_varada@quicinc.com,
	kathiravan.thirumoorthy@oss.qualcomm.com
Subject: Re: [PATCH v1] arm64: dts: qcom: ipq5424: add cooling maps for CPU thermal zones
Date: Thu, 23 Oct 2025 16:26:36 +0200	[thread overview]
Message-ID: <a58956a3-b9cd-408f-98af-7ec31f2277dd@oss.qualcomm.com> (raw)
In-Reply-To: <053cdafd-1abd-4f1c-8f48-9da38591fcaa@quicinc.com>

On 10/23/25 2:21 PM, Manikanta Mylavarapu wrote:
> 
> 
> On 10/23/2025 2:09 PM, Konrad Dybcio wrote:
>> On 10/23/25 6:38 AM, Manikanta Mylavarapu wrote:
>>> Add cooling-maps to the cpu1, cpu2, and cpu3 thermal zones to associate
>>> passive trip points with CPU cooling devices. This enables proper
>>> thermal mitigation by allowing the thermal framework to throttle CPUs
>>> based on temperature thresholds. Also, label the trip points to allow
>>> referencing them in the cooling maps.
>>>
>>> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
>>> ---
>>
>> [...]
>>
>>>  		cpu1-thermal {
>>> @@ -1254,18 +1269,28 @@ cpu1-thermal {
>>>  			thermal-sensors = <&tsens 12>;
>>>  
>>>  			trips {
>>> -				cpu-critical {
>>> +				cpu1_crit: cpu-critical {
>>>  					temperature = <120000>;
>>>  					hysteresis = <9000>;
>>>  					type = "critical";
>>>  				};
>>>  
>>> -				cpu-passive {
>>> +				cpu1_alert: cpu-passive {
>>>  					temperature = <110000>;
>>>  					hysteresis = <9000>;
>>>  					type = "passive";
>>>  				};
>>
>> This means "software will start throttling the cpufreq at 110C"
>>
>> Is this what you want?
>>
> 
> Hi Konrad,
> 
> Thank you for reviewing the patch.
> 
> Yes, the intent is to initiate software-based cpufreq throttling at 110°C.
> 
>> Also, is there nothing like LMH on this platform that throttles the
>> device way earlier, without OS intervention?
>>
> 
> IPQ5424 platform does not support LMH.

Thanks for confirming

Usually it seems like the trips are ordered by temperature but I don't
think there's a strong preference

The hysteresis value is a little high, but I'm assuming that came out of
some internal tuning

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

  reply	other threads:[~2025-10-23 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  4:38 [PATCH v1] arm64: dts: qcom: ipq5424: add cooling maps for CPU thermal zones Manikanta Mylavarapu
2025-10-23  8:39 ` Konrad Dybcio
2025-10-23 12:21   ` Manikanta Mylavarapu
2025-10-23 14:26     ` Konrad Dybcio [this message]
2025-10-27 18:47 ` Bjorn Andersson
2025-10-27 22:37 ` Bjorn Andersson

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=a58956a3-b9cd-408f-98af-7ec31f2277dd@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kathiravan.thirumoorthy@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_mmanikan@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.com \
    --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