arch/mips/ralink/Platform

Source file repositories/reference/linux-study-clean/arch/mips/ralink/Platform

File Facts

System: Linux kernel
Corpus path: arch/mips/ralink/Platform
Extension: [no extension]
Size: 873 bytes
Lines: 34
Domain: Architecture Layer
Bucket: arch/mips
Inferred role: Architecture Layer: arch/mips
Status: atlas-only

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

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#
# Ralink SoC common stuff
#
cflags-$(CONFIG_RALINK)		+= -I$(srctree)/arch/mips/include/asm/mach-ralink

#
# Ralink RT288x
#
load-$(CONFIG_SOC_RT288X)	+= 0xffffffff88000000
cflags-$(CONFIG_SOC_RT288X)	+= -I$(srctree)/arch/mips/include/asm/mach-ralink/rt288x

#
# Ralink RT305x
#
load-$(CONFIG_SOC_RT305X)	+= 0xffffffff80000000
cflags-$(CONFIG_SOC_RT305X)	+= -I$(srctree)/arch/mips/include/asm/mach-ralink/rt305x

#
# Ralink RT3883
#
load-$(CONFIG_SOC_RT3883)	+= 0xffffffff80000000
cflags-$(CONFIG_SOC_RT3883)	+= -I$(srctree)/arch/mips/include/asm/mach-ralink/rt3883

#
# Ralink MT7620
#
load-$(CONFIG_SOC_MT7620)	+= 0xffffffff80000000
cflags-$(CONFIG_SOC_MT7620)	+= -I$(srctree)/arch/mips/include/asm/mach-ralink/mt7620

# Ralink MT7621
#
load-$(CONFIG_SOC_MT7621)	+= 0xffffffff80001000
cflags-$(CONFIG_SOC_MT7621)	+= -I$(srctree)/arch/mips/include/asm/mach-ralink/mt7621

Annotation

Atlas domain: Architecture Layer / arch/mips.
Implementation status: atlas-only.

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.