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
83 config THERMAL_WRITABLE_TRIPS
84 bool "Enable writable trip points"
86 This option allows the system integrator to choose whether
87 trip temperatures can be changed from userspace. The
88 writable trips need to be specified when setting up the
89 thermal zone but the choice here takes precedence.
91 Say 'Y' here if you would like to allow userspace tools to
92 change trip temperatures.
95 prompt "Default Thermal governor"
96 default THERMAL_DEFAULT_GOV_STEP_WISE
98 This option sets which thermal governor shall be loaded at
99 startup. If in doubt, select 'step_wise'.
101 config THERMAL_DEFAULT_GOV_STEP_WISE
103 select THERMAL_GOV_STEP_WISE
105 Use the step_wise governor as default. This throttles the
106 devices one step at a time.
108 config THERMAL_DEFAULT_GOV_FAIR_SHARE
110 select THERMAL_GOV_FAIR_SHARE
112 Use the fair_share governor as default. This throttles the
113 devices based on their 'contribution' to a zone. The
114 contribution should be provided through platform data.
116 config THERMAL_DEFAULT_GOV_USER_SPACE
118 select THERMAL_GOV_USER_SPACE
120 The Userspace governor allows to get trip point crossed
121 notification from the kernel via uevents. It is recommended
122 to use the netlink interface instead which gives richer
123 information about the thermal framework events.
125 config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
126 bool "power_allocator"
127 depends on THERMAL_GOV_POWER_ALLOCATOR
129 Select this if you want to control temperature based on
130 system and device power allocation. This governor can only
131 operate on cooling devices that implement the power API.
135 config THERMAL_GOV_FAIR_SHARE
136 bool "Fair-share thermal governor"
138 Enable this to manage platform thermals using fair-share governor.
140 config THERMAL_GOV_STEP_WISE
141 bool "Step_wise thermal governor"
143 Enable this to manage platform thermals using a simple linear
146 config THERMAL_GOV_BANG_BANG
147 bool "Bang Bang thermal governor"
150 Enable this to manage platform thermals using bang bang governor.
152 Say 'Y' here if you want to use two point temperature regulation
153 used for fans without throttling. Some fan drivers depend on this
154 governor to be enabled (e.g. acerhdf).
156 config THERMAL_GOV_USER_SPACE
157 bool "User_space thermal governor"
159 Enable this to let the user space manage the platform thermals.
161 config THERMAL_GOV_POWER_ALLOCATOR
162 bool "Power allocator thermal governor"
163 depends on ENERGY_MODEL
165 Enable this to manage platform thermals by dynamically
166 allocating and limiting power to devices.
169 bool "Generic cpu cooling support"
170 depends on THERMAL_OF
172 Enable the CPU cooling features. If the system has no active
173 cooling device available, this option allows to use the CPU
178 config CPU_FREQ_THERMAL
179 bool "CPU frequency cooling device"
183 This implements the generic cpu cooling mechanism through frequency
184 reduction. An ACPI version of this already exists
185 (drivers/acpi/processor_thermal.c).
186 This will be useful for platforms using the generic thermal interface
187 and not the ACPI interface.
189 config CPU_IDLE_THERMAL
190 bool "CPU idle cooling device"
191 depends on IDLE_INJECT
193 This implements the CPU cooling mechanism through
194 idle injection. This will throttle the CPU by injecting
198 config DEVFREQ_THERMAL
199 bool "Generic device cooling support"
200 depends on PM_DEVFREQ
203 This implements the generic devfreq cooling mechanism through
204 frequency reduction for devices using devfreq.
206 This will throttle the device by limiting the maximum allowed DVFS
207 frequency corresponding to the cooling level.
209 In order to use the power extensions of the cooling device,
210 devfreq should use the simple_ondemand governor.
212 If you want this support, you should say Y here.
214 config THERMAL_EMULATION
215 bool "Thermal emulation mode support"
217 Enable this option to make a emul_temp sysfs node in thermal zone
218 directory to support temperature emulation. With emulation sysfs node,
219 user can manually input temperature and test the different trip
220 threshold behaviour for simulation purpose.
222 WARNING: Be careful while enabling this option on production systems,
223 because userland can easily disable the thermal policy by simply
224 flooding this sysfs node with low temperature values.
227 tristate "Generic Thermal MMIO driver"
231 This option enables the generic thermal MMIO driver that will use
232 memory-mapped reads to get the temperature. Any HW/System that
233 allows temperature reading by a single memory-mapped reading, be it
234 register or shared memory, is a potential candidate to work with this
238 tristate "Hisilicon thermal driver"
239 depends on ARCH_HISI || COMPILE_TEST
244 Enable this to plug hisilicon's thermal sensor driver into the Linux
245 thermal framework. cpufreq is used as the cooling device to throttle
246 CPUs when the passive trip is crossed.
249 tristate "Temperature sensor driver for Freescale i.MX SoCs"
250 depends on ARCH_MXC || COMPILE_TEST
251 depends on NVMEM || !NVMEM
252 depends on MFD_SYSCON
255 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
256 It supports one critical trip point and one passive trip point. The
257 cpufreq is used as the cooling device to throttle CPUs when the
258 passive trip is crossed.
260 config IMX_SC_THERMAL
261 tristate "Temperature sensor driver for NXP i.MX SoCs with System Controller"
265 Support for Temperature Monitor (TEMPMON) found on NXP i.MX SoCs with
266 system controller inside, Linux kernel has to communicate with system
267 controller via MU (message unit) IPC to get temperature from thermal
268 sensor. It supports one critical trip point and one
269 passive trip point for each thermal sensor.
271 config IMX8MM_THERMAL
272 tristate "Temperature sensor driver for Freescale i.MX8MM SoC"
273 depends on ARCH_MXC || COMPILE_TEST
276 Support for Thermal Monitoring Unit (TMU) found on Freescale i.MX8MM SoC.
277 It supports one critical trip point and one passive trip point. The
278 cpufreq is used as the cooling device to throttle CPUs when the passive
282 tristate "Texas Instruments K3 thermal support"
283 depends on ARCH_K3 || COMPILE_TEST
285 If you say yes here you get thermal support for the Texas Instruments
286 K3 SoC family. The current chip supported is:
289 This includes temperature reading functionality.
291 config MAX77620_THERMAL
292 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
293 depends on MFD_MAX77620
296 Support for die junction temperature warning alarm for Maxim
297 Semiconductor PMIC MAX77620 device. Device generates two alarm
298 interrupts when PMIC die temperature cross the threshold of
299 120 degC and 140 degC.
302 tristate "QorIQ Thermal Monitoring Unit"
303 depends on THERMAL_OF && HAS_IOMEM
304 depends on PPC_E500MC || SOC_LS1021A || ARCH_LAYERSCAPE || (ARCH_MXC && ARM64) || COMPILE_TEST
307 Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
308 It supports one critical trip point and one passive trip point. The
309 cpufreq is used as the cooling device to throttle CPUs when the
310 passive trip is crossed.
313 tristate "SPEAr thermal sensor driver"
314 depends on PLAT_SPEAR || COMPILE_TEST
318 Enable this to plug the SPEAr thermal sensor driver into the Linux
322 tristate "Allwinner sun8i thermal driver"
323 depends on ARCH_SUNXI || COMPILE_TEST
327 depends on RESET_CONTROLLER
329 Support for the sun8i thermal sensor driver into the Linux thermal
332 To compile this driver as a module, choose M here: the
333 module will be called sun8i-thermal.
335 config ROCKCHIP_THERMAL
336 tristate "Rockchip thermal driver"
337 depends on ARCH_ROCKCHIP || COMPILE_TEST
338 depends on RESET_CONTROLLER
341 Rockchip thermal driver provides support for Temperature sensor
342 ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
343 trip point. Cpufreq is used as the cooling device and will throttle
344 CPUs when the Temperature crosses the passive trip point.
347 tristate "Renesas R-Car thermal driver"
348 depends on ARCH_RENESAS || COMPILE_TEST
351 Enable this to plug the R-Car thermal sensor driver into the Linux
354 config RCAR_GEN3_THERMAL
355 tristate "Renesas R-Car Gen3 and RZ/G2 thermal driver"
356 depends on ARCH_RENESAS || COMPILE_TEST
360 Enable this to plug the R-Car Gen3 or RZ/G2 thermal sensor driver into
361 the Linux thermal framework.
364 tristate "Renesas RZ/G2L thermal driver"
365 depends on ARCH_RENESAS || COMPILE_TEST
369 Enable this to plug the RZ/G2L thermal sensor driver into the Linux
372 config KIRKWOOD_THERMAL
373 tristate "Temperature sensor on Marvell Kirkwood SoCs"
374 depends on MACH_KIRKWOOD || COMPILE_TEST
378 Support for the Kirkwood thermal sensor driver into the Linux thermal
379 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
382 tristate "Temperature sensor on Marvell Dove SoCs"
383 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
387 Support for the Dove thermal sensor driver in the Linux thermal
390 config DB8500_THERMAL
391 tristate "DB8500 thermal management"
392 depends on MFD_DB8500_PRCMU && OF
395 Adds DB8500 thermal management implementation according to the thermal
396 management framework. A thermal zone with several trip points will be
397 created. Cooling devices can be bound to the trip points to cool this
398 thermal zone if trip points reached.
400 config ARMADA_THERMAL
401 tristate "Marvell EBU Armada SoCs thermal management"
402 depends on ARCH_MVEBU || COMPILE_TEST
406 Enable this option if you want to have support for thermal management
407 controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
409 config DA9062_THERMAL
410 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
411 depends on MFD_DA9062 || COMPILE_TEST
414 Enable this for the Dialog Semiconductor thermal sensor driver.
415 This will report PMIC junction over-temperature for one thermal trip
417 Compatible with the DA9062 and DA9061 PMICs.
419 menu "Mediatek thermal drivers"
420 depends on ARCH_MEDIATEK || COMPILE_TEST
421 source "drivers/thermal/mediatek/Kconfig"
424 config AMLOGIC_THERMAL
425 tristate "Amlogic Thermal Support"
427 depends on OF && ARCH_MESON
429 If you say yes here you get support for Amlogic Thermal
432 This driver can also be built as a module. If so, the module will
433 be called amlogic_thermal.
435 menu "Intel thermal drivers"
436 depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
437 source "drivers/thermal/intel/Kconfig"
440 menu "Broadcom thermal drivers"
441 depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
443 source "drivers/thermal/broadcom/Kconfig"
446 menu "Texas Instruments thermal drivers"
447 depends on ARCH_HAS_BANDGAP || COMPILE_TEST
449 source "drivers/thermal/ti-soc-thermal/Kconfig"
452 menu "Samsung thermal drivers"
453 depends on ARCH_EXYNOS || COMPILE_TEST
454 source "drivers/thermal/samsung/Kconfig"
457 menu "STMicroelectronics thermal drivers"
458 depends on (ARCH_STI || ARCH_STM32) && OF
459 source "drivers/thermal/st/Kconfig"
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 UNIPHIER_THERMAL
480 tristate "Socionext UniPhier thermal driver"
481 depends on ARCH_UNIPHIER || COMPILE_TEST
482 depends on THERMAL_OF && MFD_SYSCON
484 Enable this to plug in UniPhier on-chip PVT thermal driver into the
485 thermal framework. The driver supports CPU thermal zone temperature
486 reporting and a couple of trip points.
489 tristate "Temperature sensor on Spreadtrum SoCs"
490 depends on ARCH_SPRD || COMPILE_TEST
492 Support for the Spreadtrum thermal sensor driver in the Linux thermal
495 config KHADAS_MCU_FAN_THERMAL
496 tristate "Khadas MCU controller FAN cooling support"
498 depends on MFD_KHADAS_MCU
502 If you say yes here you get support for the FAN controlled
503 by the Microcontroller found on the Khadas VIM boards.