drivers/interconnect/samsung/Kconfig

Source file repositories/reference/linux-study-clean/drivers/interconnect/samsung/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/interconnect/samsung/Kconfig
Extension: [no extension]
Size: 523 bytes
Lines: 16
Domain: Driver Families
Bucket: drivers/interconnect
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-only
config INTERCONNECT_SAMSUNG
	bool "Samsung SoC interconnect drivers"
	depends on ARCH_EXYNOS || COMPILE_TEST
	help
	  Interconnect drivers for Samsung SoCs.

config INTERCONNECT_EXYNOS
	tristate "Exynos SoC generic interconnect driver"
	depends on INTERCONNECT_SAMSUNG
	default y if ARCH_EXYNOS
	help
	  Generic interconnect driver for Samsung Exynos SoCs (e.g. Exynos3250,
	  Exynos4210, Exynos4412, Exynos542x, Exynos5433).
	  Choose Y here only if you build for such Samsung SoC.

Annotation

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