summaryrefslogtreecommitdiff
path: root/doc/device-tree-bindings
diff options
context:
space:
mode:
authorRasmus Villemoes <rasmus.villemoes@prevas.dk>2022-09-27 12:54:03 +0300
committerStefan Roese <sr@denx.de>2022-10-24 12:09:19 +0300
commit27836705839c4751ac28239ee6fa1f3984e46d4d (patch)
treef2d870bb3ac574bf660add626e36fe8b4c1c6b5e /doc/device-tree-bindings
parent0ab55cb6f713abeb0b0f0cc1af2d2d16353b5ee0 (diff)
downloadu-boot-27836705839c4751ac28239ee6fa1f3984e46d4d.tar.xz
watchdog: introduce a u-boot,autostart property
This is a companion to u-boot,noautostart. If one has a single watchdog device that one does want to have auto-started, but several others that one doesn't, the only way currently is to set the CONFIG_WATCHDOG_AUTOSTART and then use the opt-out for the majority. The main motivation for this is to add an autostarted watchdog device to the sandbox (to test a fix) without having to set AUTOSTART in sandbox_defconfig and add the noautostart property to the existing devices. But it's also nice for symmetry, and the logic in init_watchdog_dev() becomes simpler to read because we avoid all the negations. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Diffstat (limited to 'doc/device-tree-bindings')
-rw-r--r--doc/device-tree-bindings/watchdog/common.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/device-tree-bindings/watchdog/common.txt b/doc/device-tree-bindings/watchdog/common.txt
index 9db6dd6146..d041fea234 100644
--- a/doc/device-tree-bindings/watchdog/common.txt
+++ b/doc/device-tree-bindings/watchdog/common.txt
@@ -6,7 +6,8 @@ Optional properties:
be used instead.
- hw_margin_ms : Period used to reset the watchdog in ms
If this period is not defined, the default value is 1000.
-- u-boot,noautostart : Specify that this watchdog should not autostart
- When the config option WATCHDOG_AUTOSTART is set, all enabled
- watchdogs are started. This property allows specifying that this
- watchdog should NOT be started.
+- u-boot,noautostart :
+- u-boot,autostart : These (mutually exclusive) boolean properties can be used to control
+ whether the watchdog is automatically started when probed. If neither
+ are present, the behaviour is determined by the config option
+ WATCHDOG_AUTOSTART.