drivers/media/platform/nuvoton/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/media/platform/nuvoton/Kconfig
Extension: [no extension]
Size: 583 bytes
Lines: 16
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

comment "Nuvoton media platform drivers"

config VIDEO_NPCM_VCD_ECE
	tristate "Nuvoton NPCM Video Capture/Encode Engine driver"
	depends on V4L_PLATFORM_DRIVERS && VIDEO_DEV
	depends on ARCH_NPCM || COMPILE_TEST
	select VIDEOBUF2_DMA_CONTIG
	help
	  Support for the Video Capture/Differentiation Engine (VCD) and
	  Encoding Compression Engine (ECE) present on Nuvoton NPCM SoCs.
	  The VCD can capture a frame from digital video input and compare
	  two frames in memory, and then the ECE can compress the frame
	  data into HEXTILE format.

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.