Re: [PATCH 5/5] docs: watchdog-parameters: add missing watchdog_core parameters

[Guenter Roeck]

On Fri, Feb 27, 2026 at 05:04:02PM -0800, Randy Dunlap wrote:
> 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@xxxxxxxxxxxxx>

Reviewed-by: Guenter Roeck <linux@xxxxxxxxxxxx>

> ---
> Cc: Jonathan Corbet <corbet@xxxxxxx>
> Cc: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
> Cc: Wim Van Sebroeck <wim@xxxxxxxxxxxxxxxxxx>
> Cc: Guenter Roeck <linux@xxxxxxxxxxxx>
> Cc: linux-watchdog@xxxxxxxxxxxxxxx
> Cc: linux-doc@xxxxxxxxxxxxxxx
> 
>  Documentation/watchdog/watchdog-parameters.rst |   11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> --- linux-next-20260227.orig/Documentation/watchdog/watchdog-parameters.rst
> +++ linux-next-20260227/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).
>  
>  -------------------------------------------------
>