Thread (4 messages) 4 messages, 3 authors, 2012-03-26

Re: [PATCH] rtc/spear: Add Device Tree probing capability

From: Arnd Bergmann <arnd@arndb.de>
Date: 2012-03-26 12:36:27
Also in: lkml

On Monday 26 March 2012, Stefan Roese wrote:
quoted
diff --git a/Documentation/devicetree/bindings/rtc/spear-rtc.txt
b/Documentation/devicetree/bindings/rtc/spear-rtc.txt new file mode 100644
index 0000000..928410f
--- /dev/null
+++ b/Documentation/devicetree/bindings/rtc/spear-rtc.txt
@@ -0,0 +1,18 @@
+* SPEAr RTC
+
+Required properties:
+- compatible : "st,spear-rtc"
+- reg : Address range of the rtc registers
+- interrupt-parent: Should be the phandle for the interrupt controller
+  that services interrupts for this device
+- interrupt: Should contain the rtc interrupt number
+
+Example:
+
+     rtc@fc000000 {
+             compatible = "st,spear-rtc";
With Rob's comments in mind, wouldn't it be better to use a more specific 
compatible property? Should we stick with "st,spear600-rtc"? Or use "st-
spear300-rtc" as "oldest" SoC variant?
I wouldn't mind if you list all three, or at least spear600 as the actual
chip and spear300 as the one that introduced the device. Of course, if the
device itself is licensed from some other vendor or was used in a prior product,
I would list that one.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help