arch/sh/boards/mach-x3proto/setup.c
Source file repositories/reference/linux-study-clean/arch/sh/boards/mach-x3proto/setup.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/boards/mach-x3proto/setup.c- Extension
.c- Size
- 5800 bytes
- Lines
- 271
- 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/kernel.hlinux/io.hlinux/smc91x.hlinux/irq.hlinux/interrupt.hlinux/input.hlinux/usb/r8a66597.hlinux/usb/m66592.hlinux/gpio/driver.hlinux/gpio_keys.hmach/ilsel.hmach/hardware.hasm/smp-ops.h
Detected Declarations
function x3proto_init_irqfunction x3proto_devices_setupfunction x3proto_setupmodule init x3proto_devices_setup
Annotated Snippet
device_initcall(x3proto_devices_setup);
static void __init x3proto_setup(char **cmdline_p)
{
register_smp_ops(&shx3_smp_ops);
}
static struct sh_machine_vector mv_x3proto __initmv = {
.mv_name = "x3proto",
.mv_setup = x3proto_setup,
};Annotation
- Immediate include surface: `linux/init.h`, `linux/platform_device.h`, `linux/kernel.h`, `linux/io.h`, `linux/smc91x.h`, `linux/irq.h`, `linux/interrupt.h`, `linux/input.h`.
- Detected declarations: `function x3proto_init_irq`, `function x3proto_devices_setup`, `function x3proto_setup`, `module init x3proto_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.