drivers/char/hangcheck-timer.c
Source file repositories/reference/linux-study-clean/drivers/char/hangcheck-timer.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/char/hangcheck-timer.c- Extension
.c- Size
- 5193 bytes
- Lines
- 180
- Domain
- Driver Families
- Bucket
- drivers/char
- 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/module.hlinux/moduleparam.hlinux/types.hlinux/kernel.hlinux/fs.hlinux/mm.hlinux/reboot.hlinux/init.hlinux/delay.hlinux/uaccess.hlinux/sysrq.hlinux/timer.hlinux/hrtimer.h
Detected Declarations
function hangcheck_parse_tickfunction hangcheck_parse_marginfunction hangcheck_parse_rebootfunction hangcheck_parse_dump_tasksfunction hangcheck_firefunction hangcheck_initfunction hangcheck_exitmodule init hangcheck_init
Annotated Snippet
module_init(hangcheck_init);
module_exit(hangcheck_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/types.h`, `linux/kernel.h`, `linux/fs.h`, `linux/mm.h`, `linux/reboot.h`, `linux/init.h`.
- Detected declarations: `function hangcheck_parse_tick`, `function hangcheck_parse_margin`, `function hangcheck_parse_reboot`, `function hangcheck_parse_dump_tasks`, `function hangcheck_fire`, `function hangcheck_init`, `function hangcheck_exit`, `module init hangcheck_init`.
- Atlas domain: Driver Families / drivers/char.
- 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.