arch/mips/ath25/devices.c

File Facts

System

Linux kernel

Corpus path

arch/mips/ath25/devices.c

Extension

.c

Size

2689 bytes

Lines

129

Domain

Architecture Layer

Bucket

arch/mips

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/serial_8250.h
• linux/platform_device.h
• asm/bootinfo.h
• ath25_platform.h
• devices.h
• ar5312.h
• ar2315.h

Detected Declarations

• function ath25_serial_setup
• function ath25_add_wmac
• function ath25_register_devices
• function ath25_arch_init
• module init ath25_register_devices

Annotated Snippet

device_initcall(ath25_register_devices);

static int __init ath25_arch_init(void)
{
	if (is_ar5312())
		ar5312_arch_init();
	else
		ar2315_arch_init();

	return 0;
}

arch_initcall(ath25_arch_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/serial_8250.h`, `linux/platform_device.h`, `asm/bootinfo.h`, `ath25_platform.h`, `devices.h`, `ar5312.h`.
• Detected declarations: `function ath25_serial_setup`, `function ath25_add_wmac`, `function ath25_register_devices`, `function ath25_arch_init`, `module init ath25_register_devices`.
• Atlas domain: Architecture Layer / arch/mips.
• 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.