arch/powerpc/platforms/44x/Makefile

File Facts

System

Linux kernel

Corpus path

arch/powerpc/platforms/44x/Makefile

Extension

[no extension]

Size

597 bytes

Lines

19

Domain

Architecture Layer

Bucket

arch/powerpc

Inferred role

Architecture Layer: build/configuration rule

Status

atlas-only

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0
obj-y	+= misc_44x.o machine_check.o uic.o soc.o
ifneq ($(CONFIG_PPC4xx_CPM),y)
obj-y	+= idle.o
endif
obj-$(CONFIG_PPC44x_SIMPLE) += ppc44x_simple.o
obj-$(CONFIG_EBONY)	+= ebony.o
obj-$(CONFIG_SAM440EP) 	+= sam440ep.o
obj-$(CONFIG_WARP)	+= warp.o
obj-$(CONFIG_ISS4xx)	+= iss4xx.o
obj-$(CONFIG_CANYONLANDS)+= canyonlands.o
obj-$(CONFIG_CURRITUCK)	+= ppc476.o
obj-$(CONFIG_AKEBONO)	+= ppc476.o
obj-$(CONFIG_FSP2)	+= fsp2.o
obj-$(CONFIG_PCI)		+= pci.o
obj-$(CONFIG_PPC4xx_HSTA_MSI)	+= hsta_msi.o
obj-$(CONFIG_PPC4xx_CPM)	+= cpm.o
obj-$(CONFIG_PPC4xx_GPIO)	+= gpio.o

Annotation

• Atlas domain: Architecture Layer / arch/powerpc.
• Implementation status: atlas-only.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.