drivers/rtc/rtc-opal.c

File Facts

System

Linux kernel

Corpus path

drivers/rtc/rtc-opal.c

Extension

.c

Size

7031 bytes

Lines

302

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/err.h
• linux/rtc.h
• linux/delay.h
• linux/bcd.h
• linux/platform_device.h
• linux/of.h
• asm/opal.h
• asm/firmware.h

Detected Declarations

• function Copyright
• function tm_to_opal
• function opal_get_rtc_time
• function opal_set_rtc_time
• function opal_get_tpo_time
• function opal_set_tpo_time
• function opal_tpo_alarm_irq_enable
• function opal_rtc_probe
• function opal_rtc_init
• function opal_rtc_exit
• module init opal_rtc_init

Annotated Snippet

module_init(opal_rtc_init);
module_exit(opal_rtc_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/err.h`, `linux/rtc.h`, `linux/delay.h`, `linux/bcd.h`, `linux/platform_device.h`, `linux/of.h`, `asm/opal.h`.
• Detected declarations: `function Copyright`, `function tm_to_opal`, `function opal_get_rtc_time`, `function opal_set_rtc_time`, `function opal_get_tpo_time`, `function opal_set_tpo_time`, `function opal_tpo_alarm_irq_enable`, `function opal_rtc_probe`, `function opal_rtc_init`, `function opal_rtc_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.