[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ff12e104-da8b-4800-bfbe-a006ffe1b840@collabora.com>
Date: Tue, 21 May 2024 16:19:19 +0200
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
To: Julien Panis <jpanis@...libre.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Matthias Brugger <matthias.bgg@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Nicolas Pitre <npitre@...libre.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v4 4/4] arm64: dts: mediatek: mt8188: add default thermal
zones
Il 21/05/24 16:05, Julien Panis ha scritto:
> From: Nicolas Pitre <npitre@...libre.com>
>
> Inspired by the vendor kernel but adapted to the upstream thermal
> driver version.
>
> Signed-off-by: Nicolas Pitre <npitre@...libre.com>
> Signed-off-by: Julien Panis <jpanis@...libre.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8188.dtsi | 432 +++++++++++++++++++++++++++++++
> 1 file changed, 432 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8188.dtsi b/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> index a9f1b9db54a6..2b0f3e03acc1 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8188.dtsi
> @@ -12,6 +12,8 @@
> #include <dt-bindings/pinctrl/mediatek,mt8188-pinfunc.h>
> #include <dt-bindings/power/mediatek,mt8188-power.h>
> #include <dt-bindings/reset/mt8188-resets.h>
> +#include <dt-bindings/thermal/thermal.h>
> +#include <dt-bindings/thermal/mediatek,lvts-thermal.h>
>
> / {
> compatible = "mediatek,mt8188";
.snip..
> +
> + gpu1-thermal {
You forgot to implement my feedback to Nicolas - this must be gpu-thermal
> + polling-delay = <1000>;
> + polling-delay-passive = <250>;
> + thermal-sensors = <&lvts_ap MT8188_AP_GPU1>;
> +
> + trips {
> + gpu1_alert0: trip-alert0 {
> + temperature = <85000>;
> + hysteresis = <2000>;
> + type = "passive";
> + };
> +
> + gpu1_alert1: trip-alert1 {
> + temperature = <95000>;
> + hysteresis = <2000>;
> + type = "hot";
> + };
> +
> + gpu1_crit: trip-crit {
> + temperature = <100000>;
> + hysteresis = <0>;
> + type = "critical";
> + };
> + };
> + };
> +
> + gpu2-thermal {
..and for consistency with the other SoCs, this must be gpu1-thermal.
> + polling-delay = <1000>;
> + polling-delay-passive = <250>;
> + thermal-sensors = <&lvts_ap MT8188_AP_GPU2>;
> +
> + trips {
> + gpu2_alert0: trip-alert0 {
> + temperature = <85000>;
> + hysteresis = <2000>;
> + type = "passive";
> + };
> +
> + gpu2_alert1: trip-alert1 {
> + temperature = <95000>;
> + hysteresis = <2000>;
> + type = "hot";
> + };
> +
> + gpu2_crit: trip-crit {
> + temperature = <100000>;
> + hysteresis = <0>;
> + type = "critical";
> + };
> + };
> + };
> +
> + soc1-thermal {
Any idea of what can "soc1" ever be? What measurement point is that?
VPU? IMG? INFRA?
soc1, soc2, soc3 make little sense.
Regards,
Angelo
Powered by blists - more mailing lists