drivers/platform/x86/amd/hfi/Kconfig
Source file repositories/reference/linux-study-clean/drivers/platform/x86/amd/hfi/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/platform/x86/amd/hfi/Kconfig- Extension
[no extension]- Size
- 709 bytes
- Lines
- 19
- Domain
- Driver Families
- Bucket
- drivers/platform
- 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
#
# AMD Hardware Feedback Interface Driver
#
config AMD_HFI
bool "AMD Hetero Core Hardware Feedback Driver"
depends on ACPI
depends on CPU_SUP_AMD
depends on SCHED_MC_PRIO
help
Select this option to enable the AMD Heterogeneous Core Hardware
Feedback Interface. If selected, hardware provides runtime thread
classification guidance to the operating system on the performance and
energy efficiency capabilities of each heterogeneous CPU core. These
capabilities may vary due to the inherent differences in the core types
and can also change as a result of variations in the operating
conditions of the system such as power and thermal limits.
Annotation
- Atlas domain: Driver Families / drivers/platform.
- 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.