arch/sh/boards/mach-landisk/setup.c
Source file repositories/reference/linux-study-clean/arch/sh/boards/mach-landisk/setup.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/boards/mach-landisk/setup.c- Extension
.c- Size
- 2575 bytes
- Lines
- 103
- 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.hlinux/pm.hlinux/mm.hasm/machvec.hmach-landisk/mach/iodata_landisk.hasm/io.h
Detected Declarations
function Copyrightfunction landisk_devices_setupfunction landisk_setupmodule init landisk_devices_setup
Annotated Snippet
device_initcall(landisk_devices_setup);
static void __init landisk_setup(char **cmdline_p)
{
/* I/O port identity mapping */
__set_io_port_base(0);
/* LED ON */
__raw_writeb(__raw_readb(PA_LED) | 0x03, PA_LED);
printk(KERN_INFO "I-O DATA DEVICE, INC. \"LANDISK Series\" support.\n");
pm_power_off = landisk_power_off;
}
/*
* The Machine Vector
*/
static struct sh_machine_vector mv_landisk __initmv = {
.mv_name = "LANDISK",
.mv_setup = landisk_setup,
.mv_init_irq = init_landisk_IRQ,
};
Annotation
- Immediate include surface: `linux/init.h`, `linux/platform_device.h`, `linux/ata_platform.h`, `linux/pm.h`, `linux/mm.h`, `asm/machvec.h`, `mach-landisk/mach/iodata_landisk.h`, `asm/io.h`.
- Detected declarations: `function Copyright`, `function landisk_devices_setup`, `function landisk_setup`, `module init landisk_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.