drivers/media/pci/cobalt/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/media/pci/cobalt/Kconfig

Extension

[no extension]

Size

762 bytes

Lines

26

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.

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_COBALT
	tristate "Cisco Cobalt support"
	depends on VIDEO_DEV && I2C
	depends on PCI_MSI && MTD_COMPLEX_MAPPINGS
	depends on (GPIOLIB && DRM_I2C_ADV7511=n) || COMPILE_TEST
	depends on SND
	depends on MTD
	select MEDIA_CONTROLLER
	select VIDEO_V4L2_SUBDEV_API
	select I2C_ALGOBIT
	select SND_PCM
	select VIDEO_ADV7604
	select VIDEO_ADV7511
	select VIDEO_ADV7842
	select VIDEOBUF2_DMA_SG
	help
	  This is a video4linux driver for the Cisco PCIe Cobalt card.

	  This board is sadly not available outside of Cisco, but it is
	  very useful as an example of a real driver that uses all the
	  latest frameworks and APIs.

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

Annotation

• Atlas domain: Driver Families / drivers/media.
• Implementation status: atlas-only.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.