From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Neil Armstrong <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 0/2] arm64: dts: qcom: sm8650: rework CPU & GPU thermal zones
Date: Fri, 3 Jan 2025 15:43:04 +0100 [thread overview]
Message-ID: <b305ec90-26b6-4dfa-830a-4ff3acd9caf5@oss.qualcomm.com> (raw)
In-Reply-To: <20250103-topic-sm8650-thermal-cpu-idle-v1-0-faa1f011ecd9@linaro.org>
On 3.01.2025 3:38 PM, Neil Armstrong wrote:
> On the SM8650 platform, the dynamic clock and voltage scaling (DCVS) for
> the CPUs and GPU is handled by hardware & firmware using factory and
> form-factor determined parameters in order to maximize frequency while
> keeping the temperature way below the junction temperature where the SoC
> would experience a thermal shutdown if not permanent damages.
>
> On the other side, the High Level Ooperating System (HLOS), like Linux,
> is able to adjust the CPU and GPU frequency using the internal SoC
> temperature sensors (here tsens) and it's UP/LOW interrupts, but it
> effectly does the same work twice in an less effective manner.
>
> Let's take the Hardware & Firmware action in account and design the
> thermal zones trip points and cooling devices mapping to use the HLOS
> as a safety warant in case the platform experiences a temperature surge
> to helpfully avoid a thermal shutdown and handle the scenario gracefully.
>
> On the CPU side, the LMh hardware does the DCVS control loop, so
> let's set higher trip points temperatures closer to the junction
> and thermal shutdown temperatures and add some idle injection cooling
> device with 100% duty cycle for each CPU that would act as emergency
> action to avoid the thermal shutdown.
>
> On the GPU side, the GPU Management Unit (GMU) acts as the DCVS
> control loop, but since we can't perform idle injection, let's
> also set higher trip points temperatures closer to the junction
> and thermal shutdown temperatures to reduce the GPU frequency only
> as an emergency action before the thermal shutdown.
>
> Those 2 changes optimizes the thermal management design by avoiding
> concurrent thermal management, calculations & avoidable interrupts
> by moving the HLOS management to a last resort emergency if the
> Hardware & Firmwares fails to avoid a thermal shutdown.
>
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> ---
Got any numbers to back this?
Konrad
next prev parent reply other threads:[~2025-01-03 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 14:38 [PATCH 0/2] arm64: dts: qcom: sm8650: rework CPU & GPU thermal zones Neil Armstrong
2025-01-03 14:38 ` [PATCH 1/2] arm64: dts: qcom: sm8650: setup cpu thermal with idle on high temperatures Neil Armstrong
2025-01-06 23:39 ` Bjorn Andersson
2025-01-07 8:13 ` Neil Armstrong
2025-01-08 3:11 ` Bjorn Andersson
2025-01-08 9:15 ` Neil Armstrong
2025-01-09 15:18 ` Konrad Dybcio
2025-01-10 9:41 ` neil.armstrong
2025-01-09 21:01 ` Bjorn Andersson
2025-01-10 9:40 ` Neil Armstrong
2025-01-03 14:38 ` [PATCH 2/2] arm64: dts: qcom: sm8650: setup gpu thermal with higher temperatures Neil Armstrong
2025-01-03 20:00 ` Rob Clark
2025-01-06 9:02 ` Neil Armstrong
2025-01-03 14:43 ` Konrad Dybcio [this message]
2025-01-03 14:49 ` [PATCH 0/2] arm64: dts: qcom: sm8650: rework CPU & GPU thermal zones Neil Armstrong
2025-01-09 15:20 ` 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=b305ec90-26b6-4dfa-830a-4ff3acd9caf5@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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