drivers/watchdog/sun4v_wdt.c

File Facts

System

Linux kernel

Corpus path

drivers/watchdog/sun4v_wdt.c

Extension

.c

Size

4390 bytes

Lines

188

Domain

Driver Families

Bucket

drivers/watchdog

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/errno.h
• linux/init.h
• linux/kernel.h
• linux/module.h
• linux/moduleparam.h
• linux/watchdog.h
• asm/hypervisor.h
• asm/mdesc.h

Detected Declarations

• function sun4v_wdt_stop
• function sun4v_wdt_ping
• function sun4v_wdt_set_timeout
• function sun4v_wdt_init
• function sun4v_wdt_exit
• module init sun4v_wdt_init

Annotated Snippet

module_init(sun4v_wdt_init);
module_exit(sun4v_wdt_exit);

MODULE_AUTHOR("Wim Coekaerts <wim.coekaerts@oracle.com>");
MODULE_DESCRIPTION("sun4v watchdog driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/errno.h`, `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/watchdog.h`, `asm/hypervisor.h`, `asm/mdesc.h`.
• Detected declarations: `function sun4v_wdt_stop`, `function sun4v_wdt_ping`, `function sun4v_wdt_set_timeout`, `function sun4v_wdt_init`, `function sun4v_wdt_exit`, `module init sun4v_wdt_init`.
• Atlas domain: Driver Families / drivers/watchdog.
• Implementation status: integration 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.