drivers/hsi/controllers/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/hsi/controllers/Kconfig

Extension

[no extension]

Size

440 bytes

Lines

17

Domain

Driver Families

Bucket

drivers/hsi

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
#
# HSI controllers configuration
#
comment "HSI controllers"

config OMAP_SSI
	tristate "OMAP SSI hardware driver"
	depends on HSI && OF && COMMON_CLK
	depends on ARCH_OMAP3 || COMPILE_TEST
	help
	  SSI is a legacy version of HSI. It is usually used to connect
	  an application engine with a cellular modem.
	  If you say Y here, you will enable the OMAP SSI hardware driver.

	  If unsure, say N.

Annotation

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