From: Randy Dunlap Date: Sat, 28 Feb 2026 01:04:02 +0000 (-0800) Subject: docs: watchdog-parameters: add missing watchdog_core parameters X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6f8daf6670d3c33b45a5f0b1f78566385424519b;p=thirdparty%2Fkernel%2Flinux.git 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 Reviewed-by: Guenter Roeck Signed-off-by: Jonathan Corbet Message-ID: <20260228010402.2389343-6-rdunlap@infradead.org> --- diff --git a/Documentation/watchdog/watchdog-parameters.rst b/Documentation/watchdog/watchdog-parameters.rst index 773241ed99867..2359aa32e25d5 100644 --- 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). -------------------------------------------------