drivers/media/platform/rockchip/rkcif/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/media/platform/rockchip/rkcif/Kconfig
Extension: [no extension]
Size: 684 bytes
Lines: 19
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

config VIDEO_ROCKCHIP_CIF
	tristate "Rockchip Camera Interface (CIF)"
	depends on VIDEO_DEV
	depends on ARCH_ROCKCHIP || COMPILE_TEST
	depends on V4L_PLATFORM_DRIVERS
	depends on PM && COMMON_CLK
	select MEDIA_CONTROLLER
	select VIDEOBUF2_DMA_CONTIG
	select V4L2_FWNODE
	select VIDEO_V4L2_SUBDEV_API
	help
	  This is a driver for Rockchip Camera Interface (CIF). It is featured
	  in many Rockchips SoCs in different variations, such as the PX30
	  Video Input Processor (VIP, one Digital Video Port (DVP)) or the
	  RK3568 Video Capture (VICAP, one DVP, one MIPI CSI-2 receiver) unit.

	  To compile this driver as a module, choose M here: the module
	  will be called rockchip-cif.

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.