[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190607194343.18359-1-khilman@kernel.org>
Date: Fri, 7 Jun 2019 12:43:42 -0700
From: Kevin Hilman <khilman@...nel.org>
To: linux-rtc@...r.kernel.org,
Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, Kevin Hilman <khilman@...libre.com>
Subject: [PATCH 1/2] dt-bindings: rtc: new binding for Amlogic VRTC
From: Kevin Hilman <khilman@...libre.com>
Add binding fo the new VRTC driver for Amlogic SoCs. The 64-bit
family of SoCs only has an RTC managed by firmware, and this VRTC
driver provides the simple, one-register firmware interface.
Signed-off-by: Kevin Hilman <khilman@...libre.com>
---
.../devicetree/bindings/rtc/rtc-meson-vrtc.txt | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/rtc-meson-vrtc.txt
diff --git a/Documentation/devicetree/bindings/rtc/rtc-meson-vrtc.txt b/Documentation/devicetree/bindings/rtc/rtc-meson-vrtc.txt
new file mode 100644
index 000000000000..f02886179788
--- /dev/null
+++ b/Documentation/devicetree/bindings/rtc/rtc-meson-vrtc.txt
@@ -0,0 +1,16 @@
+* Amlogic Virtual RTC (VRTC)
+
+This is a Linux interface to an RTC managed by firmware, hence it's
+virtual from a Linux perspective. The interface is 1 register where
+an alarm time is to be written.
+
+Required properties:
+- compatible: should be "amlogic,meson-vrtc"
+- reg: physical address for the alarm register
+
+Example:
+
+ vrtc: rtc@0a8 {
+ compatible = "amlogic,meson-vrtc";
+ reg = <0x0 0x000a8 0x0 0x4>;
+ };
--
2.21.0
Powered by blists - more mailing lists