arch/arm/mach-versatile/Makefile

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-versatile/Makefile

Extension

[no extension]

Size

837 bytes

Lines

34

Domain

Architecture Layer

Bucket

arch/arm

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.

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-only
#
# Makefile for the linux kernel.
#

# versatile
obj-$(CONFIG_ARCH_VERSATILE)		+= versatile.o

# integrator
obj-$(CONFIG_ARCH_INTEGRATOR)		+= integrator.o
obj-$(CONFIG_ARCH_INTEGRATOR_AP)	+= integrator_ap.o
obj-$(CONFIG_ARCH_INTEGRATOR_CP)	+= integrator_cp.o

# realview
obj-$(CONFIG_ARCH_REALVIEW)		+= realview.o

# vexpress
obj-$(CONFIG_ARCH_VEXPRESS)		:= v2m.o
obj-$(CONFIG_ARCH_VEXPRESS_SPC)		+= spc.o
CFLAGS_REMOVE_spc.o			= -pg
obj-$(CONFIG_ARCH_VEXPRESS_TC2_PM)	+= tc2_pm.o
CFLAGS_tc2_pm.o				+= -march=armv7-a
CFLAGS_REMOVE_tc2_pm.o			= -pg

# mps2
obj-$(CONFIG_ARCH_MPS2)			+= v2m-mps2.o

ifdef CONFIG_SMP
obj-y					+= headsmp.o platsmp.o
obj-$(CONFIG_ARCH_REALVIEW)		+= platsmp-realview.o
obj-$(CONFIG_ARCH_VEXPRESS)		+= platsmp-vexpress.o
obj-$(CONFIG_HOTPLUG_CPU)		+= hotplug.o
endif

Annotation

• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: atlas-only.

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.