[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bc0f90e4-dc66-470b-a771-e52e451aaec4@oss.qualcomm.com>
Date: Thu, 23 Jan 2025 12:59:34 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Akhil P Oommen <quic_akhilpo@...cinc.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Neil Armstrong <neil.armstrong@...aro.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sm8650: setup gpu thermal with
higher temperatures
On 22.01.2025 3:09 PM, Akhil P Oommen wrote:
> On 1/17/2025 2:50 AM, Konrad Dybcio wrote:
>> On 13.01.2025 11:28 AM, 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.
>>
>> What's this for then? Just reacting to thermal pressure?
>>
>> https://git.codelinaro.org/clo/le/platform/vendor/qcom/opensource/graphics-kernel/-/commit/e4387d101d14965c8f2c67e10a6a9499c1a88af4
>>
>
> I don't think those TSENSE configs matters on SM8650 in production.
OK, thanks
Konrad
Powered by blists - more mailing lists