drivers/platform/x86/intel/speed_select_if/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/platform/x86/intel/speed_select_if/Kconfig
Extension: [no extension]
Size: 803 bytes
Lines: 22
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

menu "Intel Speed Select Technology interface support"
	depends on PCI
	depends on X86_64 || COMPILE_TEST

config INTEL_SPEED_SELECT_TPMI
	tristate

config INTEL_SPEED_SELECT_INTERFACE
	tristate "Intel(R) Speed Select Technology interface drivers"
	select INTEL_SPEED_SELECT_TPMI if INTEL_TPMI
	help
	  This config enables the Intel(R) Speed Select Technology interface
	  drivers. The Intel(R) speed select technology features are non
	  architectural and only supported on specific Xeon(R) servers.
	  These drivers provide interface to directly communicate with hardware
	  via MMIO and Mail boxes to enumerate and control all the speed select
	  features.

	  Enable this config, if there is a need to enable and control the
	  Intel(R) Speed Select Technology features from the user space.
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.