drivers/media/pci/intel/ivsc/Kconfig

Source file repositories/reference/linux-study-clean/drivers/media/pci/intel/ivsc/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/media/pci/intel/ivsc/Kconfig
Extension: [no extension]
Size: 890 bytes
Lines: 23
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
# Copyright (C) 2023, Intel Corporation. All rights reserved.

config INTEL_VSC
	tristate "Intel Visual Sensing Controller"
	depends on INTEL_MEI && 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 Intel Visual Sensing Controller (IVSC).

	  The IVSC support is split into two devices, ACE (Algorithm
	  Context Engine) and CSI (Camera Serial Interface), each of which
	  have their own drivers. The ACE is used to select the ownership
	  of the sensor between the IVSC and the host CPU while the CSI is
	  used to both select the routing destination for the data the
	  sensor transmits over the CSI-2 bus between the IVSC and the
	  host CPU and to configure the CSI-2 bus itself.

	  The modules will be called ivsc-ace and ivsc-csi.

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.