SDM670 Basic SoC thermal zones
Subsystems (5)
v5 cover SDM670 Basic SoC thermal zones
This adds support for the thermal sensor, for thermal-based CPU throttling via LMh, and for thermal zones.
Changes since v4 (https://lore.kernel.org/r/[email protected]):
- use simple comparison to differentiate between cluster 0 and 1 (1/2)
- drop applied dt-bindings patches (previously 1-2/4)
Changes since v3 (https://lore.kernel.org/r/[email protected]):
- support LMh clusters starting at CPU 6 (dt-bindings tag dropped) (3/4)
Changes since v2 (https://lore.kernel.org/r/[email protected]):
- remove cooling from memory thermal zone (3/3)
Changes since v1 (https://lore.kernel.org/r/[email protected]):
- add review tag from Krzysztof (1/3)
- replace CPU thermal zones with lmh (2/3, 3/3)
Richard Acayan (2):
thermal/qcom/lmh: support SDM670 and its CPU clusters
arm64: dts: qcom: sdm670: add thermal zones and thermal devices
arch/arm64/boot/dts/qcom/sdm670.dtsi | 400 +++++++++++++++++++++++++++ drivers/thermal/qcom/lmh.c | 54 ++-- 2 files changed, 434 insertions(+), 20 deletions(-)
Signature · 1 line
2.53.0
PATCH v5 1/2 thermal/qcom/lmh: support SDM670 and its CPU clusters
The LMh driver was made for Qualcomm SoCs with clusters of 4 CPUs, but some SoCs divide the CPUs into different sizes of clusters. In SDM670, the first 6 CPUs are in the little cluster and the next 2 are in the big cluster. Define the clusters in the match data and define the different cluster configuration for SDM670.
Currently, this tolerates linking to any CPU in a given cluster.
--- drivers/thermal/qcom/lmh.c | 54 ++++++++++++++++++++++++-------------- 1 file changed, 34 insertions(+), 20 deletions(-)
drivers/thermal/qcom/lmh.c +34 -20
@@ -30,14 +30,17 @@#define LMH_REG_DCVS_INTR_CLR 0x8 -#define LMH_ENABLE_ALGOS 1 -struct lmh_hw_data {void __iomem *base;struct irq_domain *domain;int irq; }; +struct lmh_soc_data { +bool enable_algos; +unsigned int clus1_start_idx; +}; +static irqreturn_t lmh_handle_irq (int hw_irq,void *data) {struct lmh_hw_data *lmh_data = data;
@@ -100,8 +103,8 @@ static int lmh_probe(struct platform_device *pdev)struct device_node *np = dev->of_node;struct device_node *cpu_node;struct lmh_hw_data *lmh_data; +const struct lmh_soc_data *match_data;int temp_low, temp_high, temp_arm, cpu_id, ret; -unsigned int enable_alg;u32 node_id;if (!qcom_scm_is_available ())
@@ -121,6 +124,11 @@ static int lmh_probe(struct platform_device *pdev) cpu_id =of_cpu_node_to_id (cpu_node);of_node_put (cpu_node); +if (cpu_id <0 ) { +dev_err (dev,"Wrong CPU id associated with LMh node\n" ); +return -EINVAL ; + } + ret =of_property_read_u32 (np,"qcom,lmh-temp-high-millicelsius" , &temp_high);if (ret) {dev_err (dev,"missing qcom,lmh-temp-high-millicelsius property\n" );
@@ -139,26 +147,16 @@ static int lmh_probe(struct platform_device *pdev)return ret; } -/* -* Only sdm845 has lmh hardware currently enabled from hlos. If this is needed -* for other platforms, revisit this to check if the <cpu-id, node-id> should be part -* of a dt match table. -*/ -if (cpu_id ==0 ) { + match_data =of_device_get_match_data (dev); +if (cpu_id < match_data->clus1_start_idx) node_id =LMH_CLUSTER0_NODE_ID ; - }else if (cpu_id ==4 ) { +else node_id =LMH_CLUSTER1_NODE_ID ; - }else { -dev_err (dev,"Wrong CPU id associated with LMh node\n" ); -return -EINVAL ; - }if (!qcom_scm_lmh_dcvsh_available ())return -EINVAL ; - enable_alg = (uintptr_t )of_device_get_match_data (dev); - -if (enable_alg) { +if (match_data->enable_algos) { ret =qcom_scm_lmh_dcvsh (LMH_SUB_FN_CRNT ,LMH_ALGO_MODE_ENABLE ,1 ,LMH_NODE_DCVS , node_id,0 );if (ret)
@@ -231,10 +229,26 @@ static int lmh_probe(struct platform_device *pdev)return 0 ; } +static const struct lmh_soc_data sdm670_lmh_data = { + .enable_algos = true, + .clus1_start_idx =6 , +}; + +static const struct lmh_soc_data sdm845_lmh_data = { + .enable_algos = true, + .clus1_start_idx =4 , +}; + +static const struct lmh_soc_data sm8150_lmh_data = { + .enable_algos = false, + .clus1_start_idx =4 , +}; +static const struct of_device_id lmh_table[] = { - { .compatible ="qcom,sc8180x-lmh" , }, - { .compatible ="qcom,sdm845-lmh" , .data = (void *)LMH_ENABLE_ALGOS }, - { .compatible ="qcom,sm8150-lmh" , }, + { .compatible ="qcom,sc8180x-lmh" , .data = &sm8150_lmh_data }, + { .compatible ="qcom,sdm670-lmh" , .data = &sdm670_lmh_data }, + { .compatible ="qcom,sdm845-lmh" , .data = &sdm845_lmh_data }, + { .compatible ="qcom,sm8150-lmh" , .data = &sm8150_lmh_data }, {} };MODULE_DEVICE_TABLE (of, lmh_table);
Signature · 1 line
2.53.0
Re: [PATCH v5 1/2] thermal/qcom/lmh: support SDM670 and its CPU clusters
Quoted 6 lines · Richard Acayan
The LMh driver was made for Qualcomm SoCs with clusters of 4 CPUs, but some SoCs divide the CPUs into different sizes of clusters. In SDM670, the first 6 CPUs are in the little cluster and the next 2 are in the big cluster. Define the clusters in the match data and define the different cluster configuration for SDM670.
Quoted 7 lines
Currently, this tolerates linking to any CPU in a given cluster.
Signed-off-by Richard Acayan <[email protected]>--- drivers/thermal/qcom/lmh.c | 54 ++++++++++++++++++++++++-------------- 1 file changed, 34 insertions(+), 20 deletions(-)
Signature · 2 lines
With best wishes Dmitry
Re: [PATCH v5 1/2] thermal/qcom/lmh: support SDM670 and its CPU clusters
In reply to Richard AcayanQuoted 10 lines · Richard Acayan
The LMh driver was made for Qualcomm SoCs with clusters of 4 CPUs, but some SoCs divide the CPUs into different sizes of clusters. In SDM670, the first 6 CPUs are in the little cluster and the next 2 are in the big cluster. Define the clusters in the match data and define the different cluster configuration for SDM670.
Currently, this tolerates linking to any CPU in a given cluster.
Signed-off-by Richard Acayan <[email protected]>---
[...]
drivers/thermal/qcom/lmh.c static int lmh_probe(struct platform_device *pdev) · line 130
Quoted 4 lines
drivers/thermal/qcom/lmh.c +4
-0+if (cpu_id <0 ) { +dev_err (dev,"Wrong CPU id associated with LMh node\n" ); +return -EINVAL ; + }
nit: try to use 'return dev_err_probe(dev, ret, "....") in the future
Konrad
Re: [PATCH v5 1/2] thermal/qcom/lmh: support SDM670 and its CPU clusters
Quoted 14 lines · Konrad Dybcio
Quoted 10 lines · Richard Acayan
The LMh driver was made for Qualcomm SoCs with clusters of 4 CPUs, but some SoCs divide the CPUs into different sizes of clusters. In SDM670, the first 6 CPUs are in the little cluster and the next 2 are in the big cluster. Define the clusters in the match data and define the different cluster configuration for SDM670.
Currently, this tolerates linking to any CPU in a given cluster.
Signed-off-by Richard Acayan <[email protected]>---
Reviewed-by Konrad Dybcio <[email protected]>
Quoted 7 lines
[...]
drivers/thermal/qcom/lmh.c static int lmh_probe(struct platform_device *pdev) · line 130
Quoted 4 lines
drivers/thermal/qcom/lmh.c +4
-0+if (cpu_id <0 ) { +dev_err (dev,"Wrong CPU id associated with LMh node\n" ); +return -EINVAL ; + }nit: try to use 'return
dev_err_probe(dev, ret, "....")in the future
Does "in the future" apply to the inevitable next revision? This would be the first occurrence of dev_err_probe in this driver and the error path was just cut-and-paste.
Re: [PATCH v5 1/2] thermal/qcom/lmh: support SDM670 and its CPU clusters
Quoted 23 lines · Richard Acayan
Quoted 14 lines · Konrad Dybcio
Quoted 10 lines · Richard Acayan
The LMh driver was made for Qualcomm SoCs with clusters of 4 CPUs, but some SoCs divide the CPUs into different sizes of clusters. In SDM670, the first 6 CPUs are in the little cluster and the next 2 are in the big cluster. Define the clusters in the match data and define the different cluster configuration for SDM670.
Currently, this tolerates linking to any CPU in a given cluster.
Signed-off-by Richard Acayan <[email protected]>---
Reviewed-by Konrad Dybcio <[email protected]>Quoted 7 lines
[...]
drivers/thermal/qcom/lmh.c static int lmh_probe(struct platform_device *pdev) · line 130
Quoted 4 lines
drivers/thermal/qcom/lmh.c +4
-0+if (cpu_id <0 ) { +dev_err (dev,"Wrong CPU id associated with LMh node\n" ); +return -EINVAL ; + }nit: try to use 'return
dev_err_probe(dev, ret, "....")in the future
Quoted 3 lines
Does "in the future" apply to the inevitable next revision? This would be the first occurrence of
dev_err_probein this driver and the error path was just cut-and-paste.
Not necessarily, 'in the future' meaning 'in your future patches'
Konrad
Re: [PATCH v5 1/2] thermal/qcom/lmh: support SDM670 and its CPU clusters
In reply to Richard AcayanQuoted 9 lines · Richard Acayan
The LMh driver was made for Qualcomm SoCs with clusters of 4 CPUs, but some SoCs divide the CPUs into different sizes of clusters. In SDM670, the first 6 CPUs are in the little cluster and the next 2 are in the big cluster. Define the clusters in the match data and define the different cluster configuration for SDM670.
Currently, this tolerates linking to any CPU in a given cluster.
Signed-off-by Richard Acayan <[email protected]>
Regards,
Bjorn
Quoted 114 lines
--- drivers/thermal/qcom/lmh.c | 54 ++++++++++++++++++++++++-------------- 1 file changed, 34 insertions(+), 20 deletions(-)drivers/thermal/qcom/lmh.c +34
-20@@ -30,14 +30,17 @@#define LMH_REG_DCVS_INTR_CLR 0x8 -#define LMH_ENABLE_ALGOS 1 -struct lmh_hw_data {void __iomem *base;struct irq_domain *domain;int irq; }; +struct lmh_soc_data { +bool enable_algos; +unsigned int clus1_start_idx; +}; +static irqreturn_t lmh_handle_irq (int hw_irq,void *data) {struct lmh_hw_data *lmh_data = data;@@ -100,8 +103,8 @@ static int lmh_probe(struct platform_device *pdev)struct device_node *np = dev->of_node;struct device_node *cpu_node;struct lmh_hw_data *lmh_data; +const struct lmh_soc_data *match_data;int temp_low, temp_high, temp_arm, cpu_id, ret; -unsigned int enable_alg;u32 node_id;if (!qcom_scm_is_available ())@@ -121,6 +124,11 @@ static int lmh_probe(struct platform_device *pdev) cpu_id =of_cpu_node_to_id (cpu_node);of_node_put (cpu_node); +if (cpu_id <0 ) { +dev_err (dev,"Wrong CPU id associated with LMh node\n" ); +return -EINVAL ; + } + ret =of_property_read_u32 (np,"qcom,lmh-temp-high-millicelsius" , &temp_high);if (ret) {dev_err (dev,"missing qcom,lmh-temp-high-millicelsius property\n" );@@ -139,26 +147,16 @@ static int lmh_probe(struct platform_device *pdev)return ret; } -/* -* Only sdm845 has lmh hardware currently enabled from hlos. If this is needed -* for other platforms, revisit this to check if the <cpu-id, node-id> should be part -* of a dt match table. -*/ -if (cpu_id ==0 ) { + match_data =of_device_get_match_data (dev); +if (cpu_id < match_data->clus1_start_idx) node_id =LMH_CLUSTER0_NODE_ID ; - }else if (cpu_id ==4 ) { +else node_id =LMH_CLUSTER1_NODE_ID ; - }else { -dev_err (dev,"Wrong CPU id associated with LMh node\n" ); -return -EINVAL ; - }if (!qcom_scm_lmh_dcvsh_available ())return -EINVAL ; - enable_alg = (uintptr_t )of_device_get_match_data (dev); - -if (enable_alg) { +if (match_data->enable_algos) { ret =qcom_scm_lmh_dcvsh (LMH_SUB_FN_CRNT ,LMH_ALGO_MODE_ENABLE ,1 ,LMH_NODE_DCVS , node_id,0 );if (ret)@@ -231,10 +229,26 @@ static int lmh_probe(struct platform_device *pdev)return 0 ; } +static const struct lmh_soc_data sdm670_lmh_data = { + .enable_algos = true, + .clus1_start_idx =6 , +}; + +static const struct lmh_soc_data sdm845_lmh_data = { + .enable_algos = true, + .clus1_start_idx =4 , +}; + +static const struct lmh_soc_data sm8150_lmh_data = { + .enable_algos = false, + .clus1_start_idx =4 , +}; +static const struct of_device_id lmh_table[] = { - { .compatible ="qcom,sc8180x-lmh" , }, - { .compatible ="qcom,sdm845-lmh" , .data = (void *)LMH_ENABLE_ALGOS }, - { .compatible ="qcom,sm8150-lmh" , }, + { .compatible ="qcom,sc8180x-lmh" , .data = &sm8150_lmh_data }, + { .compatible ="qcom,sdm670-lmh" , .data = &sdm670_lmh_data }, + { .compatible ="qcom,sdm845-lmh" , .data = &sdm845_lmh_data }, + { .compatible ="qcom,sm8150-lmh" , .data = &sm8150_lmh_data }, {} };MODULE_DEVICE_TABLE (of, lmh_table);Signature · 1 line
2.53.0
PATCH v5 2/2 arm64: dts: qcom: sdm670: add thermal zones and thermal devices
In reply to Richard AcayanAdd thermal zones to safeguard from overheating to high temperatures, along with the thermal sensors (TSENS) and CPU frequency limits (LMh). The temperatures are very high, but should still be safeguard for devices that do not specify their own thermal zones.
--- arch/arm64/boot/dts/qcom/sdm670.dtsi | 400 +++++++++++++++++++++++++++ 1 file changed, 400 insertions(+)
arch/arm64/boot/dts/qcom/sdm670.dtsi +400 -0
@@ -20,6 +20,7 @@ #include <dt-bindings/phy/phy-qcom-qusb2.h> #include <dt-bindings/power/qcom-rpmpd.h> #include <dt-bindings/soc/qcom,rpmh-rsc.h> +#include <dt-bindings/thermal/thermal.h> / { interrupt-parent = <&intc>;
@@ -62,6 +63,7 @@ cpu0: cpu@0 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd0>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_0>; l2_0: l2-cache { compatible = "cache";
@@ -89,6 +91,7 @@ cpu1: cpu@100 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd1>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_100>; l2_100: l2-cache { compatible = "cache";
@@ -111,6 +114,7 @@ cpu2: cpu@200 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd2>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_200>; l2_200: l2-cache { compatible = "cache";
@@ -133,6 +137,7 @@ cpu3: cpu@300 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd3>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_300>; l2_300: l2-cache { compatible = "cache";
@@ -155,6 +160,7 @@ cpu4: cpu@400 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd4>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_400>; l2_400: l2-cache { compatible = "cache";
@@ -177,6 +183,7 @@ cpu5: cpu@500 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd5>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_500>; l2_500: l2-cache { compatible = "cache";
@@ -199,6 +206,7 @@ cpu6: cpu@600 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd6>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_600>; l2_600: l2-cache { compatible = "cache";
@@ -221,6 +229,7 @@ cpu7: cpu@700 { <&osm_l3 MASTER_OSM_L3_APPS &osm_l3 SLAVE_OSM_L3>; power-domains = <&cpu_pd7>; power-domain-names = "psci"; + #cooling-cells = <2>; next-level-cache = <&l2_700>; l2_700: l2-cache { compatible = "cache";
@@ -1408,6 +1417,8 @@ gpu: gpu@5000000 { nvmem-cells = <&gpu_speed_bin>; nvmem-cell-names = "speed_bin"; + #cooling-cells = <2>; + status = "disabled"; gpu_zap_shader: zap-shader {
@@ -2100,6 +2111,28 @@ dispcc: clock-controller@af00000 { #power-domain-cells = <1>; }; + tsens0: thermal-sensor@c263000 { + compatible = "qcom,sdm670-tsens", "qcom,tsens-v2"; + reg = <0 0x0c263000 0 0x1000>, + <0 0x0c222000 0 0x1000>; + interrupts-extended = <&pdc 26 IRQ_TYPE_EDGE_RISING>, + <&pdc 28 IRQ_TYPE_EDGE_RISING>; + interrupt-names = "uplow", "critical"; + #thermal-sensor-cells = <1>; + #qcom,sensors = <13>; + }; + + tsens1: thermal-sensor@c265000 { + compatible = "qcom,sdm670-tsens", "qcom,tsens-v2"; + reg = <0 0x0c265000 0 0x1000>, + <0 0x0c223000 0 0x1000>; + interrupts-extended = <&pdc 27 IRQ_TYPE_EDGE_RISING>, + <&pdc 29 IRQ_TYPE_EDGE_RISING>; + interrupt-names = "uplow", "critical"; + #thermal-sensor-cells = <1>; + #qcom,sensors = <8>; + }; + apps_smmu: iommu@15000000 { compatible = "qcom,sdm670-smmu-500", "qcom,smmu-500", "arm,mmu-500"; reg = <0 0x15000000 0 0x80000>;
@@ -2289,5 +2322,372 @@ cpufreq_hw: cpufreq@17d43000 { #freq-domain-cells = <1>; }; + + lmh_cluster1: lmh@17d70800 { + compatible = "qcom,sdm670-lmh", "qcom,sdm845-lmh"; + reg = <0 0x17d70800 0 0x400>; + interrupts = <GIC_SPI 33 IRQ_TYPE_LEVEL_HIGH>; + cpus = <&cpu6>; + qcom,lmh-temp-arm-millicelsius = <65000>; + qcom,lmh-temp-low-millicelsius = <94500>; + qcom,lmh-temp-high-millicelsius = <95000>; + interrupt-controller; + #interrupt-cells = <1>; + }; + + lmh_cluster0: lmh@17d78800 { + compatible = "qcom,sdm670-lmh", "qcom,sdm845-lmh"; + reg = <0 0x17d78800 0 0x400>; + interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>; + cpus = <&cpu0>; + qcom,lmh-temp-arm-millicelsius = <65000>; + qcom,lmh-temp-low-millicelsius = <94500>; + qcom,lmh-temp-high-millicelsius = <95000>; + interrupt-controller; + #interrupt-cells = <1>; + }; + }; + + thermal-zones { + aoss0-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 0>; + + trips { + aoss0_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu0-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 1>; + + trips { + cpu0_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu1-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 2>; + + trips { + cpu1_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu2-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 3>; + + trips { + cpu2_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu3-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 4>; + + trips { + cpu3_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cluster0-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 5>; + + trips { + cluster0_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cluster1-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 6>; + + trips { + cluster1_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu4-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 7>; + + trips { + cpu4_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu5-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 8>; + + trips { + cpu5_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu6-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 9>; + + trips { + cpu6_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + cpu7-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 10>; + + trips { + cpu7_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + gpu0-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 11>; + + cooling-maps { + map0 { + trip = <&gpu0_alert0>; + cooling-device = <&gpu THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; + }; + }; + + trips { + gpu0_alert0: trip-point0 { + temperature = <95000>; + hysteresis = <1000>; + type = "passive"; + }; + + gpu0_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + gpu1-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens0 12>; + + cooling-maps { + map0 { + trip = <&gpu1_alert0>; + cooling-device = <&gpu THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; + }; + }; + + trips { + gpu1_alert0: trip-point0 { + temperature = <95000>; + hysteresis = <1000>; + type = "passive"; + }; + + gpu1_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + aoss1-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 0>; + + trips { + aoss1_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + q6-modem-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 1>; + + trips { + q6_modem_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + mem-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 2>; + + trips { + mem_crit: trip-point1 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + wlan-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 3>; + + trips { + wlan_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + q6-hvx-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 4>; + + trips { + q6_hvx_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + camera-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 5>; + + trips { + camera_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + video-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 6>; + + trips { + video_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; + + modem-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>; + + thermal-sensors = <&tsens1 7>; + + trips { + modem_crit: trip-point0 { + temperature = <125000>; + hysteresis = <1000>; + type = "critical"; + }; + }; + }; }; };
Signature · 1 line
2.53.0
Re: [PATCH v5 2/2] arm64: dts: qcom: sdm670: add thermal zones and thermal devices
Quoted 10 lines · Richard Acayan
Add thermal zones to safeguard from overheating to high temperatures, along with the thermal sensors (TSENS) and CPU frequency limits (LMh). The temperatures are very high, but should still be safeguard for devices that do not specify their own thermal zones.
Signed-off-by Richard Acayan <[email protected]>--- arch/arm64/boot/dts/qcom/sdm670.dtsi | 400 +++++++++++++++++++++++++++ 1 file changed, 400 insertions(+)
Signature · 2 lines
With best wishes Dmitry
Re: [PATCH v5 2/2] arm64: dts: qcom: sdm670: add thermal zones and thermal devices
In reply to Richard AcayanQuoted 7 lines · Richard Acayan
Add thermal zones to safeguard from overheating to high temperatures, along with the thermal sensors (TSENS) and CPU frequency limits (LMh). The temperatures are very high, but should still be safeguard for devices that do not specify their own thermal zones.
Signed-off-by Richard Acayan <[email protected]>---
[...]
arch/arm64/boot/dts/qcom/sdm670.dtsi cpufreq_hw: cpufreq@17d43000 { · line 2354
Quoted 4 lines
arch/arm64/boot/dts/qcom/sdm670.dtsi +4
-0+ thermal-zones { + aoss0-thermal { + polling-delay-passive = <250>; + polling-delay = <1000>;
You can drop all polling on TSENS thermal zones - we get interrupts for when thresholds are crossed
Konrad