drivers/gpu/drm/tidss/Kconfig

Source file repositories/reference/linux-study-clean/drivers/gpu/drm/tidss/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/gpu/drm/tidss/Kconfig
Extension: [no extension]
Size: 582 bytes
Lines: 17
Domain: Driver Families
Bucket: drivers/gpu
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

config DRM_TIDSS
	tristate "DRM Support for TI Keystone"
	depends on DRM && OF
	depends on ARM || ARM64 || COMPILE_TEST
	select DRM_CLIENT_SELECTION
	select DRM_KMS_HELPER
	select DRM_DISPLAY_HELPER
	select DRM_BRIDGE_CONNECTOR
	select DRM_GEM_DMA_HELPER
	help
	  The TI Keystone family SoCs introduced a new generation of
	  Display SubSystem. There is currently three Keystone family
	  SoCs released with DSS. Each with somewhat different version
	  of it. The SoCs are 66AK2Gx, AM65x, and J721E. Set this to Y
	  or M to add display support for TI Keystone family
	  platforms.

Annotation

Atlas domain: Driver Families / drivers/gpu.
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.