arch/sh/boards/mach-rsk/setup.c

File Facts

System

Linux kernel

Corpus path

arch/sh/boards/mach-rsk/setup.c

Extension

.c

Size

1938 bytes

Lines

85

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/types.h
• linux/platform_device.h
• linux/interrupt.h
• linux/mtd/mtd.h
• linux/mtd/partitions.h
• linux/mtd/physmap.h
• linux/mtd/map.h
• linux/regulator/fixed.h
• linux/regulator/machine.h
• asm/machvec.h
• asm/io.h

Detected Declarations

• function rsk_devices_setup
• module init rsk_devices_setup

Annotated Snippet

device_initcall(rsk_devices_setup);

/*
 * The Machine Vector
 */
static struct sh_machine_vector mv_rsk __initmv = {
	.mv_name        = "RSK+",
};

Annotation

• Immediate include surface: `linux/init.h`, `linux/types.h`, `linux/platform_device.h`, `linux/interrupt.h`, `linux/mtd/mtd.h`, `linux/mtd/partitions.h`, `linux/mtd/physmap.h`, `linux/mtd/map.h`.
• Detected declarations: `function rsk_devices_setup`, `module init rsk_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.