drivers/media/i2c/cvs/Kconfig

Source file repositories/reference/linux-study-clean/drivers/media/i2c/cvs/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/media/i2c/cvs/Kconfig
Extension: [no extension]
Size: 743 bytes
Lines: 22
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

config VIDEO_INTEL_CVS
	tristate "Intel CVS CSI-2 bridge support"
	depends on I2C && ACPI && VIDEO_DEV
	depends on IPU_BRIDGE || !IPU_BRIDGE
	select MEDIA_CONTROLLER
	select VIDEO_V4L2_SUBDEV_API
	select V4L2_FWNODE
	help
	  This adds support for the Intel Computer Vision Sensing (CVS).

	  The driver registers a V4L2 sub-device to arbitrate CSI-2 link
	  ownership between the host and CVS firmware, and configures the
	  device for camera sensor streaming.

	  The driver can operate with full I2C transport or in a reduced
	  platform (GPIO-only) mode when I2C is unavailable.

	  Say Y to build into the kernel, or M to build as a module.
	  The module will be named intel_cvs. If unsure, say N.

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.