drivers/platform/x86/intel/uncore-frequency/Kconfig

Source file repositories/reference/linux-study-clean/drivers/platform/x86/intel/uncore-frequency/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/platform/x86/intel/uncore-frequency/Kconfig
Extension: [no extension]
Size: 637 bytes
Lines: 26
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
#
# Uncore Frquency control drivers
#

menu "Intel Uncore Frequency Control"
	depends on X86_64 || COMPILE_TEST

config INTEL_UNCORE_FREQ_CONTROL_TPMI
	tristate

config INTEL_UNCORE_FREQ_CONTROL
	tristate "Intel Uncore frequency control driver"
	depends on X86_64
	select INTEL_UNCORE_FREQ_CONTROL_TPMI if INTEL_TPMI
	help
	  This driver allows control of Uncore frequency limits on
	  supported server platforms.

	  Uncore frequency controls RING/LLC (last-level cache) clocks.

	  To compile this driver as a module, choose M here: the module
	  will be called intel-uncore-frequency.

endmenu

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.