This optional property can be used to specify which timers are to be used
for hardware watchdog timeouts (via a tegra wdt driver).
Signed-off-by: Andrew Chew <ac...@nvidia.com>
---
Documentation/devicetree/bindings/timer/nvidia,tegra30-timer.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/timer/nvidia,tegra30-timer.txt
b/Documentation/devicetree/bindings/timer/nvidia,tegra30-timer.txt
index b5082a1..e87fa70 100644
--- a/Documentation/devicetree/bindings/timer/nvidia,tegra30-timer.txt
+++ b/Documentation/devicetree/bindings/timer/nvidia,tegra30-timer.txt
@@ -13,6 +13,13 @@ Required properties:
- clocks : Must contain one entry, for the module clock.
See ../clocks/clock-bindings.txt for details.
+Optional properties:
+
+- nvidia,wdt-timer-id: A list of timer IDs to be used for watchdogs.
+ Watchdog 0 will be assigned to the first timer listed, watchdog 1 will
+ be assigned to the second timer listed, etc. up to the number of watchdogs
+ available.
+
timer {
compatible = "nvidia,tegra30-timer", "nvidia,tegra20-timer";
reg = <0x60005000 0x400>;
@@ -23,4 +30,5 @@ timer {
0 121 0x04
0 122 0x04>;
clocks = <&tegra_car 214>;
+ nvidia,wdt-timer-id = <7 8>;
};
--
1.8.1.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
