drivers/media/cec/i2c/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/media/cec/i2c/Kconfig
Extension: [no extension]
Size: 706 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.

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
#
# I2C drivers

config CEC_CH7322
	tristate "Chrontel CH7322 CEC controller"
	depends on I2C
	select REGMAP
	select REGMAP_I2C
	select CEC_CORE
	help
	  This is a driver for the Chrontel CH7322 CEC controller. It uses the
	  generic CEC framework interface.
	  CEC bus is present in the HDMI connector and enables communication
	  between compatible devices.

config CEC_NXP_TDA9950
	tristate "NXP Semiconductors TDA9950/TDA998X HDMI CEC"
	depends on I2C
	select CEC_NOTIFIER
	select CEC_CORE
	default DRM_I2C_NXP_TDA998X
	help
	  This is a driver for the NXP TDA9950 CEC controller and for the CEC
	  controller block integrated into several NXP TDA998x HDMI encoders.

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.