drivers/media/platform/imagination/Kconfig

Source file repositories/reference/linux-study-clean/drivers/media/platform/imagination/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/media/platform/imagination/Kconfig
Extension: [no extension]
Size: 557 bytes
Lines: 15
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_E5010_JPEG_ENC
	tristate "Imagination E5010 JPEG Encoder Driver"
	depends on VIDEO_DEV
	depends on ARCH_K3 || COMPILE_TEST
	select VIDEOBUF2_DMA_CONTIG
	select VIDEOBUF2_VMALLOC
	select V4L2_MEM2MEM_DEV
	select V4L2_JPEG_HELPER
	help
	  This is a video4linux2 M2M driver for Imagination E5010 JPEG encoder,
	  which supports JPEG and MJPEG baseline encoding of YUV422 and YUV420
	  semiplanar video formats, with resolution ranging from 64x64 to 8K x 8K
	  pixels. The module will be named as e5010_jpeg_enc.

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.