drivers/rtc/rtc-pcf85063.c

File Facts

System

Linux kernel

Corpus path

drivers/rtc/rtc-pcf85063.c

Extension

.c

Size

20370 bytes

Lines

833

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/clk-provider.h
• linux/i2c.h
• linux/bcd.h
• linux/rtc.h
• linux/module.h
• linux/of.h
• linux/pm_wakeirq.h
• linux/regmap.h
• linux/spi/spi.h

Detected Declarations

• struct pcf85063_config
• struct pcf85063
• function pcf85063_rtc_read_time
• function pcf85063_rtc_set_time
• function pcf85063_rtc_read_alarm
• function pcf85063_rtc_set_alarm
• function pcf85063_rtc_alarm_irq_enable
• function pcf85063_rtc_handle_irq
• function pcf85063_read_offset
• function pcf85063_set_offset
• function pcf85063_ioctl
• function pcf85063_nvmem_read
• function pcf85063_nvmem_write
• function pcf85063_load_capacitance
• function pcf85063_clkout_recalc_rate
• function pcf85063_clkout_determine_rate
• function pcf85063_clkout_set_rate
• function pcf85063_clkout_control
• function pcf85063_clkout_prepare
• function pcf85063_clkout_unprepare
• function pcf85063_clkout_is_prepared
• function pcf85063_probe
• function pcf85063_i2c_probe
• function pcf85063_register_driver
• function pcf85063_unregister_driver
• function pcf85063_register_driver
• function pcf85063_unregister_driver
• function rv8063_probe
• function rv8063_register_driver
• function rv8063_unregister_driver
• function rv8063_register_driver
• function rv8063_unregister_driver
• function pcf85063_exit
• module init pcf85063_init

Annotated Snippet

module_init(pcf85063_init);

static void __exit pcf85063_exit(void)
{
	rv8063_unregister_driver();
	pcf85063_unregister_driver();
}
module_exit(pcf85063_exit);

MODULE_AUTHOR("Søren Andersen <san@rosetechnology.dk>");
MODULE_DESCRIPTION("PCF85063 RTC driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/clk-provider.h`, `linux/i2c.h`, `linux/bcd.h`, `linux/rtc.h`, `linux/module.h`, `linux/of.h`, `linux/pm_wakeirq.h`, `linux/regmap.h`.
• Detected declarations: `struct pcf85063_config`, `struct pcf85063`, `function pcf85063_rtc_read_time`, `function pcf85063_rtc_set_time`, `function pcf85063_rtc_read_alarm`, `function pcf85063_rtc_set_alarm`, `function pcf85063_rtc_alarm_irq_enable`, `function pcf85063_rtc_handle_irq`, `function pcf85063_read_offset`, `function pcf85063_set_offset`.
• Atlas domain: Driver Families / drivers/rtc.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.