OMAP34xx and OMAP36xx processors contain a register in the syscon area,
which can be used to determine the SoCs temperature. This provides a
DT binding specification for the temperature monitor.
Signed-off-by: Sebastian Reichel <sre@xxxxxxxxxx>
---
.../bindings/hwmon/omap3-temperature.txt | 25 ++++++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/omap3-temperature.txt
diff --git a/Documentation/devicetree/bindings/hwmon/omap3-temperature.txt b/Documentation/devicetree/bindings/hwmon/omap3-temperature.txt
new file mode 100644
index 0000000..99631ad
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/omap3-temperature.txt
@@ -0,0 +1,25 @@
+* OMAP3 temperature sensor
+
+The OMAP34xx and OMAP36xx processors contain a register in the syscon area,
+which can be used to determine the SoCs temperature.
+
+Requires node properties:
+- compatible : should contain one of
+ - "ti,omap34xx-temperature-sensor" for OMAP34xx
+ - "ti,omap36xx-temperature-sensor" for OMAP36xx
+- syscon : Should be a phandle to system configuration node which
+ encompases the temperature register
+- clocks : Should contain 32KHz fclk clock specifier
+- clock-names : Should contain clock names
+ - "fck" for the 32KHz fclk clock specifier
+
+Example for omap34xx:
+
+/ {
+ temperature-sensor {
+ compatible = "ti,omap34xx-temperature-sensor";
+ syscon = <&omap3_scm_general>;
+ clocks = <&ts_fck>;
+ clock-names = "fck";
+ };
+};
--
2.1.3
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
