[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190913153714.30980-1-aford173@gmail.com>
Date: Fri, 13 Sep 2019 10:37:13 -0500
From: Adam Ford <aford173@...il.com>
To: linux-omap@...r.kernel.org
Cc: adam.ford@...icpd.com, nm@...com, hns@...delico.com,
Adam Ford <aford173@...il.com>,
BenoƮt Cousson <bcousson@...libre.com>,
Tony Lindgren <tony@...mide.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC v2 1/2] ARM: dts: omap3: Add cpu trips and cooling map for omap3 family
The OMAP3530, AM3517 and DM3730 all show thresholds of 90C and 105C
depending on commercial or industrial temperature ratings. This
patch expands the thermal information to the limits of 90 and 105
for alert and critical.
For boards who never use industrial temperatures, these can be
changed on their respective device trees with something like:
&cpu_alert0 {
temperature = <85000>; /* millicelsius */
};
&cpu_crit {
temperature = <90000>; /* millicelsius */
};
Signed-off-by: Adam Ford <aford173@...il.com>
---
V2: Change the CPU reference to &cpu instead of &cpu0
diff --git a/arch/arm/boot/dts/omap3-cpu-thermal.dtsi b/arch/arm/boot/dts/omap3-cpu-thermal.dtsi
index 235ecfd61e2d..dfbd0cb0b00b 100644
--- a/arch/arm/boot/dts/omap3-cpu-thermal.dtsi
+++ b/arch/arm/boot/dts/omap3-cpu-thermal.dtsi
@@ -17,4 +17,25 @@ cpu_thermal: cpu_thermal {
/* sensor ID */
thermal-sensors = <&bandgap 0>;
+
+ cpu_trips: trips {
+ cpu_alert0: cpu_alert {
+ temperature = <90000>; /* millicelsius */
+ hysteresis = <2000>; /* millicelsius */
+ type = "passive";
+ };
+ cpu_crit: cpu_crit {
+ temperature = <105000>; /* millicelsius */
+ hysteresis = <2000>; /* millicelsius */
+ type = "critical";
+ };
+ };
+
+ cpu_cooling_maps: cooling-maps {
+ map0 {
+ trip = <&cpu_alert0>;
+ cooling-device =
+ <&cpu THERMAL_NO_LIMIT THERMAL_NO_LIMIT>;
+ };
+ };
};
--
2.17.1
Powered by blists - more mailing lists