[linux-block.git] / drivers / thermal / Kconfig

# SPDX-License-Identifier: GPL-2.0-only
#
# Generic thermal drivers configuration
#

menuconfig THERMAL
	bool "Thermal drivers"
	help
	  Thermal drivers offer a generic mechanism for
	  thermal management. Usually it's made up of one or more thermal
	  zones and cooling devices.
	  Each thermal zone contains its own temperature, trip points,
	  and cooling devices.
	  All platforms with ACPI or Open Firmware thermal support can use
	  this driver.
	  If you want this support, you should say Y here.

if THERMAL

config THERMAL_NETLINK
	bool "Thermal netlink management"
	depends on NET
	help
	  The thermal framework has a netlink interface to do thermal
	  zones discovery, temperature readings and events such as
	  trip point crossed, cooling device update or governor
	  change. It is recommended to enable the feature.

config THERMAL_STATISTICS
	bool "Thermal state transition statistics"
	help
	  Export thermal state transition statistics information through sysfs.

	  If in doubt, say N.

config THERMAL_DEBUGFS
	bool "Thermal subsystem debug support"
	depends on DEBUG_FS
	help
	  Say Y to allow the thermal subsystem to collect diagnostic
	  information that can be accessed via debugfs.

config THERMAL_CORE_TESTING
	tristate "Thermal core testing facility"
	depends on DEBUG_FS
	help
	  Say Y to add a debugfs-based thermal core testing facility.
	  It allows test thermal zones to be created and populated
	  with trip points in order to exercise the thermal core
	  functionality in a controlled way.

config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
	int "Emergency poweroff delay in milli-seconds"
	default 0
	help
	  Thermal subsystem will issue a graceful shutdown when
	  critical temperatures are reached using orderly_poweroff(). In
	  case of failure of an orderly_poweroff(), the thermal emergency
	  poweroff kicks in after a delay has elapsed and shuts down the system.
	  This config is number of milliseconds to delay before emergency
	  poweroff kicks in. Similarly to the critical trip point,
	  the delay should be carefully profiled so as to give adequate
	  time for orderly_poweroff() to finish on regular execution.
	  If set to 0 emergency poweroff will not be supported.

	  In doubt, leave as 0.

config THERMAL_HWMON
	bool
	prompt "Expose thermal sensors as hwmon device"
	depends on HWMON=y || HWMON=THERMAL
	default y
	help
	  In case a sensor is registered with the thermal
	  framework, this option will also register it
	  as a hwmon. The sensor will then have the common
	  hwmon sysfs interface.

	  Say 'Y' here if you want all thermal sensors to
	  have hwmon sysfs interface too.

config THERMAL_OF
	bool
	prompt "APIs to parse thermal data out of device tree"
	depends on OF
	default y
	help
	  This options provides helpers to add the support to
	  read and parse thermal data definitions out of the
	  device tree blob.

	  Say 'Y' here if you need to build thermal infrastructure
	  based on device tree.

choice
	prompt "Default Thermal governor"
	default THERMAL_DEFAULT_GOV_STEP_WISE
	help
	  This option sets which thermal governor shall be loaded at
	  startup. If in doubt, select 'step_wise'.

config THERMAL_DEFAULT_GOV_STEP_WISE
	bool "step_wise"
	select THERMAL_GOV_STEP_WISE
	help
	  Use the step_wise governor as default. This throttles the
	  devices one step at a time.

config THERMAL_DEFAULT_GOV_FAIR_SHARE
	bool "fair_share"
	select THERMAL_GOV_FAIR_SHARE
	help
	  Use the fair_share governor as default. This throttles the
	  devices based on their 'contribution' to a zone. The
	  contribution should be provided through platform data.

config THERMAL_DEFAULT_GOV_USER_SPACE
	bool "user_space"
	select THERMAL_GOV_USER_SPACE
	help
	  The Userspace governor allows to get trip point crossed
	  notification from the kernel via uevents. It is recommended
	  to use the netlink interface instead which gives richer
	  information about the thermal framework events.

config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
	bool "power_allocator"
	depends on THERMAL_GOV_POWER_ALLOCATOR
	help
	  Select this if you want to control temperature based on
	  system and device power allocation. This governor can only
	  operate on cooling devices that implement the power API.

config THERMAL_DEFAULT_GOV_BANG_BANG
	bool "bang_bang"
	depends on THERMAL_GOV_BANG_BANG
	help
	  Use the bang_bang governor as default. This throttles the
	  devices one step at the time, taking into account the trip
	  point hysteresis.

endchoice

config THERMAL_GOV_FAIR_SHARE
	bool "Fair-share thermal governor"
	help
	  Enable this to manage platform thermals using fair-share governor.

config THERMAL_GOV_STEP_WISE
	bool "Step_wise thermal governor"
	help
	  Enable this to manage platform thermals using a simple linear
	  governor.

config THERMAL_GOV_BANG_BANG
	bool "Bang Bang thermal governor"
	default n
	help
	  Enable this to manage platform thermals using bang bang governor.

	  Say 'Y' here if you want to use two point temperature regulation
	  used for fans without throttling.  Some fan drivers depend on this
	  governor to be enabled (e.g. acerhdf).

config THERMAL_GOV_USER_SPACE
	bool "User_space thermal governor"
	help
	  Enable this to let the user space manage the platform thermals.

config THERMAL_GOV_POWER_ALLOCATOR
	bool "Power allocator thermal governor"
	depends on ENERGY_MODEL
	help
	  Enable this to manage platform thermals by dynamically
	  allocating and limiting power to devices.

config CPU_THERMAL
	bool "Generic cpu cooling support"
	depends on THERMAL_OF
	help
	  Enable the CPU cooling features. If the system has no active
	  cooling device available, this option allows to use the CPU
	  as a cooling device.

if CPU_THERMAL

config CPU_FREQ_THERMAL
	bool "CPU frequency cooling device"
	depends on CPU_FREQ
	default y
	help
	  This implements the generic cpu cooling mechanism through frequency
	  reduction. An ACPI version of this already exists
	  (drivers/acpi/processor_thermal.c).
	  This will be useful for platforms using the generic thermal interface
	  and not the ACPI interface.

config CPU_IDLE_THERMAL
	bool "CPU idle cooling device"
	depends on IDLE_INJECT
	help
	  This implements the CPU cooling mechanism through
	  idle injection. This will throttle the CPU by injecting
	  idle cycle.
endif

config DEVFREQ_THERMAL
	bool "Generic device cooling support"
	depends on PM_DEVFREQ
	depends on PM_OPP
	help
	  This implements the generic devfreq cooling mechanism through
	  frequency reduction for devices using devfreq.

	  This will throttle the device by limiting the maximum allowed DVFS
	  frequency corresponding to the cooling level.

	  In order to use the power extensions of the cooling device,
	  devfreq should use the simple_ondemand governor.

	  If you want this support, you should say Y here.

config PCIE_THERMAL
	bool "PCIe cooling support"
	depends on PCIEPORTBUS
	help
	  This implements PCIe cooling mechanism through bandwidth reduction
	  for PCIe devices.

	  If you want this support, you should say Y here.

config THERMAL_EMULATION
	bool "Thermal emulation mode support"
	help
	  Enable this option to make a emul_temp sysfs node in thermal zone
	  directory to support temperature emulation. With emulation sysfs node,
	  user can manually input temperature and test the different trip
	  threshold behaviour for simulation purpose.

	  WARNING: Be careful while enabling this option on production systems,
	  because userland can easily disable the thermal policy by simply
	  flooding this sysfs node with low temperature values.

config THERMAL_MMIO
	tristate "Generic Thermal MMIO driver"
	depends on OF
	depends on HAS_IOMEM
	help
	  This option enables the generic thermal MMIO driver that will use
	  memory-mapped reads to get the temperature.  Any HW/System that
	  allows temperature reading by a single memory-mapped reading, be it
	  register or shared memory, is a potential candidate to work with this
	  driver.

config HISI_THERMAL
	tristate "Hisilicon thermal driver"
	depends on ARCH_HISI || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	default ARCH_HISI
	help
	  Enable this to plug hisilicon's thermal sensor driver into the Linux
	  thermal framework. cpufreq is used as the cooling device to throttle
	  CPUs when the passive trip is crossed.

config IMX_THERMAL
	tristate "Temperature sensor driver for Freescale i.MX SoCs"
	depends on ARCH_MXC || COMPILE_TEST
	depends on NVMEM || !NVMEM
	depends on MFD_SYSCON
	depends on OF
	help
	  Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
	  It supports one critical trip point and one passive trip point.  The
	  cpufreq is used as the cooling device to throttle CPUs when the
	  passive trip is crossed.

config IMX_SC_THERMAL
	tristate "Temperature sensor driver for NXP i.MX SoCs with System Controller"
	depends on IMX_SCU
	depends on OF
	help
	  Support for Temperature Monitor (TEMPMON) found on NXP i.MX SoCs with
	  system controller inside, Linux kernel has to communicate with system
	  controller via MU (message unit) IPC to get temperature from thermal
	  sensor. It supports one critical trip point and one
	  passive trip point for each thermal sensor.

config IMX8MM_THERMAL
	tristate "Temperature sensor driver for Freescale i.MX8MM SoC"
	depends on ARCH_MXC || COMPILE_TEST
	depends on OF
	help
	  Support for Thermal Monitoring Unit (TMU) found on Freescale i.MX8MM SoC.
	  It supports one critical trip point and one passive trip point. The
	  cpufreq is used as the cooling device to throttle CPUs when the passive
	  trip is crossed.

config K3_THERMAL
	tristate "Texas Instruments K3 thermal support"
	depends on ARCH_K3 || COMPILE_TEST
	help
	  If you say yes here you get thermal support for the Texas Instruments
	  K3 SoC family. The current chip supported is:
	  - AM654

	  This includes temperature reading functionality.

config MAX77620_THERMAL
	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
	depends on MFD_MAX77620
	depends on OF
	help
	  Support for die junction temperature warning alarm for Maxim
	  Semiconductor PMIC MAX77620 device. Device generates two alarm
	  interrupts when PMIC die temperature cross the threshold of
	  120 degC and 140 degC.

config QORIQ_THERMAL
	tristate "QorIQ Thermal Monitoring Unit"
	depends on THERMAL_OF && HAS_IOMEM
	depends on PPC_E500MC || SOC_LS1021A || ARCH_LAYERSCAPE || (ARCH_MXC && ARM64) || COMPILE_TEST
	select REGMAP_MMIO
	help
	  Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
	  It supports one critical trip point and one passive trip point. The
	  cpufreq is used as the cooling device to throttle CPUs when the
	  passive trip is crossed.

config AIROHA_THERMAL
	tristate "Airoha thermal sensor driver"
	depends on ARCH_AIROHA || COMPILE_TEST
	depends on MFD_SYSCON
	depends on OF
	help
	  Enable this to plug the Airoha thermal sensor driver into the Linux
	  thermal framework.

config SPEAR_THERMAL
	tristate "SPEAr thermal sensor driver"
	depends on PLAT_SPEAR || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Enable this to plug the SPEAr thermal sensor driver into the Linux
	  thermal framework.

config SUN8I_THERMAL
	tristate "Allwinner sun8i thermal driver"
	depends on ARCH_SUNXI || COMPILE_TEST
	depends on HAS_IOMEM
	depends on NVMEM
	depends on OF
	depends on RESET_CONTROLLER
	help
	  Support for the sun8i thermal sensor driver into the Linux thermal
	  framework.

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

config ROCKCHIP_THERMAL
	tristate "Rockchip thermal driver"
	depends on ARCH_ROCKCHIP || COMPILE_TEST
	depends on RESET_CONTROLLER
	depends on HAS_IOMEM
	help
	  Rockchip thermal driver provides support for Temperature sensor
	  ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
	  trip point. Cpufreq is used as the cooling device and will throttle
	  CPUs when the Temperature crosses the passive trip point.

config KIRKWOOD_THERMAL
	tristate "Temperature sensor on Marvell Kirkwood SoCs"
	depends on MACH_KIRKWOOD || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Support for the Kirkwood thermal sensor driver into the Linux thermal
	  framework. Only kirkwood 88F6282 and 88F6283 have this sensor.

config DOVE_THERMAL
	tristate "Temperature sensor on Marvell Dove SoCs"
	depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Support for the Dove thermal sensor driver in the Linux thermal
	  framework.

config DB8500_THERMAL
	tristate "DB8500 thermal management"
	depends on MFD_DB8500_PRCMU && OF
	default y
	help
	  Adds DB8500 thermal management implementation according to the thermal
	  management framework. A thermal zone with several trip points will be
	  created. Cooling devices can be bound to the trip points to cool this
	  thermal zone if trip points reached.

config ARMADA_THERMAL
	tristate "Marvell EBU Armada SoCs thermal management"
	depends on ARCH_MVEBU || COMPILE_TEST
	depends on HAS_IOMEM
	depends on OF
	help
	  Enable this option if you want to have support for thermal management
	  controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).

config DA9062_THERMAL
	tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
	depends on MFD_DA9062 || COMPILE_TEST
	depends on OF
	help
	  Enable this for the Dialog Semiconductor thermal sensor driver.
	  This will report PMIC junction over-temperature for one thermal trip
	  zone.
	  Compatible with the DA9062 and DA9061 PMICs.

menu "Mediatek thermal drivers"
depends on ARCH_MEDIATEK || COMPILE_TEST
source "drivers/thermal/mediatek/Kconfig"
endmenu

config AMLOGIC_THERMAL
	tristate "Amlogic Thermal Support"
	default ARCH_MESON
	depends on OF && ARCH_MESON
	help
	  If you say yes here you get support for Amlogic Thermal
	  for G12 SoC Family.

	  This driver can also be built as a module. If so, the module will
	  be called amlogic_thermal.

menu "Intel thermal drivers"
depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
source "drivers/thermal/intel/Kconfig"
endmenu

menu "Broadcom thermal drivers"
depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
		COMPILE_TEST
source "drivers/thermal/broadcom/Kconfig"
endmenu

menu "Texas Instruments thermal drivers"
depends on ARCH_HAS_BANDGAP || COMPILE_TEST
depends on HAS_IOMEM
source "drivers/thermal/ti-soc-thermal/Kconfig"
endmenu

menu "Samsung thermal drivers"
depends on ARCH_EXYNOS || COMPILE_TEST
source "drivers/thermal/samsung/Kconfig"
endmenu

menu "STMicroelectronics thermal drivers"
depends on (ARCH_STI || ARCH_STM32) && THERMAL_OF
source "drivers/thermal/st/Kconfig"
endmenu

source "drivers/thermal/renesas/Kconfig"

source "drivers/thermal/tegra/Kconfig"

config GENERIC_ADC_THERMAL
	tristate "Generic ADC based thermal sensor"
	depends on IIO
	help
	  This enabled a thermal sysfs driver for the temperature sensor
	  which is connected to the General Purpose ADC. The ADC channel
	  is read via IIO framework and the channel information is provided
	  to this driver. This driver reports the temperature by reading ADC
	  channel and converts it to temperature based on lookup table.

menu "Qualcomm thermal drivers"
depends on (ARCH_QCOM && OF) || COMPILE_TEST
source "drivers/thermal/qcom/Kconfig"
endmenu

config UNIPHIER_THERMAL
	tristate "Socionext UniPhier thermal driver"
	depends on ARCH_UNIPHIER || COMPILE_TEST
	depends on THERMAL_OF && MFD_SYSCON
	help
	  Enable this to plug in UniPhier on-chip PVT thermal driver into the
	  thermal framework. The driver supports CPU thermal zone temperature
	  reporting and a couple of trip points.

config SPRD_THERMAL
	tristate "Temperature sensor on Spreadtrum SoCs"
	depends on ARCH_SPRD || COMPILE_TEST
	help
	  Support for the Spreadtrum thermal sensor driver in the Linux thermal
	  framework.

config KHADAS_MCU_FAN_THERMAL
	tristate "Khadas MCU controller FAN cooling support"
	depends on OF
	depends on MFD_KHADAS_MCU
	select MFD_CORE
	select REGMAP
	help
	  If you say yes here you get support for the FAN controlled
	  by the Microcontroller found on the Khadas VIM boards.

config LOONGSON2_THERMAL
	tristate "Loongson-2 SoC series thermal driver"
	depends on LOONGARCH || COMPILE_TEST
	depends on OF
	help
	  Support for Thermal driver found on Loongson-2 SoC series platforms.
	  The thermal driver realizes get_temp and set_trips function, which
	  are used to obtain the temperature of the current node and set the
	  temperature range to trigger the interrupt. When the input temperature
	  is higher than the high temperature threshold or lower than the low
	  temperature threshold, the interrupt will occur.

endif
Commit	Line	Data
ec8f24b7	1	# SPDX-License-Identifier: GPL-2.0-only
203d3d4a	2	#
eb850462	3	# Generic thermal drivers configuration
203d3d4a ZR	4	#
	5
	6	menuconfig THERMAL
eb850462	7	bool "Thermal drivers"
203d3d4a	8	help
eb850462	9	Thermal drivers offer a generic mechanism for
203d3d4a	10	thermal management. Usually it's made up of one or more thermal
eb850462	11	zones and cooling devices.
543a9561	12	Each thermal zone contains its own temperature, trip points,
eb850462 LW	13	and cooling devices.
	14	All platforms with ACPI or Open Firmware thermal support can use
	15	this driver.
554b3529	16	If you want this support, you should say Y here.
16d75239	17
72e19897 ZR	18	if THERMAL
72e19897 ZR	19
5b8583d3 DL	20	config THERMAL_NETLINK
	21	bool "Thermal netlink management"
	22	depends on NET
5b8583d3 DL	23	help
	24	The thermal framework has a netlink interface to do thermal
	25	zones discovery, temperature readings and events such as
	26	trip point crossed, cooling device update or governor
	27	change. It is recommended to enable the feature.
	28
8ea22951 VK	29	config THERMAL_STATISTICS
	30	bool "Thermal state transition statistics"
	31	help
	32	Export thermal state transition statistics information through sysfs.
	33
	34	If in doubt, say N.
	35
755113d7 DL	36	config THERMAL_DEBUGFS
	37	bool "Thermal subsystem debug support"
	38	depends on DEBUG_FS
	39	help
	40	Say Y to allow the thermal subsystem to collect diagnostic
	41	information that can be accessed via debugfs.
	42
f6a034f2 RW	43	config THERMAL_CORE_TESTING
	44	tristate "Thermal core testing facility"
	45	depends on DEBUG_FS
	46	help
	47	Say Y to add a debugfs-based thermal core testing facility.
	48	It allows test thermal zones to be created and populated
	49	with trip points in order to exercise the thermal core
	50	functionality in a controlled way.
	51
ef1d87e0 K	52	config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
ef1d87e0 K	53	int "Emergency poweroff delay in milli-seconds"
ef1d87e0 K	54	default 0
	55	help
	56	Thermal subsystem will issue a graceful shutdown when
	57	critical temperatures are reached using orderly_poweroff(). In
	58	case of failure of an orderly_poweroff(), the thermal emergency
	59	poweroff kicks in after a delay has elapsed and shuts down the system.
	60	This config is number of milliseconds to delay before emergency
	61	poweroff kicks in. Similarly to the critical trip point,
	62	the delay should be carefully profiled so as to give adequate
	63	time for orderly_poweroff() to finish on regular execution.
	64	If set to 0 emergency poweroff will not be supported.
	65
	66	In doubt, leave as 0.
	67
16d75239	68	config THERMAL_HWMON
ab92402a	69	bool
0dd88793	70	prompt "Expose thermal sensors as hwmon device"
16d75239	71	depends on HWMON=y \|\| HWMON=THERMAL
ab92402a	72	default y
0dd88793 EV	73	help
	74	In case a sensor is registered with the thermal
	75	framework, this option will also register it
	76	as a hwmon. The sensor will then have the common
	77	hwmon sysfs interface.
	78
	79	Say 'Y' here if you want all thermal sensors to
	80	have hwmon sysfs interface too.
6a92c366	81
4e5e4705 EV	82	config THERMAL_OF
	83	bool
	84	prompt "APIs to parse thermal data out of device tree"
	85	depends on OF
	86	default y
	87	help
	88	This options provides helpers to add the support to
	89	read and parse thermal data definitions out of the
	90	device tree blob.
	91
	92	Say 'Y' here if you need to build thermal infrastructure
	93	based on device tree.
	94
72e19897 ZR	95	choice
	96	prompt "Default Thermal governor"
	97	default THERMAL_DEFAULT_GOV_STEP_WISE
	98	help
	99	This option sets which thermal governor shall be loaded at
	100	startup. If in doubt, select 'step_wise'.
	101
	102	config THERMAL_DEFAULT_GOV_STEP_WISE
	103	bool "step_wise"
9d185d04	104	select THERMAL_GOV_STEP_WISE
72e19897 ZR	105	help
	106	Use the step_wise governor as default. This throttles the
	107	devices one step at a time.
	108
	109	config THERMAL_DEFAULT_GOV_FAIR_SHARE
	110	bool "fair_share"
9d185d04	111	select THERMAL_GOV_FAIR_SHARE
72e19897 ZR	112	help
	113	Use the fair_share governor as default. This throttles the
	114	devices based on their 'contribution' to a zone. The
	115	contribution should be provided through platform data.
	116
	117	config THERMAL_DEFAULT_GOV_USER_SPACE
	118	bool "user_space"
9d185d04	119	select THERMAL_GOV_USER_SPACE
72e19897	120	help
fa1ef24a DL	121	The Userspace governor allows to get trip point crossed
	122	notification from the kernel via uevents. It is recommended
	123	to use the netlink interface instead which gives richer
	124	information about the thermal framework events.
72e19897	125
6b775e87 JM	126	config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
6b775e87 JM	127	bool "power_allocator"
50260614	128	depends on THERMAL_GOV_POWER_ALLOCATOR
6b775e87 JM	129	help
	130	Select this if you want to control temperature based on
	131	system and device power allocation. This governor can only
	132	operate on cooling devices that implement the power API.
	133
04bf1fe4 TR	134	config THERMAL_DEFAULT_GOV_BANG_BANG
	135	bool "bang_bang"
	136	depends on THERMAL_GOV_BANG_BANG
	137	help
	138	Use the bang_bang governor as default. This throttles the
	139	devices one step at the time, taking into account the trip
	140	point hysteresis.
	141
72e19897 ZR	142	endchoice
72e19897 ZR	143
9d185d04	144	config THERMAL_GOV_FAIR_SHARE
72e19897 ZR	145	bool "Fair-share thermal governor"
	146	help
	147	Enable this to manage platform thermals using fair-share governor.
	148
9d185d04	149	config THERMAL_GOV_STEP_WISE
72e19897 ZR	150	bool "Step_wise thermal governor"
	151	help
	152	Enable this to manage platform thermals using a simple linear
a8227948	153	governor.
72e19897	154
e4dbf98f PF	155	config THERMAL_GOV_BANG_BANG
	156	bool "Bang Bang thermal governor"
	157	default n
	158	help
	159	Enable this to manage platform thermals using bang bang governor.
	160
	161	Say 'Y' here if you want to use two point temperature regulation
	162	used for fans without throttling. Some fan drivers depend on this
	163	governor to be enabled (e.g. acerhdf).
	164
9d185d04	165	config THERMAL_GOV_USER_SPACE
72e19897 ZR	166	bool "User_space thermal governor"
	167	help
	168	Enable this to let the user space manage the platform thermals.
	169
6b775e87 JM	170	config THERMAL_GOV_POWER_ALLOCATOR
6b775e87 JM	171	bool "Power allocator thermal governor"
a4e893e8	172	depends on ENERGY_MODEL
6b775e87 JM	173	help
	174	Enable this to manage platform thermals by dynamically
	175	allocating and limiting power to devices.
	176
02361418	177	config CPU_THERMAL
2e31c856	178	bool "Generic cpu cooling support"
39d99cff	179	depends on THERMAL_OF
2b586fea DL	180	help
	181	Enable the CPU cooling features. If the system has no active
	182	cooling device available, this option allows to use the CPU
	183	as a cooling device.
	184
	185	if CPU_THERMAL
	186
	187	config CPU_FREQ_THERMAL
	188	bool "CPU frequency cooling device"
	189	depends on CPU_FREQ
	190	default y
02361418 ADK	191	help
02361418 ADK	192	This implements the generic cpu cooling mechanism through frequency
f7188b3d EV	193	reduction. An ACPI version of this already exists
f7188b3d EV	194	(drivers/acpi/processor_thermal.c).
02361418 ADK	195	This will be useful for platforms using the generic thermal interface
02361418 ADK	196	and not the ACPI interface.
f7188b3d	197
a4c428e5 DL	198	config CPU_IDLE_THERMAL
	199	bool "CPU idle cooling device"
	200	depends on IDLE_INJECT
	201	help
	202	This implements the CPU cooling mechanism through
	203	idle injection. This will throttle the CPU by injecting
	204	idle cycle.
2b586fea	205	endif
02361418	206
a76caf55 ØE	207	config DEVFREQ_THERMAL
	208	bool "Generic device cooling support"
	209	depends on PM_DEVFREQ
	210	depends on PM_OPP
	211	help
	212	This implements the generic devfreq cooling mechanism through
	213	frequency reduction for devices using devfreq.
	214
	215	This will throttle the device by limiting the maximum allowed DVFS
	216	frequency corresponding to the cooling level.
	217
	218	In order to use the power extensions of the cooling device,
	219	devfreq should use the simple_ondemand governor.
	220
f9df89d8 EV	221	If you want this support, you should say Y here.
f9df89d8 EV	222
d278b098 IJ	223	config PCIE_THERMAL
	224	bool "PCIe cooling support"
	225	depends on PCIEPORTBUS
	226	help
	227	This implements PCIe cooling mechanism through bandwidth reduction
	228	for PCIe devices.
	229
	230	If you want this support, you should say Y here.
	231
e6e238c3 ADK	232	config THERMAL_EMULATION
	233	bool "Thermal emulation mode support"
	234	help
	235	Enable this option to make a emul_temp sysfs node in thermal zone
	236	directory to support temperature emulation. With emulation sysfs node,
	237	user can manually input temperature and test the different trip
	238	threshold behaviour for simulation purpose.
	239
8837295a EV	240	WARNING: Be careful while enabling this option on production systems,
	241	because userland can easily disable the thermal policy by simply
	242	flooding this sysfs node with low temperature values.
	243
71aa3693 TS	244	config THERMAL_MMIO
71aa3693 TS	245	tristate "Generic Thermal MMIO driver"
8df4ef3e	246	depends on OF
6ec8070b	247	depends on HAS_IOMEM
71aa3693 TS	248	help
	249	This option enables the generic thermal MMIO driver that will use
	250	memory-mapped reads to get the temperature. Any HW/System that
	251	allows temperature reading by a single memory-mapped reading, be it
	252	register or shared memory, is a potential candidate to work with this
	253	driver.
	254
9a5238a9	255	config HISI_THERMAL
9a5238a9	256	tristate "Hisilicon thermal driver"
f05f4821	257	depends on ARCH_HISI \|\| COMPILE_TEST
bf82c350	258	depends on HAS_IOMEM
f05f4821	259	depends on OF
5f9ab5df	260	default ARCH_HISI
9a5238a9	261	help
	262	Enable this to plug hisilicon's thermal sensor driver into the Linux
	263	thermal framework. cpufreq is used as the cooling device to throttle
	264	CPUs when the passive trip is crossed.
	265
ca3de46b SG	266	config IMX_THERMAL
ca3de46b SG	267	tristate "Temperature sensor driver for Freescale i.MX SoCs"
c589c566	268	depends on ARCH_MXC \|\| COMPILE_TEST
531fcdeb	269	depends on NVMEM \|\| !NVMEM
ca3de46b SG	270	depends on MFD_SYSCON
	271	depends on OF
	272	help
	273	Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
	274	It supports one critical trip point and one passive trip point. The
	275	cpufreq is used as the cooling device to throttle CPUs when the
	276	passive trip is crossed.
	277
e20db70d AH	278	config IMX_SC_THERMAL
e20db70d AH	279	tristate "Temperature sensor driver for NXP i.MX SoCs with System Controller"
ef502fc1	280	depends on IMX_SCU
e20db70d AH	281	depends on OF
	282	help
	283	Support for Temperature Monitor (TEMPMON) found on NXP i.MX SoCs with
	284	system controller inside, Linux kernel has to communicate with system
	285	controller via MU (message unit) IPC to get temperature from thermal
	286	sensor. It supports one critical trip point and one
	287	passive trip point for each thermal sensor.
	288
5eed800a AH	289	config IMX8MM_THERMAL
5eed800a AH	290	tristate "Temperature sensor driver for Freescale i.MX8MM SoC"
52cbc58b	291	depends on ARCH_MXC \|\| COMPILE_TEST
5eed800a AH	292	depends on OF
	293	help
	294	Support for Thermal Monitoring Unit (TMU) found on Freescale i.MX8MM SoC.
	295	It supports one critical trip point and one passive trip point. The
	296	cpufreq is used as the cooling device to throttle CPUs when the passive
	297	trip is crossed.
	298
48b2bce8 K	299	config K3_THERMAL
	300	tristate "Texas Instruments K3 thermal support"
	301	depends on ARCH_K3 \|\| COMPILE_TEST
	302	help
	303	If you say yes here you get thermal support for the Texas Instruments
	304	K3 SoC family. The current chip supported is:
	305	- AM654
	306
	307	This includes temperature reading functionality.
	308
ec4664b3 LD	309	config MAX77620_THERMAL
	310	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
	311	depends on MFD_MAX77620
	312	depends on OF
	313	help
	314	Support for die junction temperature warning alarm for Maxim
	315	Semiconductor PMIC MAX77620 device. Device generates two alarm
	316	interrupts when PMIC die temperature cross the threshold of
	317	120 degC and 140 degC.
	318
43528445 JH	319	config QORIQ_THERMAL
43528445 JH	320	tristate "QorIQ Thermal Monitoring Unit"
1ab20c0e GU	321	depends on THERMAL_OF && HAS_IOMEM
1ab20c0e GU	322	depends on PPC_E500MC \|\| SOC_LS1021A \|\| ARCH_LAYERSCAPE \|\| (ARCH_MXC && ARM64) \|\| COMPILE_TEST
cbe259fd	323	select REGMAP_MMIO
43528445 JH	324	help
	325	Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
	326	It supports one critical trip point and one passive trip point. The
	327	cpufreq is used as the cooling device to throttle CPUs when the
	328	passive trip is crossed.
	329
42de37f4 CM	330	config AIROHA_THERMAL
	331	tristate "Airoha thermal sensor driver"
	332	depends on ARCH_AIROHA \|\| COMPILE_TEST
	333	depends on MFD_SYSCON
	334	depends on OF
	335	help
	336	Enable this to plug the Airoha thermal sensor driver into the Linux
	337	thermal framework.
	338
6a92c366	339	config SPEAR_THERMAL
4d2f1794	340	tristate "SPEAr thermal sensor driver"
aa2937b7	341	depends on PLAT_SPEAR \|\| COMPILE_TEST
bf82c350	342	depends on HAS_IOMEM
b9c7aff4	343	depends on OF
6a92c366 VF	344	help
6a92c366 VF	345	Enable this to plug the SPEAr thermal sensor driver into the Linux
a8227948	346	thermal framework.
1e426ffd	347
dccc5c3b YL	348	config SUN8I_THERMAL
	349	tristate "Allwinner sun8i thermal driver"
	350	depends on ARCH_SUNXI \|\| COMPILE_TEST
	351	depends on HAS_IOMEM
	352	depends on NVMEM
	353	depends on OF
	354	depends on RESET_CONTROLLER
	355	help
	356	Support for the sun8i thermal sensor driver into the Linux thermal
	357	framework.
	358
	359	To compile this driver as a module, choose M here: the
	360	module will be called sun8i-thermal.
	361
cbac8f63 CW	362	config ROCKCHIP_THERMAL
cbac8f63 CW	363	tristate "Rockchip thermal driver"
444f9b00	364	depends on ARCH_ROCKCHIP \|\| COMPILE_TEST
cbac8f63	365	depends on RESET_CONTROLLER
bf82c350	366	depends on HAS_IOMEM
cbac8f63 CW	367	help
	368	Rockchip thermal driver provides support for Temperature sensor
	369	ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
	370	trip point. Cpufreq is used as the cooling device and will throttle
	371	CPUs when the Temperature crosses the passive trip point.
	372
7060aa36 NI	373	config KIRKWOOD_THERMAL
7060aa36 NI	374	tristate "Temperature sensor on Marvell Kirkwood SoCs"
9c8aa959	375	depends on MACH_KIRKWOOD \|\| COMPILE_TEST
bf82c350	376	depends on HAS_IOMEM
7060aa36 NI	377	depends on OF
	378	help
	379	Support for the Kirkwood thermal sensor driver into the Linux thermal
	380	framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
	381
74ffa64c AL	382	config DOVE_THERMAL
74ffa64c AL	383	tristate "Temperature sensor on Marvell Dove SoCs"
07fffd5c	384	depends on ARCH_DOVE \|\| MACH_DOVE \|\| COMPILE_TEST
bf82c350	385	depends on HAS_IOMEM
74ffa64c AL	386	depends on OF
	387	help
	388	Support for the Dove thermal sensor driver in the Linux thermal
	389	framework.
	390
aa1acb04	391	config DB8500_THERMAL
26716ce1	392	tristate "DB8500 thermal management"
cb063a83	393	depends on MFD_DB8500_PRCMU && OF
aa1acb04	394	default y
	395	help
	396	Adds DB8500 thermal management implementation according to the thermal
	397	management framework. A thermal zone with several trip points will be
	398	created. Cooling devices can be bound to the trip points to cool this
	399	thermal zone if trip points reached.
	400
fa0d654c	401	config ARMADA_THERMAL
a9d58a1a	402	tristate "Marvell EBU Armada SoCs thermal management"
1b158267	403	depends on ARCH_MVEBU \|\| COMPILE_TEST
bf82c350	404	depends on HAS_IOMEM
fa0d654c EG	405	depends on OF
	406	help
	407	Enable this option if you want to have support for thermal management
a9d58a1a	408	controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
fa0d654c	409
608567aa ST	410	config DA9062_THERMAL
	411	tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
	412	depends on MFD_DA9062 \|\| COMPILE_TEST
	413	depends on OF
	414	help
	415	Enable this for the Dialog Semiconductor thermal sensor driver.
	416	This will report PMIC junction over-temperature for one thermal trip
	417	zone.
	418	Compatible with the DA9062 and DA9061 PMICs.
	419
fad399eb BC	420	menu "Mediatek thermal drivers"
	421	depends on ARCH_MEDIATEK \|\| COMPILE_TEST
	422	source "drivers/thermal/mediatek/Kconfig"
	423	endmenu
a92db1c8	424
421eda10 GLR	425	config AMLOGIC_THERMAL
	426	tristate "Amlogic Thermal Support"
	427	default ARCH_MESON
	428	depends on OF && ARCH_MESON
	429	help
	430	If you say yes here you get support for Amlogic Thermal
	431	for G12 SoC Family.
	432
	433	This driver can also be built as a module. If so, the module will
	434	be called amlogic_thermal.
	435
3e8c4d31 AK	436	menu "Intel thermal drivers"
	437	depends on X86 \|\| X86_INTEL_QUARK \|\| COMPILE_TEST
	438	source "drivers/thermal/intel/Kconfig"
	439	endmenu
	440
a94cb7ee	441	menu "Broadcom thermal drivers"
250e2110 PK	442	depends on ARCH_BCM \|\| ARCH_BRCMSTB \|\| ARCH_BCM2835 \|\| ARCH_BCM_IPROC \|\| \
250e2110 PK	443	COMPILE_TEST
a94cb7ee RM	444	source "drivers/thermal/broadcom/Kconfig"
	445	endmenu
	446
eb982001	447	menu "Texas Instruments thermal drivers"
ec2feb47	448	depends on ARCH_HAS_BANDGAP \|\| COMPILE_TEST
bf82c350	449	depends on HAS_IOMEM
eb982001 EV	450	source "drivers/thermal/ti-soc-thermal/Kconfig"
eb982001 EV	451	endmenu
f157f596	452
c6821378	453	menu "Samsung thermal drivers"
2bf42735	454	depends on ARCH_EXYNOS \|\| COMPILE_TEST
c6821378 ADK	455	source "drivers/thermal/samsung/Kconfig"
	456	endmenu
	457
60aef7ce	458	menu "STMicroelectronics thermal drivers"
8e12f1f8	459	depends on (ARCH_STI \|\| ARCH_STM32) && THERMAL_OF
60aef7ce LJ	460	source "drivers/thermal/st/Kconfig"
	461	endmenu
	462
9d617949 NS	463	source "drivers/thermal/renesas/Kconfig"
9d617949 NS	464
a4dff94f WN	465	source "drivers/thermal/tegra/Kconfig"
a4dff94f WN	466
b3aef78f LD	467	config GENERIC_ADC_THERMAL
	468	tristate "Generic ADC based thermal sensor"
	469	depends on IIO
	470	help
	471	This enabled a thermal sysfs driver for the temperature sensor
	472	which is connected to the General Purpose ADC. The ADC channel
	473	is read via IIO framework and the channel information is provided
	474	to this driver. This driver reports the temperature by reading ADC
	475	channel and converts it to temperature based on lookup table.
	476
9066073c RN	477	menu "Qualcomm thermal drivers"
	478	depends on (ARCH_QCOM && OF) \|\| COMPILE_TEST
	479	source "drivers/thermal/qcom/Kconfig"
	480	endmenu
	481
86da4391 KH	482	config UNIPHIER_THERMAL
	483	tristate "Socionext UniPhier thermal driver"
	484	depends on ARCH_UNIPHIER \|\| COMPILE_TEST
	485	depends on THERMAL_OF && MFD_SYSCON
	486	help
	487	Enable this to plug in UniPhier on-chip PVT thermal driver into the
	488	thermal framework. The driver supports CPU thermal zone temperature
	489	reporting and a couple of trip points.
554fdbaf FL	490
	491	config SPRD_THERMAL
	492	tristate "Temperature sensor on Spreadtrum SoCs"
	493	depends on ARCH_SPRD \|\| COMPILE_TEST
	494	help
	495	Support for the Spreadtrum thermal sensor driver in the Linux thermal
	496	framework.
5772717e NA	497
	498	config KHADAS_MCU_FAN_THERMAL
	499	tristate "Khadas MCU controller FAN cooling support"
8df4ef3e	500	depends on OF
5772717e NA	501	depends on MFD_KHADAS_MCU
	502	select MFD_CORE
	503	select REGMAP
	504	help
	505	If you say yes here you get support for the FAN controlled
	506	by the Microcontroller found on the Khadas VIM boards.
	507
e7e3a7c3 YZ	508	config LOONGSON2_THERMAL
	509	tristate "Loongson-2 SoC series thermal driver"
	510	depends on LOONGARCH \|\| COMPILE_TEST
	511	depends on OF
	512	help
	513	Support for Thermal driver found on Loongson-2 SoC series platforms.
	514	The thermal driver realizes get_temp and set_trips function, which
	515	are used to obtain the temperature of the current node and set the
	516	temperature range to trigger the interrupt. When the input temperature
	517	is higher than the high temperature threshold or lower than the low
	518	temperature threshold, the interrupt will occur.
	519
72e19897	520	endif