drivers/vfio/platform/reset/Kconfig

Source file repositories/reference/linux-study-clean/drivers/vfio/platform/reset/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/vfio/platform/reset/Kconfig
Extension: [no extension]
Size: 790 bytes
Lines: 26
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.

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
if VFIO_PLATFORM
config VFIO_PLATFORM_CALXEDAXGMAC_RESET
	tristate "VFIO support for calxeda xgmac reset (DEPRECATED)"
	help
	  Enables the VFIO platform driver to handle reset for Calxeda xgmac

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

config VFIO_PLATFORM_AMDXGBE_RESET
	tristate "VFIO support for AMD XGBE reset (DEPRECATED)"
	help
	  Enables the VFIO platform driver to handle reset for AMD XGBE

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

config VFIO_PLATFORM_BCMFLEXRM_RESET
	tristate "VFIO support for Broadcom FlexRM reset (DEPRECATED)"
	depends on ARCH_BCM_IPROC || COMPILE_TEST
	default ARCH_BCM_IPROC
	help
	  Enables the VFIO platform driver to handle reset for Broadcom FlexRM

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

Annotation

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