Documentation/watchdog/watchdog-parameters.rst
Source file repositories/reference/linux-study-clean/Documentation/watchdog/watchdog-parameters.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/watchdog/watchdog-parameters.rst- Extension
.rst- Size
- 18007 bytes
- Lines
- 714
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
==========================
WatchDog Module Parameters
==========================
This file provides information on the module parameters of many of
the Linux watchdog drivers. Watchdog driver parameter specs should
be listed here unless the driver has its own driver-specific information
file.
See Documentation/admin-guide/kernel-parameters.rst for information on
providing kernel parameters for builtin drivers versus loadable
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. Default is set
by the kconfig option CONFIG_WATCHDOG_OPEN_TIMEOUT.
stop_on_reboot:
Stops watchdogs on reboot (0 = keep watching, 1 = stop).
-------------------------------------------------
acquirewdt:
wdt_stop:
Acquire WDT 'stop' io port (default 0x43)
wdt_start:
Acquire WDT 'start' io port (default 0x443)
nowayout:
Watchdog cannot be stopped once started
(default=kernel config parameter)
-------------------------------------------------
advantechwdt:
wdt_stop:
Advantech WDT 'stop' io port (default 0x443)
wdt_start:
Advantech WDT 'start' io port (default 0x443)
timeout:
Watchdog timeout in seconds. 1<= timeout <=63, default=60.
nowayout:
Watchdog cannot be stopped once started
(default=kernel config parameter)
-------------------------------------------------
alim1535_wdt:
timeout:
Watchdog timeout in seconds. (0 < timeout < 18000, default=60
nowayout:
Watchdog cannot be stopped once started
(default=kernel config parameter)
-------------------------------------------------
alim7101_wdt:
timeout:
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.