drivers/media/platform/synopsys/Kconfig

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

File Facts

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

source "drivers/media/platform/synopsys/hdmirx/Kconfig"

config VIDEO_DW_MIPI_CSI2RX
	tristate "Synopsys DesignWare MIPI CSI-2 Receiver"
	depends on ARCH_ROCKCHIP || COMPILE_TEST
	depends on VIDEO_DEV
	depends on V4L_PLATFORM_DRIVERS
	depends on PM && COMMON_CLK
	select GENERIC_PHY_MIPI_DPHY
	select MEDIA_CONTROLLER
	select V4L2_FWNODE
	select VIDEO_V4L2_SUBDEV_API
	help
	  The Synopsys DesignWare MIPI CSI-2 Receiver is a CSI-2 bridge with
	  one input port and one output port. It receives the data with the
	  help of an external MIPI PHY (C-PHY or D-PHY) and passes it to e.g.,
	  the Rockchip Video Capture (VICAP) block on recent Rockchip SoCs.
	  This is a driver for this unit.

	  To compile this driver as a module, choose M here: the module
	  will be called dw-mipi-csi2rx.

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.