diff mbox series

[07/15] dt: thermal: tsens: Document interrupt support in tsens driver

Message ID 72bce036fa8cba3db6e5ba82249837ee46e9c077.1564091601.git.amit.kucheria@linaro.org
State New
Headers show
Series None | expand

Commit Message

Amit Kucheria July 25, 2019, 10:18 p.m. UTC
Define two new required properties to define interrupts and
interrupt-names for tsens.

Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>

---
 Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 5 +++++
 1 file changed, 5 insertions(+)

-- 
2.17.1

Comments

Stephen Boyd Aug. 17, 2019, 4:10 a.m. UTC | #1
Quoting Amit Kucheria (2019-08-16 15:02:08)
> 

> Depending on the version of the tsens IP, there can be 1 (upper/lower

> threshold), 2 (upper/lower + critical threshold) or 3 (upper/lower +

> critical + zero degree) interrupts. This patch series only introduces

> support for a single interrupt (upper/lower).

> 

> I used the names tsens0, tsens1 to encapsulate the controller instance

> since some SoCs have 1 controller, others have two. So we'll end up

> with something like the following in DT:

> 

> tsens0: thermal-sensor@c263000 {

>                         compatible = "qcom,sdm845-tsens", "qcom,tsens-v2";

>                         reg = <0 0x0c263000 0 0x1ff>, /* TM */

>                               <0 0x0c222000 0 0x1ff>; /* SROT */

>                         #qcom,sensors = <13>;

>                         interrupts = <GIC_SPI 506 IRQ_TYPE_LEVEL_HIGH>,

>                                      <GIC_SPI 508 IRQ_TYPE_LEVEL_HIGH>;

>                         interrupt-names = "tsens0", "tsens0-critical";

>                         #thermal-sensor-cells = <1>;

> };

> 

> tsens1: thermal-sensor@c265000 {

>                         compatible = "qcom,sdm845-tsens", "qcom,tsens-v2";

>                         reg = <0 0x0c265000 0 0x1ff>, /* TM */

>                               <0 0x0c223000 0 0x1ff>; /* SROT */

>                         #qcom,sensors = <8>;

>                         interrupts = <GIC_SPI 507 IRQ_TYPE_LEVEL_HIGH>,

>                                      <GIC_SPI 509 IRQ_TYPE_LEVEL_HIGH>;

>                         interrupt-names = "tsens1", "tsens1-critical";

>                         #thermal-sensor-cells = <1>;

> }

> 

> Does that work?

> 


Can you convert this binding to YAML? Then it looks like we can enforce
the number of interrupts based on the compatible string.
diff mbox series

Patch

diff --git a/Documentation/devicetree/bindings/thermal/qcom-tsens.txt b/Documentation/devicetree/bindings/thermal/qcom-tsens.txt
index 673cc1831ee9..3d3dd5dc6d36 100644
--- a/Documentation/devicetree/bindings/thermal/qcom-tsens.txt
+++ b/Documentation/devicetree/bindings/thermal/qcom-tsens.txt
@@ -22,6 +22,8 @@  Required properties:
 
 - #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description.
 - #qcom,sensors: Number of sensors in tsens block
+- interrupts: Interrupts generated from Always-On subsystem (AOSS)
+- interrupt-names: The name of the interrupt e.g. "tsens0", "tsens1"
 - Refer to Documentation/devicetree/bindings/nvmem/nvmem.txt to know how to specify
 nvmem cells
 
@@ -40,6 +42,9 @@  tsens0: thermal-sensor@c263000 {
 		reg = <0xc263000 0x1ff>, /* TM */
 			<0xc222000 0x1ff>; /* SROT */
 		#qcom,sensors = <13>;
+		interrupts = <GIC_SPI 506 IRQ_TYPE_LEVEL_HIGH>;
+		interrupt-names = "tsens0";
+
 		#thermal-sensor-cells = <1>;
 	};