drivers/media/test-drivers/visl/Kconfig

Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/visl/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/media/test-drivers/visl/Kconfig
Extension: [no extension]
Size: 771 bytes
Lines: 29
Domain: Driver Families
Bucket: drivers/media
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+
config VIDEO_VISL
	tristate "Virtual Stateless Decoder Driver (visl)"
	depends on VIDEO_DEV
	select FONT_SUPPORT
	select FONT_8x16
	select VIDEOBUF2_VMALLOC
	select V4L2_MEM2MEM_DEV
	select MEDIA_CONTROLLER
	select VIDEO_V4L2_TPG
	help

	  A virtual stateless decoder device for uAPI development purposes.

	  A userspace implementation can use visl to run a decoding loop even
	  when no hardware is available or when the kernel uAPI for the codec
	  has not been upstreamed yet. This can reveal bugs at an early stage.

	  When in doubt, say N.

config VISL_DEBUGFS
	bool "Enable debugfs for visl"
	depends on VIDEO_VISL
	depends on DEBUG_FS

	help
	  Choose Y to dump the bitstream buffers through debugfs.
	  When in doubt, say N.

Annotation

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