arch/sh/boards/board-edosk7760.c
Source file repositories/reference/linux-study-clean/arch/sh/boards/board-edosk7760.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/boards/board-edosk7760.c- Extension
.c- Size
- 3942 bytes
- Lines
- 179
- 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/types.hlinux/platform_device.hlinux/smc91x.hlinux/interrupt.hlinux/sh_intc.hlinux/i2c.hlinux/mtd/physmap.hasm/machvec.hasm/io.hasm/addrspace.hasm/delay.hasm/i2c-sh7760.hlinux/sizes.h
Detected Declarations
function init_edosk7760_devicesmodule init init_edosk7760_devices
Annotated Snippet
device_initcall(init_edosk7760_devices);
/*
* The Machine Vector
*/
struct sh_machine_vector mv_edosk7760 __initmv = {
.mv_name = "EDOSK7760",
};Annotation
- Immediate include surface: `linux/init.h`, `linux/types.h`, `linux/platform_device.h`, `linux/smc91x.h`, `linux/interrupt.h`, `linux/sh_intc.h`, `linux/i2c.h`, `linux/mtd/physmap.h`.
- Detected declarations: `function init_edosk7760_devices`, `module init init_edosk7760_devices`.
- 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.