arch/x86/kernel/rtc.c
Source file repositories/reference/linux-study-clean/arch/x86/kernel/rtc.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/kernel/rtc.c- Extension
.c- Size
- 3335 bytes
- Lines
- 148
- Domain
- Architecture Layer
- Bucket
- arch/x86
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- 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/acpi.hlinux/platform_device.hlinux/mc146818rtc.hlinux/export.hasm/vsyscall.hasm/x86_init.hasm/time.hasm/setup.h
Detected Declarations
function mach_set_cmos_timefunction mach_get_cmos_timefunction rtc_cmos_readfunction rtc_cmos_writefunction update_persistent_clock64function read_persistent_clock64function add_rtc_cmosmodule init add_rtc_cmosexport cmos_lockexport rtc_lockexport rtc_cmos_readexport rtc_cmos_write
Annotated Snippet
device_initcall(add_rtc_cmos);Annotation
- Immediate include surface: `linux/acpi.h`, `linux/platform_device.h`, `linux/mc146818rtc.h`, `linux/export.h`, `asm/vsyscall.h`, `asm/x86_init.h`, `asm/time.h`, `asm/setup.h`.
- Detected declarations: `function mach_set_cmos_time`, `function mach_get_cmos_time`, `function rtc_cmos_read`, `function rtc_cmos_write`, `function update_persistent_clock64`, `function read_persistent_clock64`, `function add_rtc_cmos`, `module init add_rtc_cmos`, `export cmos_lock`, `export rtc_lock`.
- Atlas domain: Architecture Layer / arch/x86.
- 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.