docs: watchdog-parameters: add missing watchdog_core parameters

Add missing watchdog_core parameters (handle_boot_enabled and
stop_on_reboot).
Add default values for handle_boot_enabled and open_timeout.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20260228010402.2389343-6-rdunlap@infradead.org>

diff --git a/Documentation/watchdog/watchdog-parameters.rst b/Documentation/watchdog/watchdog-parameters.rst
index 773241ed99867cb479e2ce6bd1cba52f0e909d39..2359aa32e25d5e7b4b3b058b36db4f02188e0f98 100644 (file)
--- a/Documentation/watchdog/watchdog-parameters.rst
+++ b/Documentation/watchdog/watchdog-parameters.rst
@@ -14,13 +14,22 @@ modules.
 -------------------------------------------------
 
 watchdog core:
+    handle_boot_enabled:
+       Watchdog core auto-updates boot-enabled watchdogs before userspace
+       takes over. Default is set by the kconfig option
+       CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED.
+
     open_timeout:
        Maximum time, in seconds, for which the watchdog framework will take
        care of pinging a running hardware watchdog until userspace opens the
        corresponding /dev/watchdogN device. A value of 0 means an infinite
        timeout. Setting this to a non-zero value can be useful to ensure that
        either userspace comes up properly, or the board gets reset and allows
-       fallback logic in the bootloader to try something else.
+       fallback logic in the bootloader to try something else. Default is set
+       by the kconfig option CONFIG_WATCHDOG_OPEN_TIMEOUT.
+
+    stop_on_reboot:
+       Stops watchdogs on reboot (0 = keep watching, 1 = stop).
 
 -------------------------------------------------