arch/sh/boards/mach-lboxre2/setup.c
Source file repositories/reference/linux-study-clean/arch/sh/boards/mach-lboxre2/setup.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/boards/mach-lboxre2/setup.c- Extension
.c- Size
- 1834 bytes
- Lines
- 80
- Domain
- Architecture Layer
- Bucket
- arch/sh
- 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/init.hlinux/platform_device.hlinux/ata_platform.hasm/machvec.hasm/addrspace.hmach/lboxre2.hasm/io.h
Detected Declarations
function lboxre2_devices_setupmodule init lboxre2_devices_setup
Annotated Snippet
device_initcall(lboxre2_devices_setup);
/*
* The Machine Vector
*/
static struct sh_machine_vector mv_lboxre2 __initmv = {
.mv_name = "L-BOX RE2",
.mv_init_irq = init_lboxre2_IRQ,
};
Annotation
- Immediate include surface: `linux/init.h`, `linux/platform_device.h`, `linux/ata_platform.h`, `asm/machvec.h`, `asm/addrspace.h`, `mach/lboxre2.h`, `asm/io.h`.
- Detected declarations: `function lboxre2_devices_setup`, `module init lboxre2_devices_setup`.
- Atlas domain: Architecture Layer / arch/sh.
- 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.