Add devicetree binding document which describes the qpnp-rtc.
Signed-off-by: Stanimir Varbanov <svarbanov@xxxxxxxxxx>
---
.../devicetree/bindings/rtc/qcom,rtc-qpnp.txt | 24 ++++++++++++++++++++
1 files changed, 24 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/rtc/qcom,rtc-qpnp.txt
diff --git a/Documentation/devicetree/bindings/rtc/qcom,rtc-qpnp.txt b/Documentation/devicetree/bindings/rtc/qcom,rtc-qpnp.txt
new file mode 100644
index 0000000..a64e194
--- /dev/null
+++ b/Documentation/devicetree/bindings/rtc/qcom,rtc-qpnp.txt
@@ -0,0 +1,24 @@
+Qualcomm RTC QPNP
+
+The RTC device supports 32bit RTC module housed inside QPNP PMIC's.
+The driver utilizes SPMI interface to communicate with the RTC module.
+RTC device is divided into two sub-peripherals one which controls
+basic RTC and other for controlling alarm.
+
+Required properties :
+ - compatible: Should be "qcom,qpnp-rtc".
+ - reg: Specify the peripheral id for device. Currently there
+ are two sub-peripherals - rtc base and alarm base.
+ - reg-names: Specify the reg property as strings. Should be "rtc"
+ and "alarm", defining the rtc and alarm bases.
+ - interrupts: Specifies alarm interrupt, only for alarm sub-peripheral.
+ For more info about interrupt cells see
+ Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt
+
+Example:
+ rtc@6000 {
+ compatible = "qcom,qpnp-rtc";
+ reg = <0x6000 0x6100>;
+ reg-names = "rtc", "alarm";
+ interrupts = <0x0 0x61 0x1 IRQ_TYPE_EDGE_RISING>;
+ };
--
1.7.0.4
--
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
