arch/arm/mach-mv78xx0/buffalo-wxl-setup.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-mv78xx0/buffalo-wxl-setup.c

Extension

.c

Size

3725 bytes

Lines

184

Domain

Architecture Layer

Bucket

arch/arm

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/kernel.h
• linux/init.h
• linux/platform_device.h
• linux/ata_platform.h
• linux/mv643xx_eth.h
• linux/ethtool.h
• linux/i2c.h
• linux/gpio.h
• linux/gpio_keys.h
• linux/input.h
• asm/mach-types.h
• asm/mach/arch.h
• mv78xx0.h
• common.h
• mpp.h

Detected Declarations

• function wxl_init
• function wxl_pci_init
• module init wxl_pci_init

Annotated Snippet

subsys_initcall(wxl_pci_init);

MACHINE_START(TERASTATION_WXL, "Buffalo Nas WXL")
	/* Maintainer: Sebastien Requiem <sebastien@requiem.fr> */
	.atag_offset	= 0x100,
	.nr_irqs	= MV78XX0_NR_IRQS,
	.init_machine	= wxl_init,
	.map_io		= mv78xx0_map_io,
	.init_early	= mv78xx0_init_early,
	.init_irq	= mv78xx0_init_irq,
	.init_time	= mv78xx0_timer_init,
	.restart	= mv78xx0_restart,
MACHINE_END

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/platform_device.h`, `linux/ata_platform.h`, `linux/mv643xx_eth.h`, `linux/ethtool.h`, `linux/i2c.h`, `linux/gpio.h`.
• Detected declarations: `function wxl_init`, `function wxl_pci_init`, `module init wxl_pci_init`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.