[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385085414-9034-7-git-send-email-joelf@ti.com>
Date: Thu, 21 Nov 2013 19:56:52 -0600
From: Joel Fernandes <joelf@...com>
To: <linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
CC: <benoit.cousson@...aro.org>, <santosh.shilimkar@...com>,
<jgchunter@...il.com>, <rnayak@...com>, <balbi@...com>,
Joel Fernandes <joelf@...com>
Subject: [PATCH 6/8] devicetree: doc: Document ti,timer-parent property
Timer's parent mux clocks require a parent clock alias, provide the same from
device tree.
Ultimately this will be provided from DT as clock node phandles but clk-mux
driver DT bindings series is still under going review. So to keep things
working during the timer migration, we add this property. Originally this was
hardcoded in timer.c, now we do the same in DT and would be removing the
hardcoded names from timer.c
Signed-off-by: Joel Fernandes <joelf@...com>
---
Documentation/devicetree/bindings/arm/omap/timer.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/omap/timer.txt b/Documentation/devicetree/bindings/arm/omap/timer.txt
index 6cf7a75..644bc61 100644
--- a/Documentation/devicetree/bindings/arm/omap/timer.txt
+++ b/Documentation/devicetree/bindings/arm/omap/timer.txt
@@ -24,6 +24,11 @@ Required properties:
where <X> is the instance number of the timer from the
HW spec.
+Required properties for system timers (clockevents/clocksource):
+- ti,timer-parent: System timer's parent mux clock needs to be setup.
+ This is currently hardcoded in code, for DT boot we
+ move this to DT.
+
Optional properties:
- ti,timer-alwon: Indicates the timer is in an alway-on power domain.
- ti,timer-dsp: Indicates the timer can interrupt the on-chip DSP in
--
1.8.1.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists