drivers/media/platform/broadcom/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/media/platform/broadcom/Kconfig
Extension: [no extension]
Size: 611 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

# SPDX-License-Identifier: GPL-2.0

config VIDEO_BCM2835_UNICAM
	tristate "Broadcom BCM283x/BCM271x Unicam video capture driver"
	depends on ARCH_BCM2835 || COMPILE_TEST
	depends on COMMON_CLK && PM
	depends on VIDEO_DEV
	select MEDIA_CONTROLLER
	select V4L2_FWNODE
	select VIDEO_V4L2_SUBDEV_API
	select VIDEOBUF2_DMA_CONTIG
	help
	  Say Y here to enable support for the BCM283x/BCM271x CSI-2 receiver.
	  This is a V4L2 driver that controls the CSI-2 receiver directly,
	  independently from the VC4 firmware.

	  To compile this driver as a module, choose M here. The module will be
	  called bcm2835-unicam.

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.