drivers/vfio/pci/hisilicon/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/vfio/pci/hisilicon/Kconfig

Extension

[no extension]

Size

480 bytes

Lines

16

Domain

Driver Families

Bucket

drivers/vfio

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.

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 HISI_ACC_VFIO_PCI
	tristate "VFIO support for HiSilicon ACC PCI devices"
	depends on ARM64 || (COMPILE_TEST && 64BIT)
	depends on PCI_MSI
	depends on CRYPTO_DEV_HISI_QM
	depends on CRYPTO_DEV_HISI_HPRE
	depends on CRYPTO_DEV_HISI_SEC2
	depends on CRYPTO_DEV_HISI_ZIP
	select VFIO_PCI_CORE
	help
	  This provides generic PCI support for HiSilicon ACC devices
	  using the VFIO framework.

	  If you don't know what to do here, say N.

Annotation

• Atlas domain: Driver Families / drivers/vfio.
• Implementation status: atlas-only.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.