drivers/rtc/rtc-test.c
Source file repositories/reference/linux-study-clean/drivers/rtc/rtc-test.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/rtc/rtc-test.c- Extension
.c- Size
- 4222 bytes
- Lines
- 202
- Domain
- Driver Families
- Bucket
- drivers/rtc
- 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/err.hlinux/rtc.hlinux/platform_device.h
Detected Declarations
struct rtc_test_datafunction test_rtc_read_alarmfunction test_rtc_set_alarmfunction test_rtc_read_timefunction test_rtc_set_timefunction test_rtc_alarm_irq_enablefunction test_rtc_alarm_handlerfunction test_probefunction test_initfunction test_exitmodule init test_init
Annotated Snippet
module_init(test_init);
module_exit(test_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/err.h`, `linux/rtc.h`, `linux/platform_device.h`.
- Detected declarations: `struct rtc_test_data`, `function test_rtc_read_alarm`, `function test_rtc_set_alarm`, `function test_rtc_read_time`, `function test_rtc_set_time`, `function test_rtc_alarm_irq_enable`, `function test_rtc_alarm_handler`, `function test_probe`, `function test_init`, `function test_exit`.
- Atlas domain: Driver Families / drivers/rtc.
- 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.