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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

3845 bytes

Lines

173

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/types.h
• linux/init.h
• linux/platform_device.h
• linux/irq.h
• linux/sh_intc.h
• sound/sh_dac_audio.h
• asm/hd64461.h
• asm/io.h
• mach/hp6xx.h
• cpu/dac.h

Detected Declarations

• function dac_audio_start
• function dac_audio_stop
• function hp6xx_init_irq
• function hp6xx_devices_setup
• function hp6xx_setup
• module init hp6xx_devices_setup

Annotated Snippet

device_initcall(hp6xx_devices_setup);

static struct sh_machine_vector mv_hp6xx __initmv = {
	.mv_name = "hp6xx",
	.mv_setup = hp6xx_setup,
	/* Enable IRQ0 -> IRQ3 in IRQ_MODE */
	.mv_init_irq = hp6xx_init_irq,
};

Annotation

• Immediate include surface: `linux/types.h`, `linux/init.h`, `linux/platform_device.h`, `linux/irq.h`, `linux/sh_intc.h`, `sound/sh_dac_audio.h`, `asm/hd64461.h`, `asm/io.h`.
• Detected declarations: `function dac_audio_start`, `function dac_audio_stop`, `function hp6xx_init_irq`, `function hp6xx_devices_setup`, `function hp6xx_setup`, `module init hp6xx_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.