arch/sparc/include/uapi/asm/watchdog.h
Source file repositories/reference/linux-study-clean/arch/sparc/include/uapi/asm/watchdog.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/include/uapi/asm/watchdog.h- Extension
.h- Size
- 1029 bytes
- Lines
- 33
- Domain
- Architecture Layer
- Bucket
- arch/sparc
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
linux/watchdog.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _SPARC64_WATCHDOG_H
#define _SPARC64_WATCHDOG_H
#include <linux/watchdog.h>
/* Solaris compatibility ioctls--
* Ref. <linux/watchdog.h> for standard linux watchdog ioctls
*/
#define WIOCSTART _IO (WATCHDOG_IOCTL_BASE, 10) /* Start Timer */
#define WIOCSTOP _IO (WATCHDOG_IOCTL_BASE, 11) /* Stop Timer */
#define WIOCGSTAT _IOR(WATCHDOG_IOCTL_BASE, 12, int)/* Get Timer Status */
/* Status flags from WIOCGSTAT ioctl
*/
#define WD_FREERUN 0x01 /* timer is running, interrupts disabled */
#define WD_EXPIRED 0x02 /* timer has expired */
#define WD_RUNNING 0x04 /* timer is running, interrupts enabled */
#define WD_STOPPED 0x08 /* timer has not been started */
#define WD_SERVICED 0x10 /* timer interrupt was serviced */
#endif /* ifndef _SPARC64_WATCHDOG_H */
Annotation
- Immediate include surface: `linux/watchdog.h`.
- Atlas domain: Architecture Layer / arch/sparc.
- Implementation status: source implementation candidate.
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.