drivers/acpi/nfit/Kconfig

Source file repositories/reference/linux-study-clean/drivers/acpi/nfit/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/acpi/nfit/Kconfig
Extension: [no extension]
Size: 1010 bytes
Lines: 27
Domain: Driver Families
Bucket: drivers/acpi
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 ACPI_NFIT
	tristate "ACPI NVDIMM Firmware Interface Table (NFIT)"
	depends on PHYS_ADDR_T_64BIT
	depends on BLK_DEV
	depends on ARCH_HAS_PMEM_API
	select LIBNVDIMM
	help
	  Infrastructure to probe ACPI 6 compliant platforms for
	  NVDIMMs (NFIT) and register a libnvdimm device tree.  In
	  addition to storage devices this also enables libnvdimm to pass
	  ACPI._DSM messages for platform/dimm configuration.

	  To compile this driver as a module, choose M here:
	  the module will be called nfit.

config NFIT_SECURITY_DEBUG
	bool "Enable debug for NVDIMM security commands"
	depends on ACPI_NFIT
	help
	  Some NVDIMM devices and controllers support encryption and
	  other security features. The payloads for the commands that
	  enable those features may contain sensitive clear-text
	  security material. Disable debug of those command payloads
	  by default. If you are a kernel developer actively working
	  on NVDIMM security enabling say Y, otherwise say N.

Annotation

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