arch/sh/boards/mach-se/770x/setup.c

File Facts

System

Linux kernel

Corpus path

arch/sh/boards/mach-se/770x/setup.c

Extension

.c

Size

4701 bytes

Lines

206

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.h
• linux/platform_device.h
• linux/sh_eth.h
• mach-se/mach/se.h
• mach-se/mach/mrshpc.h
• asm/machvec.h
• asm/io.h
• asm/smc37c93x.h
• asm/heartbeat.h

Detected Declarations

• function Copyright
• function smsc_setup
• function se_devices_setup
• module init se_devices_setup

Annotated Snippet

device_initcall(se_devices_setup);

/*
 * The Machine Vector
 */
static struct sh_machine_vector mv_se __initmv = {
	.mv_name		= "SolutionEngine",
	.mv_setup		= smsc_setup,
	.mv_init_irq		= init_se_IRQ,
};

Annotation

• Immediate include surface: `linux/init.h`, `linux/platform_device.h`, `linux/sh_eth.h`, `mach-se/mach/se.h`, `mach-se/mach/mrshpc.h`, `asm/machvec.h`, `asm/io.h`, `asm/smc37c93x.h`.
• Detected declarations: `function Copyright`, `function smsc_setup`, `function se_devices_setup`, `module init se_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.