i.MX ProcessorsのトピックDifference Between DTS Thermal Configuration and Runtime Thermal Trip Points IMX93

Difference Between DTS Thermal Configuration and Runtime Thermal Trip Points IMX93

Jamal — Mon, 08 Jun 2026 06:10:16 GMT

Hi,

We observed the following thermal configuration in the file:

arch/arm64/boot/dts/freescale/imx93.dtsi

thermal-zones {
cpu-thermal {
polling-delay-passive = <250>;
polling-delay = <2000>;

thermal-sensors = <&tmu 0>;

trips {
cpu_alert: cpu-alert {
temperature = <80000>;
hysteresis = <2000>;
type = "passive";
};

cpu_crit: cpu-crit {
temperature = <90000>;
hysteresis = <2000>;
type = "critical";
};
};
};
};

However, on the running system, the sysfs entries report different values:

cat /sys/class/thermal/thermal_zone0/trip_point_0_temp
95000

cat /sys/class/thermal/thermal_zone0/trip_point_1_temp
105000

This indicates that the passive trip point is set to 95°C and the critical trip point is set to 105°C at runtime, which differs from the values defined in the DTS file (80°C and 90°C).

Could you please clarify why these values are different? Is there any other location in the kernel, driver, or platform code where these thermal trip points are being modified or overridden at runtime?

Kindly let us know where we can further investigate this behavior.

Regards,
Jamal Deen

Re: Difference Between DTS Thermal Configuration and Runtime Thermal Trip Points IMX93

yipingwang — Mon, 08 Jun 2026 07:15:09 GMT

On imx93evk board, I checked the following dts configuration.

root@imx93evk:/tmp# hexdump -C /sys/firmware/devicetree/base/thermal-zones/cpu-thermal/trips/cpu-alert/temperature

00000000 00 01 73 18 |..s.|

00000004

root@imx93evk:/tmp# hexdump -C /sys/firmware/devicetree/base/thermal-zones/cpu-thermal/trips/cpu-crit/temperature

00000000 00 01 9a 28 |...(|

00000004

HEX 19a28 = 105000(DEC)

HEX 17318 = 95000(DEC)

It means the DTS has already been modified by u-boot before loading by Linux Kernel.

Please refer to function fixup_thermal_trips in arch/arm/mach-imx/fdt.c in u-boot source code.

get_cpu_temp_grade(&minc, &maxc);

fdt_for_each_subnode(trip, blob, node) {
const char *type;
int temp, ret;

type = fdt_getprop(blob, trip, "type", NULL);
if (!type)
continue;

temp = 0;
if (!strcmp(type, "critical"))
temp = 1000 * maxc;
else if (!strcmp(type, "passive"))
temp = 1000 * (maxc - 10);
if (temp) {
ret = fdt_setprop_u32(blob, trip, "temperature", temp);
if (ret)
return ret;
}