drivers/rtc/rtc-rv3029c2.c

File Facts

System

Linux kernel

Corpus path

drivers/rtc/rtc-rv3029c2.c

Extension

.c

Size

22937 bytes

Lines

925

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/module.h
• linux/i2c.h
• linux/spi/spi.h
• linux/bcd.h
• linux/rtc.h
• linux/delay.h
• linux/of.h
• linux/hwmon.h
• linux/hwmon-sysfs.h
• linux/kstrtox.h
• linux/regmap.h

Detected Declarations

• struct rv3029_data
• function rv3029_eeprom_busywait
• function rv3029_eeprom_exit
• function rv3029_eeprom_enter
• function rv3029_eeprom_read
• function rv3029_eeprom_write
• function rv3029_eeprom_update_bits
• function rv3029_handle_irq
• function rv3029_read_time
• function rv3029_read_alarm
• function rv3029_alarm_irq_enable
• function rv3029_set_alarm
• function rv3029_set_time
• function rv3029_ioctl
• function rv3029_nvram_write
• function rv3029_nvram_read
• function rv3029_trickle_config
• function rv3029_read_temp
• function rv3029_hwmon_show_temp
• function rv3029_hwmon_set_update_interval
• function rv3029_hwmon_show_update_interval
• function rv3029_hwmon_register
• function rv3029_hwmon_register
• function rv3029_probe
• function rv3029_i2c_probe
• function rv3029_register_driver
• function rv3029_unregister_driver
• function rv3029_register_driver
• function rv3029_unregister_driver
• function rv3049_register_driver
• function rv3049_unregister_driver
• function rv3049_register_driver
• function rv3049_unregister_driver
• function rv30x9_exit
• module init rv30x9_init

Annotated Snippet

module_init(rv30x9_init)

static void __exit rv30x9_exit(void)
{
	rv3049_unregister_driver();
	rv3029_unregister_driver();
}
module_exit(rv30x9_exit)

MODULE_AUTHOR("Gregory Hermant <gregory.hermant@calao-systems.com>");
MODULE_AUTHOR("Michael Buesch <m@bues.ch>");
MODULE_DESCRIPTION("Micro Crystal RV3029/RV3049 RTC driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("spi:rv3049");

Annotation

• Immediate include surface: `linux/module.h`, `linux/i2c.h`, `linux/spi/spi.h`, `linux/bcd.h`, `linux/rtc.h`, `linux/delay.h`, `linux/of.h`, `linux/hwmon.h`.
• Detected declarations: `struct rv3029_data`, `function rv3029_eeprom_busywait`, `function rv3029_eeprom_exit`, `function rv3029_eeprom_enter`, `function rv3029_eeprom_read`, `function rv3029_eeprom_write`, `function rv3029_eeprom_update_bits`, `function rv3029_handle_irq`, `function rv3029_read_time`, `function rv3029_read_alarm`.
• 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.