drivers/gpu/drm/imagination/Kconfig

Source file repositories/reference/linux-study-clean/drivers/gpu/drm/imagination/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/gpu/drm/imagination/Kconfig
Extension: [no extension]
Size: 950 bytes
Lines: 33
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.

config DRM_POWERVR
	tristate "Imagination Technologies PowerVR (Series 6 and later) & IMG Graphics"
	depends on (ARM64 || RISCV && 64BIT)
	depends on DRM
	depends on MMU
	depends on PM
	depends on POWER_SEQUENCING || !POWER_SEQUENCING
	select DRM_EXEC
	select DRM_GEM_SHMEM_HELPER
	select DRM_SCHED
	select DRM_GPUVM
	select FW_LOADER
	help
	  Choose this option if you have a system that has an Imagination
	  Technologies PowerVR (Series 6 or later) or IMG GPU.

	  If "M" is selected, the module will be called powervr.

config DRM_POWERVR_KUNIT_TEST
	tristate "KUnit tests for the drm powervr driver" if !KUNIT_ALL_TESTS
	depends on DRM_POWERVR && KUNIT
	default KUNIT_ALL_TESTS
	help
	  Choose this option to allow the driver to perform selftests under
	  the kunit framework

	  Recommended for driver developers only.

	  If in doubt, say "N".

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.