From: Michael Riesch <michael.riesch@wolfvision.net>
To: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Alex Bee <knaerzche@gmail.com>, Liang Chen <cl@rock-chips.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH v6 3/5] arm64: dts: rockchip: add cooling map and trip points for gpu to rk356x
Date: Wed, 9 Feb 2022 22:55:47 +0100 [thread overview]
Message-ID: <20220209215549.94524-4-michael.riesch@wolfvision.net> (raw)
In-Reply-To: <20220209215549.94524-1-michael.riesch@wolfvision.net>
From: Alex Bee <knaerzche@gmail.com>
RK356x SoCs have a second thermal sensor for the GPU. This adds the
cooling map and trip points for it to make use of its contribution as
a cooling device.
Signed-off-by: Alex Bee <knaerzche@gmail.com>
Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
---
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 27 ++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
index 50bbea862a6a..37194d735028 100644
--- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
@@ -1093,6 +1093,33 @@ gpu_thermal: gpu-thermal {
polling-delay = <1000>; /* milliseconds */
thermal-sensors = <&tsadc 1>;
+
+ trips {
+ gpu_threshold: gpu-threshold {
+ temperature = <70000>;
+ hysteresis = <2000>;
+ type = "passive";
+ };
+ gpu_target: gpu-target {
+ temperature = <75000>;
+ hysteresis = <2000>;
+ type = "passive";
+ };
+ gpu_crit: gpu-crit {
+ temperature = <95000>;
+ hysteresis = <2000>;
+ type = "critical";
+ };
+ };
+
+ cooling-maps {
+ map0 {
+ trip = <&gpu_target>;
+ cooling-device =
+ <&gpu THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
+ };
+ };
+
};
};
--
2.30.2
next prev parent reply other threads:[~2022-02-09 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 21:55 [PATCH v6 0/5] Add GPU for RK356x SoCs Michael Riesch
2022-02-09 21:55 ` [PATCH v6 1/5] dt-bindings: gpu: mali-bifrost: describe clocks for the rk356x gpu Michael Riesch
2022-02-11 17:07 ` Rob Herring
2022-02-09 21:55 ` [PATCH v6 2/5] arm64: dts: rockchip: add gpu node to rk356x Michael Riesch
2022-02-09 21:55 ` Michael Riesch [this message]
2022-02-09 21:55 ` [PATCH v6 4/5] arm64: dts: rockchip: enable the gpu on quartz64-a Michael Riesch
2022-02-09 21:55 ` [PATCH v6 5/5] arm64: dts: rockchip: enable the gpu on rk3568-evb1-v10 Michael Riesch
2022-02-11 19:24 ` (subset) [PATCH v6 0/5] Add GPU for RK356x SoCs Heiko Stuebner
2022-02-11 19:30 ` Heiko Stuebner
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=20220209215549.94524-4-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=airlied@linux.ie \
--cc=cl@rock-chips.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).