drivers/gpu/drm/imagination/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/imagination/Makefile

Extension

[no extension]

Size

719 bytes

Lines

41

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 OR MIT
# Copyright (c) 2023 Imagination Technologies Ltd.

powervr-y := \
	pvr_ccb.o \
	pvr_cccb.o \
	pvr_context.o \
	pvr_device.o \
	pvr_device_info.o \
	pvr_drv.o \
	pvr_dump.o \
	pvr_free_list.o \
	pvr_fw.o \
	pvr_fw_meta.o \
	pvr_fw_mips.o \
	pvr_fw_riscv.o \
	pvr_fw_startstop.o \
	pvr_fw_trace.o \
	pvr_fw_util.o \
	pvr_gem.o \
	pvr_hwrt.o \
	pvr_job.o \
	pvr_mmu.o \
	pvr_power.o \
	pvr_queue.o \
	pvr_stream.o \
	pvr_stream_defs.o \
	pvr_sync.o \
	pvr_vm.o \
	pvr_vm_mips.o

powervr-$(CONFIG_DEBUG_FS) += \
	pvr_debugfs.o

powervr-$(CONFIG_TRACEPOINTS) += \
	pvr_trace_points.o

obj-$(CONFIG_DRM_POWERVR) += powervr.o

obj-$(CONFIG_DRM_POWERVR_KUNIT_TEST) += pvr_test.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.