arch/sh/boards/mach-se/7721/setup.c

Source file repositories/reference/linux-study-clean/arch/sh/boards/mach-se/7721/setup.c

File Facts

System: Linux kernel
Corpus path: arch/sh/boards/mach-se/7721/setup.c
Extension: .c
Size: 2154 bytes
Lines: 93
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
mach-se/mach/se7721.h
mach-se/mach/mrshpc.h
asm/machvec.h
asm/io.h
asm/heartbeat.h

Detected Declarations

function se7721_devices_setup
function se7721_setup
module init se7721_devices_setup

Annotated Snippet

device_initcall(se7721_devices_setup);

static void __init se7721_setup(char **cmdline_p)
{
	/* for USB */
	__raw_writew(0x0000, 0xA405010C);	/* PGCR */
	__raw_writew(0x0000, 0xA405010E);	/* PHCR */
	__raw_writew(0x00AA, 0xA4050118);	/* PPCR */
	__raw_writew(0x0000, 0xA4050124);	/* PSELA */
}

/*
 * The Machine Vector
 */
struct sh_machine_vector mv_se7721 __initmv = {
	.mv_name		= "Solution Engine 7721",
	.mv_setup		= se7721_setup,
	.mv_init_irq		= init_se7721_IRQ,
};

Annotation

Immediate include surface: `linux/init.h`, `linux/platform_device.h`, `mach-se/mach/se7721.h`, `mach-se/mach/mrshpc.h`, `asm/machvec.h`, `asm/io.h`, `asm/heartbeat.h`.
Detected declarations: `function se7721_devices_setup`, `function se7721_setup`, `module init se7721_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.