drivers/infiniband/hw/ionic/Kconfig

Source file repositories/reference/linux-study-clean/drivers/infiniband/hw/ionic/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/infiniband/hw/ionic/Kconfig
Extension: [no extension]
Size: 532 bytes
Lines: 16
Domain: Driver Families
Bucket: drivers/infiniband
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
# Copyright (C) 2018-2025, Advanced Micro Devices, Inc.

config INFINIBAND_IONIC
	tristate "AMD Pensando DSC RDMA/RoCE Support"
	depends on NETDEVICES && ETHERNET && PCI && INET && IONIC
	help
	  This enables RDMA/RoCE support for the AMD Pensando family of
	  Distributed Services Cards (DSCs).

	  To learn more, visit our website at
	  <https://www.amd.com/en/products/accelerators/pensando.html>.

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

Annotation

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