drivers/platform/x86/amd/pmf/Kconfig

Source file repositories/reference/linux-study-clean/drivers/platform/x86/amd/pmf/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/platform/x86/amd/pmf/Kconfig
Extension: [no extension]
Size: 1016 bytes
Lines: 33
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 PMF Driver
#

config AMD_PMF
	tristate "AMD Platform Management Framework"
	depends on ACPI && PCI
	depends on POWER_SUPPLY
	depends on AMD_NODE
	select ACPI_PLATFORM_PROFILE
	depends on TEE && AMDTEE
	depends on AMD_SFH_HID
	depends on HAS_IOMEM
	help
	  This driver provides support for the AMD Platform Management Framework.
	  The goal is to enhance end user experience by making AMD PCs smarter,
	  quiter, power efficient by adapting to user behavior and environment.

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

config AMD_PMF_DEBUG
	bool "PMF debug information"
	depends on AMD_PMF
	help
	 Enabling this option would give more debug information on the OEM fed
	 power setting values for each of the PMF feature. PMF driver gets this
	 information after evaluating a ACPI method and the information is stored
	 in the PMF config store.

	 Say Y here to enable more debug logs and Say N here if you are not sure.

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.