drivers/gpu/drm/virtio/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/gpu/drm/virtio/Kconfig
Extension: [no extension]
Size: 679 bytes
Lines: 26
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
config DRM_VIRTIO_GPU
	tristate "Virtio GPU driver"
	depends on DRM && VIRTIO_MENU && MMU
	select VIRTIO
	select DRM_CLIENT_SELECTION
	select DRM_KMS_HELPER
	select DRM_GEM_SHMEM_HELPER
	select VIRTIO_DMA_SHARED_BUFFER
	help
	   This is the virtual GPU driver for virtio.  It can be used with
	   QEMU based VMMs (like KVM or Xen).

	   If unsure say M.

config DRM_VIRTIO_GPU_KMS
	bool "Virtio GPU driver modesetting support"
	depends on DRM_VIRTIO_GPU
	default y
	help
	   Enable modesetting support for virtio GPU driver.  This can be
	   disabled in cases where only "headless" usage of the GPU is
	   required.

	   If unsure, say Y.

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.