drivers/gpu/drm/vc4/Makefile

Source file repositories/reference/linux-study-clean/drivers/gpu/drm/vc4/Makefile

File Facts

System: Linux kernel
Corpus path: drivers/gpu/drm/vc4/Makefile
Extension: [no extension]
Size: 663 bytes
Lines: 38
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
# Please keep these build lists sorted!

# core driver code
vc4-y := \
	vc4_bo.o \
	vc4_crtc.o \
	vc4_drv.o \
	vc4_dpi.o \
	vc4_dsi.o \
	vc4_fence.o \
	vc4_kms.o \
	vc4_gem.o \
	vc4_hdmi.o \
	vc4_hdmi_phy.o \
	vc4_vec.o \
	vc4_hvs.o \
	vc4_irq.o \
	vc4_perfmon.o \
	vc4_plane.o \
	vc4_render_cl.o \
	vc4_trace_points.o \
	vc4_txp.o \
	vc4_v3d.o \
	vc4_validate.o \
	vc4_validate_shaders.o

vc4-$(CONFIG_DRM_VC4_KUNIT_TEST) += \
	tests/vc4_mock.o \
	tests/vc4_mock_crtc.o \
	tests/vc4_mock_output.o \
	tests/vc4_mock_plane.o \
	tests/vc4_test_pv_muxing.o

vc4-$(CONFIG_DEBUG_FS) += vc4_debugfs.o

obj-$(CONFIG_DRM_VC4)  += vc4.o

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.