arch/mips/include/asm/mach-dec/mc146818rtc.h
Source file repositories/reference/linux-study-clean/arch/mips/include/asm/mach-dec/mc146818rtc.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/include/asm/mach-dec/mc146818rtc.h- Extension
.h- Size
- 935 bytes
- Lines
- 40
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source 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.
Dependency Surface
linux/types.hasm/addrspace.hasm/dec/system.h
Detected Declarations
function CMOS_READfunction CMOS_WRITE
Annotated Snippet
#ifndef __ASM_MIPS_DEC_RTC_DEC_H
#define __ASM_MIPS_DEC_RTC_DEC_H
#include <linux/types.h>
#include <asm/addrspace.h>
#include <asm/dec/system.h>
extern volatile u8 *dec_rtc_base;
#define ARCH_RTC_LOCATION
#define RTC_PORT(x) CPHYSADDR((long)dec_rtc_base)
#define RTC_IO_EXTENT dec_kn_slot_size
#define RTC_IOMAPPED 0
#undef RTC_IRQ
#define RTC_DEC_YEAR 0x3f /* Where we store the real year on DECs. */
static inline unsigned char CMOS_READ(unsigned long addr)
{
return dec_rtc_base[addr * 4];
}
static inline void CMOS_WRITE(unsigned char data, unsigned long addr)
{
dec_rtc_base[addr * 4] = data;
}
#define RTC_ALWAYS_BCD 0
#endif /* __ASM_MIPS_DEC_RTC_DEC_H */
Annotation
- Immediate include surface: `linux/types.h`, `asm/addrspace.h`, `asm/dec/system.h`.
- Detected declarations: `function CMOS_READ`, `function CMOS_WRITE`.
- Atlas domain: Architecture Layer / arch/mips.
- Implementation status: source 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.