Documentation/watchdog/pcwd-watchdog.rst
Source file repositories/reference/linux-study-clean/Documentation/watchdog/pcwd-watchdog.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/watchdog/pcwd-watchdog.rst- Extension
.rst- Size
- 2618 bytes
- Lines
- 79
- 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
===================================
Berkshire Products PC Watchdog Card
===================================
Last reviewed: 10/05/2007
Support for ISA Cards Revision A and C
=======================================
Documentation and Driver by Ken Hollis <kenji@bitgate.com>
The PC Watchdog is a card that offers the same type of functionality that
the WDT card does, only it doesn't require an IRQ to run. Furthermore,
the Revision C card allows you to monitor any IO Port to automatically
trigger the card into being reset. This way you can make the card
monitor hard drive status, or anything else you need.
The Watchdog Driver has one basic role: to talk to the card and send
signals to it so it doesn't reset your computer ... at least during
normal operation.
The Watchdog Driver will automatically find your watchdog card, and will
attach a running driver for use with that card. After the watchdog
drivers have initialized, you can then talk to the card using a PC
Watchdog program.
I suggest putting a "watchdog -d" before the beginning of an fsck, and
a "watchdog -e -t 1" immediately after the end of an fsck. (Remember
to run the program with an "&" to run it in the background!)
If you want to write a program to be compatible with the PC Watchdog
driver, simply use or modify the watchdog test program:
tools/testing/selftests/watchdog/watchdog-test.c
Other IOCTL functions include:
WDIOC_GETSUPPORT
This returns the support of the card itself. This
returns in structure watchdog_info:
identity = "PCWD"
options = list of supported options::
WDIOF_OVERHEAT
WDIOF_CARDRESET
WDIOF_KEEPALIVEPING
WDIOF_SETTIMEOUT
WDIOF_MAGICCLOSE
firmware_version = xxxx
(Firmware version of the card)
WDIOC_GETSTATUS
This returns the status of the card, with the bits of
WDIOF_* bitwise-ored into the value. (The comments
are in include/uapi/linux/watchdog.h)
WDIOC_GETBOOTSTATUS
This returns the status of the card that was reported
at bootup.
WDIOC_GETTEMP
This returns the temperature of the card. (You can also
read /dev/temperature, which gives a temperature update
every second.)
WDIOC_SETOPTIONS
This lets you set the options of the card. You can either
enable or disable the card this way.
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.