1 # SPDX-License-Identifier: GPL-2.0-only
3 # Generic thermal drivers configuration
9 Thermal drivers offer a generic mechanism for
10 thermal management. Usually it's made up of one or more thermal
11 zones and cooling devices.
12 Each thermal zone contains its own temperature, trip points,
14 All platforms with ACPI or Open Firmware thermal support can use
16 If you want this support, you should say Y here.
20 config THERMAL_NETLINK
21 bool "Thermal netlink management"
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.
29 config THERMAL_STATISTICS
30 bool "Thermal state transition statistics"
32 Export thermal state transition statistics information through sysfs.
36 config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
37 int "Emergency poweroff delay in milli-seconds"
40 Thermal subsystem will issue a graceful shutdown when
41 critical temperatures are reached using orderly_poweroff(). In
42 case of failure of an orderly_poweroff(), the thermal emergency
43 poweroff kicks in after a delay has elapsed and shuts down the system.
44 This config is number of milliseconds to delay before emergency
45 poweroff kicks in. Similarly to the critical trip point,
46 the delay should be carefully profiled so as to give adequate
47 time for orderly_poweroff() to finish on regular execution.
48 If set to 0 emergency poweroff will not be supported.
54 prompt "Expose thermal sensors as hwmon device"
55 depends on HWMON=y || HWMON=THERMAL
58 In case a sensor is registered with the thermal
59 framework, this option will also register it
60 as a hwmon. The sensor will then have the common
61 hwmon sysfs interface.
63 Say 'Y' here if you want all thermal sensors to
64 have hwmon sysfs interface too.
68 prompt "APIs to parse thermal data out of device tree"
72 This options provides helpers to add the support to
73 read and parse thermal data definitions out of the
76 Say 'Y' here if you need to build thermal infrastructure
79 config THERMAL_WRITABLE_TRIPS
80 bool "Enable writable trip points"
82 This option allows the system integrator to choose whether
83 trip temperatures can be changed from userspace. The
84 writable trips need to be specified when setting up the
85 thermal zone but the choice here takes precedence.
87 Say 'Y' here if you would like to allow userspace tools to
88 change trip temperatures.
91 prompt "Default Thermal governor"
92 default THERMAL_DEFAULT_GOV_STEP_WISE
94 This option sets which thermal governor shall be loaded at
95 startup. If in doubt, select 'step_wise'.
97 config THERMAL_DEFAULT_GOV_STEP_WISE
99 select THERMAL_GOV_STEP_WISE
101 Use the step_wise governor as default. This throttles the
102 devices one step at a time.
104 config THERMAL_DEFAULT_GOV_FAIR_SHARE
106 select THERMAL_GOV_FAIR_SHARE
108 Use the fair_share governor as default. This throttles the
109 devices based on their 'contribution' to a zone. The
110 contribution should be provided through platform data.
112 config THERMAL_DEFAULT_GOV_USER_SPACE
114 select THERMAL_GOV_USER_SPACE
116 Select this if you want to let the user space manage the
119 config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
120 bool "power_allocator"
121 depends on THERMAL_GOV_POWER_ALLOCATOR
123 Select this if you want to control temperature based on
124 system and device power allocation. This governor can only
125 operate on cooling devices that implement the power API.
129 config THERMAL_GOV_FAIR_SHARE
130 bool "Fair-share thermal governor"
132 Enable this to manage platform thermals using fair-share governor.
134 config THERMAL_GOV_STEP_WISE
135 bool "Step_wise thermal governor"
137 Enable this to manage platform thermals using a simple linear
140 config THERMAL_GOV_BANG_BANG
141 bool "Bang Bang thermal governor"
144 Enable this to manage platform thermals using bang bang governor.
146 Say 'Y' here if you want to use two point temperature regulation
147 used for fans without throttling. Some fan drivers depend on this
148 governor to be enabled (e.g. acerhdf).
150 config THERMAL_GOV_USER_SPACE
151 bool "User_space thermal governor"
153 Enable this to let the user space manage the platform thermals.
155 config THERMAL_GOV_POWER_ALLOCATOR
156 bool "Power allocator thermal governor"
157 depends on ENERGY_MODEL
159 Enable this to manage platform thermals by dynamically
160 allocating and limiting power to devices.
163 bool "Generic cpu cooling support"
164 depends on THERMAL_OF
166 Enable the CPU cooling features. If the system has no active
167 cooling device available, this option allows to use the CPU
172 config CPU_FREQ_THERMAL
173 bool "CPU frequency cooling device"
177 This implements the generic cpu cooling mechanism through frequency
178 reduction. An ACPI version of this already exists
179 (drivers/acpi/processor_thermal.c).
180 This will be useful for platforms using the generic thermal interface
181 and not the ACPI interface.
183 config CPU_IDLE_THERMAL
184 bool "CPU idle cooling device"
185 depends on IDLE_INJECT
187 This implements the CPU cooling mechanism through
188 idle injection. This will throttle the CPU by injecting
192 config DEVFREQ_THERMAL
193 bool "Generic device cooling support"
194 depends on PM_DEVFREQ
197 This implements the generic devfreq cooling mechanism through
198 frequency reduction for devices using devfreq.
200 This will throttle the device by limiting the maximum allowed DVFS
201 frequency corresponding to the cooling level.
203 In order to use the power extensions of the cooling device,
204 devfreq should use the simple_ondemand governor.
206 If you want this support, you should say Y here.
208 config THERMAL_EMULATION
209 bool "Thermal emulation mode support"
211 Enable this option to make a emul_temp sysfs node in thermal zone
212 directory to support temperature emulation. With emulation sysfs node,
213 user can manually input temperature and test the different trip
214 threshold behaviour for simulation purpose.
216 WARNING: Be careful while enabling this option on production systems,
217 because userland can easily disable the thermal policy by simply
218 flooding this sysfs node with low temperature values.
221 tristate "Generic Thermal MMIO driver"
222 depends on OF || COMPILE_TEST
225 This option enables the generic thermal MMIO driver that will use
226 memory-mapped reads to get the temperature. Any HW/System that
227 allows temperature reading by a single memory-mapped reading, be it
228 register or shared memory, is a potential candidate to work with this
232 tristate "Hisilicon thermal driver"
233 depends on ARCH_HISI || COMPILE_TEST
238 Enable this to plug hisilicon's thermal sensor driver into the Linux
239 thermal framework. cpufreq is used as the cooling device to throttle
240 CPUs when the passive trip is crossed.
243 tristate "Temperature sensor driver for Freescale i.MX SoCs"
244 depends on ARCH_MXC || COMPILE_TEST
245 depends on NVMEM || !NVMEM
246 depends on MFD_SYSCON
249 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
250 It supports one critical trip point and one passive trip point. The
251 cpufreq is used as the cooling device to throttle CPUs when the
252 passive trip is crossed.
254 config IMX_SC_THERMAL
255 tristate "Temperature sensor driver for NXP i.MX SoCs with System Controller"
259 Support for Temperature Monitor (TEMPMON) found on NXP i.MX SoCs with
260 system controller inside, Linux kernel has to communicate with system
261 controller via MU (message unit) IPC to get temperature from thermal
262 sensor. It supports one critical trip point and one
263 passive trip point for each thermal sensor.
265 config IMX8MM_THERMAL
266 tristate "Temperature sensor driver for Freescale i.MX8MM SoC"
267 depends on ARCH_MXC || COMPILE_TEST
270 Support for Thermal Monitoring Unit (TMU) found on Freescale i.MX8MM SoC.
271 It supports one critical trip point and one passive trip point. The
272 cpufreq is used as the cooling device to throttle CPUs when the passive
276 tristate "Texas Instruments K3 thermal support"
277 depends on ARCH_K3 || COMPILE_TEST
279 If you say yes here you get thermal support for the Texas Instruments
280 K3 SoC family. The current chip supported is:
283 This includes temperature reading functionality.
285 config MAX77620_THERMAL
286 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
287 depends on MFD_MAX77620
290 Support for die junction temperature warning alarm for Maxim
291 Semiconductor PMIC MAX77620 device. Device generates two alarm
292 interrupts when PMIC die temperature cross the threshold of
293 120 degC and 140 degC.
296 tristate "QorIQ Thermal Monitoring Unit"
297 depends on THERMAL_OF && HAS_IOMEM
298 depends on PPC_E500MC || SOC_LS1021A || ARCH_LAYERSCAPE || (ARCH_MXC && ARM64) || COMPILE_TEST
301 Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
302 It supports one critical trip point and one passive trip point. The
303 cpufreq is used as the cooling device to throttle CPUs when the
304 passive trip is crossed.
307 tristate "SPEAr thermal sensor driver"
308 depends on PLAT_SPEAR || COMPILE_TEST
312 Enable this to plug the SPEAr thermal sensor driver into the Linux
316 tristate "Allwinner sun8i thermal driver"
317 depends on ARCH_SUNXI || COMPILE_TEST
321 depends on RESET_CONTROLLER
323 Support for the sun8i thermal sensor driver into the Linux thermal
326 To compile this driver as a module, choose M here: the
327 module will be called sun8i-thermal.
329 config ROCKCHIP_THERMAL
330 tristate "Rockchip thermal driver"
331 depends on ARCH_ROCKCHIP || COMPILE_TEST
332 depends on RESET_CONTROLLER
335 Rockchip thermal driver provides support for Temperature sensor
336 ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
337 trip point. Cpufreq is used as the cooling device and will throttle
338 CPUs when the Temperature crosses the passive trip point.
341 tristate "Renesas R-Car thermal driver"
342 depends on ARCH_RENESAS || COMPILE_TEST
345 Enable this to plug the R-Car thermal sensor driver into the Linux
348 config RCAR_GEN3_THERMAL
349 tristate "Renesas R-Car Gen3 and RZ/G2 thermal driver"
350 depends on ARCH_RENESAS || COMPILE_TEST
354 Enable this to plug the R-Car Gen3 or RZ/G2 thermal sensor driver into
355 the Linux thermal framework.
357 config KIRKWOOD_THERMAL
358 tristate "Temperature sensor on Marvell Kirkwood SoCs"
359 depends on MACH_KIRKWOOD || COMPILE_TEST
363 Support for the Kirkwood thermal sensor driver into the Linux thermal
364 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
367 tristate "Temperature sensor on Marvell Dove SoCs"
368 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
372 Support for the Dove thermal sensor driver in the Linux thermal
375 config DB8500_THERMAL
376 tristate "DB8500 thermal management"
377 depends on MFD_DB8500_PRCMU && OF
380 Adds DB8500 thermal management implementation according to the thermal
381 management framework. A thermal zone with several trip points will be
382 created. Cooling devices can be bound to the trip points to cool this
383 thermal zone if trip points reached.
385 config ARMADA_THERMAL
386 tristate "Marvell EBU Armada SoCs thermal management"
387 depends on ARCH_MVEBU || COMPILE_TEST
391 Enable this option if you want to have support for thermal management
392 controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
394 config DA9062_THERMAL
395 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
396 depends on MFD_DA9062 || COMPILE_TEST
399 Enable this for the Dialog Semiconductor thermal sensor driver.
400 This will report PMIC junction over-temperature for one thermal trip
402 Compatible with the DA9062 and DA9061 PMICs.
405 tristate "Temperature sensor driver for mediatek SoCs"
406 depends on ARCH_MEDIATEK || COMPILE_TEST
408 depends on NVMEM || NVMEM=n
409 depends on RESET_CONTROLLER
412 Enable this option if you want to have support for thermal management
413 controller present in Mediatek SoCs
415 config AMLOGIC_THERMAL
416 tristate "Amlogic Thermal Support"
418 depends on OF && ARCH_MESON
420 If you say yes here you get support for Amlogic Thermal
423 This driver can also be built as a module. If so, the module will
424 be called amlogic_thermal.
426 menu "Intel thermal drivers"
427 depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
428 source "drivers/thermal/intel/Kconfig"
431 menu "Broadcom thermal drivers"
432 depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
434 source "drivers/thermal/broadcom/Kconfig"
437 menu "Texas Instruments thermal drivers"
438 depends on ARCH_HAS_BANDGAP || COMPILE_TEST
440 source "drivers/thermal/ti-soc-thermal/Kconfig"
443 menu "Samsung thermal drivers"
444 depends on ARCH_EXYNOS || COMPILE_TEST
445 source "drivers/thermal/samsung/Kconfig"
448 menu "STMicroelectronics thermal drivers"
449 depends on (ARCH_STI || ARCH_STM32) && OF
450 source "drivers/thermal/st/Kconfig"
454 tristate "Tango thermal management"
455 depends on ARCH_TANGO || COMPILE_TEST
457 Enable the Tango thermal driver, which supports the primitive
458 temperature sensor embedded in Tango chips since the SMP8758.
459 This sensor only generates a 1-bit signal to indicate whether
460 the die temperature exceeds a programmable threshold.
462 source "drivers/thermal/tegra/Kconfig"
464 config GENERIC_ADC_THERMAL
465 tristate "Generic ADC based thermal sensor"
468 This enabled a thermal sysfs driver for the temperature sensor
469 which is connected to the General Purpose ADC. The ADC channel
470 is read via IIO framework and the channel information is provided
471 to this driver. This driver reports the temperature by reading ADC
472 channel and converts it to temperature based on lookup table.
474 menu "Qualcomm thermal drivers"
475 depends on (ARCH_QCOM && OF) || COMPILE_TEST
476 source "drivers/thermal/qcom/Kconfig"
479 config ZX2967_THERMAL
480 tristate "Thermal sensors on zx2967 SoC"
481 depends on ARCH_ZX || COMPILE_TEST
483 Enable the zx2967 thermal sensors driver, which supports
484 the primitive temperature sensor embedded in zx2967 SoCs.
485 This sensor generates the real time die temperature.
487 config UNIPHIER_THERMAL
488 tristate "Socionext UniPhier thermal driver"
489 depends on ARCH_UNIPHIER || COMPILE_TEST
490 depends on THERMAL_OF && MFD_SYSCON
492 Enable this to plug in UniPhier on-chip PVT thermal driver into the
493 thermal framework. The driver supports CPU thermal zone temperature
494 reporting and a couple of trip points.
497 tristate "Temperature sensor on Spreadtrum SoCs"
498 depends on ARCH_SPRD || COMPILE_TEST
500 Support for the Spreadtrum thermal sensor driver in the Linux thermal
503 config KHADAS_MCU_FAN_THERMAL
504 tristate "Khadas MCU controller FAN cooling support"
505 depends on OF || COMPILE_TEST
506 depends on MFD_KHADAS_MCU
510 If you say yes here you get support for the FAN controlled
511 by the Microcontroller found on the Khadas VIM boards.