drivers/media/test-drivers/Kconfig
Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/test-drivers/Kconfig- Extension
[no extension]- Size
- 997 bytes
- Lines
- 41
- 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-only
menuconfig V4L_TEST_DRIVERS
bool "V4L test drivers"
depends on VIDEO_DEV
if V4L_TEST_DRIVERS
config VIDEO_VIM2M
tristate "Virtual Memory-to-Memory Driver"
depends on VIDEO_DEV
select VIDEOBUF2_VMALLOC
select V4L2_MEM2MEM_DEV
select MEDIA_CONTROLLER
help
This is a virtual test device for the memory-to-memory driver
framework.
source "drivers/media/test-drivers/vicodec/Kconfig"
source "drivers/media/test-drivers/vimc/Kconfig"
source "drivers/media/test-drivers/vivid/Kconfig"
source "drivers/media/test-drivers/visl/Kconfig"
endif #V4L_TEST_DRIVERS
menuconfig DVB_TEST_DRIVERS
bool "DVB test drivers"
depends on DVB_CORE && MEDIA_SUPPORT && I2C
help
Enables DVB test drivers.
This enables the DVB test drivers. They are meant as an aid for
DVB device driver writers and developers working on userspace
media applications.
if DVB_TEST_DRIVERS
source "drivers/media/test-drivers/vidtv/Kconfig"
endif #DVB_TEST_DRIVERS
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.