[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210421162621.24910-2-francesco.zanella@vimar.com>
Date: Wed, 21 Apr 2021 18:26:20 +0200
From: Francesco Zanella <francesco.zanella@...ar.com>
To: linux-watchdog@...r.kernel.org, wim@...ux-watchdog.org,
linux@...ck-us.net
Cc: devicetree@...r.kernel.org, robh+dt@...nel.org,
linux-kernel@...r.kernel.org,
Francesco Zanella <francesco.zanella@...ar.com>
Subject: [PATCH 1/2] dt-bindings: watchdog: gpio-wdt: add "start-at-boot"
Documentation for new device tree property "start-at-boot".
Signed-off-by: Francesco Zanella <francesco.zanella@...ar.com>
---
Documentation/devicetree/bindings/watchdog/gpio-wdt.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt b/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
index 198794963786..cdaf7f0602e8 100644
--- a/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
+++ b/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
@@ -17,6 +17,13 @@ Optional Properties:
- always-running: If the watchdog timer cannot be disabled, add this flag to
have the driver keep toggling the signal without a client. It will only cease
to toggle the signal when the device is open and the timeout elapsed.
+- start-at-boot: Start pinging hw watchdog at probe, in order to take advantage
+ of kernel configs:
+ - WATCHDOG_HANDLE_BOOT_ENABLED: Avoid possible reboot if hw watchdog was been
+ enabled before the kernel (by uboot for example) and userspace doesn't take
+ control of /dev/watchdog in time;
+ - WATCHDOG_OPEN_TIMEOUT: Reboot if userspace doesn't take control of
+ /dev/watchdog within the timeout.
Example:
watchdog: watchdog {
--
2.17.1
Powered by blists - more mailing lists