Re: [PATCH v4 12/21] DT: omap4/5: add binding for the wake-up generator

2015-01-21 Thread Tony Lindgren 
* Marc Zyngier marc.zyng...@arm.com [150119 01:48]:
 Signed-off-by: Marc Zyngier marc.zyng...@arm.com

Acked-by: Tony Lindgren t...@atomide.com

 ---
  .../interrupt-controller/ti,omap4-wugen-mpu| 33 
 ++
  1 file changed, 33 insertions(+)
  create mode 100644 
 Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
 
 diff --git 
 a/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu 
 b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
 new file mode 100644
 index 000..43effa0
 --- /dev/null
 +++ 
 b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
 @@ -0,0 +1,33 @@
 +TI OMAP4 Wake-up Generator
 +
 +All TI OMAP4/5 (and their derivatives) an interrupt controller that
 +routes interrupts to the GIC, and also serves as a wakeup source. It
 +is also referred to as WUGEN-MPU, hence the name of the binding.
 +
 +Reguired properties:
 +
 +- compatible : should contain at least ti,omap4-wugen-mpu or
 +  ti,omap5-wugen-mpu
 +- reg : Specifies base physical address and size of the registers.
 +- interrupt-controller : Identifies the node as an interrupt controller.
 +- #interrupt-cells : Specifies the number of cells needed to encode an
 +  interrupt source. The value must be 3.
 +- interrupt-parent : a phandle to the GIC these interrupts are routed
 +  to.
 +
 +Notes:
 +
 +- Because this HW ultimately routes interrupts to the GIC, the
 +  interrupt specifier must be that of the GIC.
 +- Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
 +  are explicitly forbiden.
 +
 +Example:
 +
 +   wakeupgen: interrupt-controller@48281000 {
 +   compatible = ti,omap5-wugen-mpu, ti,omap4-wugen-mpu;
 +   interrupt-controller;
 +   #interrupt-cells = 3;
 +   reg = 0x48281000 0x1000;
 +   interrupt-parent = gic;
 +   };
 -- 
 2.1.4
 
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH v4 12/21] DT: omap4/5: add binding for the wake-up generator

2015-01-19 Thread Marc Zyngier 
Signed-off-by: Marc Zyngier marc.zyng...@arm.com
---
 .../interrupt-controller/ti,omap4-wugen-mpu| 33 ++
 1 file changed, 33 insertions(+)
 create mode 100644 
Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu

diff --git 
a/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu 
b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
new file mode 100644
index 000..43effa0
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
@@ -0,0 +1,33 @@
+TI OMAP4 Wake-up Generator
+
+All TI OMAP4/5 (and their derivatives) an interrupt controller that
+routes interrupts to the GIC, and also serves as a wakeup source. It
+is also referred to as WUGEN-MPU, hence the name of the binding.
+
+Reguired properties:
+
+- compatible : should contain at least ti,omap4-wugen-mpu or
+  ti,omap5-wugen-mpu
+- reg : Specifies base physical address and size of the registers.
+- interrupt-controller : Identifies the node as an interrupt controller.
+- #interrupt-cells : Specifies the number of cells needed to encode an
+  interrupt source. The value must be 3.
+- interrupt-parent : a phandle to the GIC these interrupts are routed
+  to.
+
+Notes:
+
+- Because this HW ultimately routes interrupts to the GIC, the
+  interrupt specifier must be that of the GIC.
+- Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
+  are explicitly forbiden.
+
+Example:
+
+   wakeupgen: interrupt-controller@48281000 {
+   compatible = ti,omap5-wugen-mpu, ti,omap4-wugen-mpu;
+   interrupt-controller;
+   #interrupt-cells = 3;
+   reg = 0x48281000 0x1000;
+   interrupt-parent = gic;
+   };
-- 
2.1.4

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html