arch/mips/alchemy/board-xxs1500.c
Source file repositories/reference/linux-study-clean/arch/mips/alchemy/board-xxs1500.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/alchemy/board-xxs1500.c- Extension
.c- Size
- 3327 bytes
- Lines
- 126
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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/kernel.hlinux/init.hlinux/interrupt.hlinux/platform_device.hlinux/gpio.hlinux/delay.hlinux/pm.hasm/bootinfo.hasm/reboot.hasm/setup.hasm/mach-au1x00/au1000.hasm/mach-au1x00/gpio-au1000.hprom.h
Detected Declarations
function prom_putcharfunction xxs1500_resetfunction xxs1500_power_offfunction board_setupfunction xxs1500_dev_initmodule init xxs1500_dev_init
Annotated Snippet
device_initcall(xxs1500_dev_init);
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/interrupt.h`, `linux/platform_device.h`, `linux/gpio.h`, `linux/delay.h`, `linux/pm.h`, `asm/bootinfo.h`.
- Detected declarations: `function prom_putchar`, `function xxs1500_reset`, `function xxs1500_power_off`, `function board_setup`, `function xxs1500_dev_init`, `module init xxs1500_dev_init`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.