[linux-2.6-block.git] / drivers / powercap / Kconfig

# SPDX-License-Identifier: GPL-2.0-only
#
# Generic power capping sysfs interface configuration
#

menuconfig POWERCAP
	bool "Generic powercap sysfs driver"
	help
	  The power capping sysfs interface allows kernel subsystems to expose power
	  capping settings to user space in a consistent way.  Usually, it consists
	  of multiple control types that determine which settings may be exposed and
	  power zones representing parts of the system that can be subject to power
	  capping.

	  If you want this code to be compiled in, say Y here.

if POWERCAP
# Client driver configurations go here.
config INTEL_RAPL_CORE
	tristate

config INTEL_RAPL
	tristate "Intel RAPL Support via MSR Interface"
	depends on X86 && IOSF_MBI
	select INTEL_RAPL_CORE
	help
	  This enables support for the Intel Running Average Power Limit (RAPL)
	  technology via MSR interface, which allows power limits to be enforced
	  and monitored on modern Intel processors (Sandy Bridge and later).

	  In RAPL, the platform level settings are divided into domains for
	  fine grained control. These domains include processor package, DRAM
	  controller, CPU core (Power Plane 0), graphics uncore (Power Plane
	  1), etc.

config IDLE_INJECT
	bool "Idle injection framework"
	depends on CPU_IDLE
	default n
	help
	  This enables support for the idle injection framework. It
	  provides a way to force idle periods on a set of specified
	  CPUs for power capping. Idle period can be injected
	  synchronously on a set of specified CPUs or alternatively
	  on a per CPU basis.

config DTPM
	bool "Power capping for Dynamic Thermal Power Management"
	help
	  This enables support for the power capping for the dynamic
	  thermal power management userspace engine.
endif
Commit	Line	Data
ec8f24b7	1	# SPDX-License-Identifier: GPL-2.0-only
75d2364e SP	2	#
	3	# Generic power capping sysfs interface configuration
	4	#
	5
	6	menuconfig POWERCAP
	7	bool "Generic powercap sysfs driver"
	8	help
	9	The power capping sysfs interface allows kernel subsystems to expose power
	10	capping settings to user space in a consistent way. Usually, it consists
	11	of multiple control types that determine which settings may be exposed and
	12	power zones representing parts of the system that can be subject to power
	13	capping.
	14
	15	If you want this code to be compiled in, say Y here.
	16
	17	if POWERCAP
	18	# Client driver configurations go here.
3382388d ZR	19	config INTEL_RAPL_CORE
	20	tristate
	21
2d281d81	22	config INTEL_RAPL
3382388d	23	tristate "Intel RAPL Support via MSR Interface"
24b59841	24	depends on X86 && IOSF_MBI
3382388d	25	select INTEL_RAPL_CORE
a7f7f624	26	help
2d281d81	27	This enables support for the Intel Running Average Power Limit (RAPL)
3382388d ZR	28	technology via MSR interface, which allows power limits to be enforced
3382388d ZR	29	and monitored on modern Intel processors (Sandy Bridge and later).
2d281d81 JP	30
	31	In RAPL, the platform level settings are divided into domains for
	32	fine grained control. These domains include processor package, DRAM
f8fee6e6	33	controller, CPU core (Power Plane 0), graphics uncore (Power Plane
2d281d81	34	1), etc.
75d2364e	35
88763a5c DL	36	config IDLE_INJECT
	37	bool "Idle injection framework"
	38	depends on CPU_IDLE
	39	default n
	40	help
	41	This enables support for the idle injection framework. It
	42	provides a way to force idle periods on a set of specified
	43	CPUs for power capping. Idle period can be injected
	44	synchronously on a set of specified CPUs or alternatively
	45	on a per CPU basis.
a20d0ef9 DL	46
	47	config DTPM
	48	bool "Power capping for Dynamic Thermal Power Management"
	49	help
	50	This enables support for the power capping for the dynamic
	51	thermal power management userspace engine.
75d2364e	52	endif