drivers/media/platform/synopsys/hdmirx/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/media/platform/synopsys/hdmirx/Kconfig
Extension: [no extension]
Size: 1283 bytes
Lines: 37
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_SYNOPSYS_HDMIRX
	tristate "Synopsys DesignWare HDMI Receiver driver"
	depends on ARCH_ROCKCHIP || COMPILE_TEST
	depends on VIDEO_DEV
	select MEDIA_CONTROLLER
	select VIDEO_V4L2_SUBDEV_API
	select VIDEOBUF2_DMA_CONTIG
	select CEC_CORE
	select HDMI
	help
	  Support for Synopsys HDMI HDMI RX Controller.
	  This driver supports HDMI 2.0 version.

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

config VIDEO_SYNOPSYS_HDMIRX_LOAD_DEFAULT_EDID
	bool "Load default EDID"
	depends on VIDEO_SYNOPSYS_HDMIRX
	help
	  Preload default EDID (Extended Display Identification Data)
	  branded by Linux Foundation that exposes display modes up
	  to 4k@30Hz, which have best compatibility with HDMI transmitters.

	  Enabling this option is recommended for a non-production use-cases.
	  It will make driver usable out-of-the-box.

	  For a higher display modes you will need to load customized EDID
	  from userspace using v4l2-ctl tool or by other means.

	  Without enabling this option driver will be practically
	  non-functional until EDID will be loaded from userspace.
	  Which is a wanted behavior when using this driver in a
	  commercial product that should utilize own branded EDID.

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.