Re: [PATCH 2/5] Documentation: dt: Add binding info for jz4740-rtc driver
From: Rob Herring <hidden>
Date: 2016-03-17 11:52:33
Also in:
linux-mips, linux-rtc, lkml
On Sat, Mar 05, 2016 at 11:38:48PM +0100, Paul Cercueil wrote:
quoted hunk ↗ jump to hunk
Signed-off-by: Paul Cercueil <redacted> --- .../devicetree/bindings/rtc/ingenic,jz4740-rtc.txt | 38 ++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txtdiff --git a/Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txt b/Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txt new file mode 100644 index 0000000..71e4ad0 --- /dev/null +++ b/Documentation/devicetree/bindings/rtc/ingenic,jz4740-rtc.txt@@ -0,0 +1,38 @@ +JZ4740 and similar SoCs real-time clock driver + +Required properties: + +- compatible: One of: + - "ingenic,jz4740-rtc" - for use with the JZ4740 SoC + - "ingenic,jz4780-rtc" - for use with the JZ4780 SoC +- reg: Address range of rtc register set +- interrupts: IRQ number for the alarm interrupt +- interrupt-parent: phandle of the interrupt controller +- clocks: phandle to the "rtc" clock +- clock-names: must be "rtc" + +Optional properties: +- system-power-controller: To use this component as the + system power controller
+- reset-pin-assert-time: Reset pin low-level assertion time + after wakeup (default 60ms; range 0-125ms if RTC clock at + 32 kHz) +- min-wakeup-pin-assert-time: Minimum wakeup pin assertion time + (default 100ms; range 0-2s if RTC clock at 32 kHz)
Please append units on these (-msec).
+
+Example:
+
+rtc@10003000 {
+ compatible = "ingenic,jz4740-rtc";
+ reg = <0x10003000 0x3F>;
+
+ interrupt-parent = <&intc>;
+ interrupts = <32>;
+
+ clocks = <&rtc_clock>;
+ clock-names = "rtc";
+
+ system-power-controller;
+ reset-pin-assert-time = <60>;
+ min-wakeup-pin-assert-time = <100>;
+};
--
2.7.0-- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html