drivers/ras/amd/atl/Kconfig

Source file repositories/reference/linux-study-clean/drivers/ras/amd/atl/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/ras/amd/atl/Kconfig
Extension: [no extension]
Size: 662 bytes
Lines: 26
Domain: Driver Families
Bucket: drivers/ras
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-or-later
#
# AMD Address Translation Library Kconfig
#
# Copyright (c) 2023, Advanced Micro Devices, Inc.
# All Rights Reserved.
#
# Author: Yazen Ghannam <Yazen.Ghannam@amd.com>

config AMD_ATL
	tristate "AMD Address Translation Library"
	depends on AMD_NB && X86_64 && RAS
	depends on AMD_NODE
	depends on MEMORY_FAILURE
	help
	  This library includes support for implementation-specific
	  address translation procedures needed for various error
	  handling cases.

	  Enable this option if using DRAM ECC on Zen-based systems
	  and OS-based error handling.

config AMD_ATL_PRM
	depends on AMD_ATL && ACPI_PRMT
	def_bool y

Annotation

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