arch/powerpc/platforms/44x/iss4xx.c

File Facts

System

Linux kernel

Corpus path

arch/powerpc/platforms/44x/iss4xx.c

Extension

.c

Size

3840 bytes

Lines

151

Domain

Architecture Layer

Bucket

arch/powerpc

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/of_platform.h
• linux/rtc.h
• asm/machdep.h
• asm/prom.h
• asm/udbg.h
• asm/time.h
• asm/uic.h
• asm/ppc4xx.h
• asm/mpic.h
• asm/mmu.h

Detected Declarations

• function iss4xx_device_probe
• function iss4xx_init_irq
• function smp_iss4xx_setup_cpu
• function smp_iss4xx_kick_cpu
• function iss4xx_smp_init
• function iss4xx_smp_init

Annotated Snippet

static void __init iss4xx_smp_init(void) { }
#endif /* CONFIG_SMP */

static void __init iss4xx_setup_arch(void)
{
	iss4xx_smp_init();
}

define_machine(iss4xx) {
	.name			= "ISS-4xx",
	.compatible		= "ibm,iss-4xx",
	.progress		= udbg_progress,
	.init_IRQ		= iss4xx_init_irq,
	.setup_arch		= iss4xx_setup_arch,
	.restart		= ppc4xx_reset_system,
};

Annotation

• Immediate include surface: `linux/init.h`, `linux/of_platform.h`, `linux/rtc.h`, `asm/machdep.h`, `asm/prom.h`, `asm/udbg.h`, `asm/time.h`, `asm/uic.h`.
• Detected declarations: `function iss4xx_device_probe`, `function iss4xx_init_irq`, `function smp_iss4xx_setup_cpu`, `function smp_iss4xx_kick_cpu`, `function iss4xx_smp_init`, `function iss4xx_smp_init`.
• Atlas domain: Architecture Layer / arch/powerpc.
• 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.