drivers/dibs/Kconfig

Source file repositories/reference/linux-study-clean/drivers/dibs/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/dibs/Kconfig
Extension: [no extension]
Size: 816 bytes
Lines: 24
Domain: Driver Families
Bucket: drivers/dibs
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 DIBS
	tristate "Direct Internal Buffer Sharing support"
	default n
	help
	  Direct Internal Buffer Sharing (DIBS) is a communication method that
	  uses common physical (internal) memory for synchronous direct access
	  into a remote buffer.

	  Select this option to provide the abstraction layer between
	  dibs devices and dibs clients like the SMC protocol.
	  The module name is dibs.

config DIBS_LO
	bool "Intra-OS shortcut with dibs loopback"
	depends on DIBS
	default n
	help
	  DIBS_LO enables the creation of an software-emulated dibs device
	  named lo which can be used for transferring data when communication
	  occurs within the same OS. This helps in convenient testing of
	  dibs clients, since dibs loopback is independent of architecture or
	  hardware.

Annotation

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