From: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
To: 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,
Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Subject: [PATCH] arm64: dts: qcom: monaco: Add passive polling-delay for gpuss thermal zones
Date: Fri, 03 Jul 2026 10:53:39 +0530 [thread overview]
Message-ID: <20260703-gpu_polling_delay-v1-1-132de4dd3cad@oss.qualcomm.com> (raw)
Introduce a passive polling delay to ensure more than one "passive"
thermal point is considered when throttling the GPU thermal zones.
Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/monaco.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/monaco.dtsi b/arch/arm64/boot/dts/qcom/monaco.dtsi
index e4c8466f941b..a3943b6f299d 100644
--- a/arch/arm64/boot/dts/qcom/monaco.dtsi
+++ b/arch/arm64/boot/dts/qcom/monaco.dtsi
@@ -7895,6 +7895,7 @@ cpu-critical {
gpuss-0-thermal {
thermal-sensors = <&tsens0 5>;
+ polling-delay-passive = <10>;
trips {
gpuss0_alert0: trip-point0 {
@@ -8028,6 +8029,7 @@ cpu-critical {
gpuss-1-thermal {
thermal-sensors = <&tsens1 5>;
+ polling-delay-passive = <10>;
trips {
gpuss1_alert0: trip-point0 {
---
base-commit: 4f441960e691d37c880d2cc004de06bb5b6bd5e4
change-id: 20260703-gpu_polling_delay-9c0c642149cc
Best regards,
--
Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
next reply other threads:[~2026-07-03 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 5:23 Gaurav Kohli [this message]
2026-07-03 13:34 ` [PATCH] arm64: dts: qcom: monaco: Add passive polling-delay for gpuss thermal zones 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=20260703-gpu_polling_delay-v1-1-132de4dd3cad@oss.qualcomm.com \
--to=gaurav.kohli@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=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