drivers/gpu/drm/v3d/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/v3d/Makefile

Extension

[no extension]

Size

401 bytes

Lines

24

Domain

Driver Families

Bucket

drivers/gpu

Inferred role

Driver Families: build/configuration rule

Status

atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

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
# Please keep these build lists sorted!

# core driver code
v3d-y := \
	v3d_bo.o \
	v3d_drv.o \
	v3d_fence.o \
	v3d_gem.o \
	v3d_irq.o \
	v3d_mmu.o \
	v3d_perfmon.o \
	v3d_power.o \
	v3d_trace_points.o \
	v3d_sched.o \
	v3d_sysfs.o \
	v3d_submit.o

v3d-$(CONFIG_DEBUG_FS) += v3d_debugfs.o

obj-$(CONFIG_DRM_V3D)  += v3d.o

CFLAGS_v3d_trace_points.o := -I$(src)

Annotation

• Atlas domain: Driver Families / drivers/gpu.
• 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.