1 # SPDX-License-Identifier: GPL-2.0-only
3 # Generic thermal sysfs drivers configuration
7 bool "Generic Thermal sysfs driver"
9 Generic Thermal Sysfs driver offers a generic mechanism for
10 thermal management. Usually it's made up of one or more thermal
11 zone and cooling device.
12 Each thermal zone contains its own temperature, trip points,
14 All platforms with ACPI thermal support can use this driver.
15 If you want this support, you should say Y here.
19 config THERMAL_STATISTICS
20 bool "Thermal state transition statistics"
22 Export thermal state transition statistics information through sysfs.
26 config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
27 int "Emergency poweroff delay in milli-seconds"
30 Thermal subsystem will issue a graceful shutdown when
31 critical temperatures are reached using orderly_poweroff(). In
32 case of failure of an orderly_poweroff(), the thermal emergency
33 poweroff kicks in after a delay has elapsed and shuts down the system.
34 This config is number of milliseconds to delay before emergency
35 poweroff kicks in. Similarly to the critical trip point,
36 the delay should be carefully profiled so as to give adequate
37 time for orderly_poweroff() to finish on regular execution.
38 If set to 0 emergency poweroff will not be supported.
44 prompt "Expose thermal sensors as hwmon device"
45 depends on HWMON=y || HWMON=THERMAL
48 In case a sensor is registered with the thermal
49 framework, this option will also register it
50 as a hwmon. The sensor will then have the common
51 hwmon sysfs interface.
53 Say 'Y' here if you want all thermal sensors to
54 have hwmon sysfs interface too.
58 prompt "APIs to parse thermal data out of device tree"
62 This options provides helpers to add the support to
63 read and parse thermal data definitions out of the
66 Say 'Y' here if you need to build thermal infrastructure
69 config THERMAL_WRITABLE_TRIPS
70 bool "Enable writable trip points"
72 This option allows the system integrator to choose whether
73 trip temperatures can be changed from userspace. The
74 writable trips need to be specified when setting up the
75 thermal zone but the choice here takes precedence.
77 Say 'Y' here if you would like to allow userspace tools to
78 change trip temperatures.
81 prompt "Default Thermal governor"
82 default THERMAL_DEFAULT_GOV_STEP_WISE
84 This option sets which thermal governor shall be loaded at
85 startup. If in doubt, select 'step_wise'.
87 config THERMAL_DEFAULT_GOV_STEP_WISE
89 select THERMAL_GOV_STEP_WISE
91 Use the step_wise governor as default. This throttles the
92 devices one step at a time.
94 config THERMAL_DEFAULT_GOV_FAIR_SHARE
96 select THERMAL_GOV_FAIR_SHARE
98 Use the fair_share governor as default. This throttles the
99 devices based on their 'contribution' to a zone. The
100 contribution should be provided through platform data.
102 config THERMAL_DEFAULT_GOV_USER_SPACE
104 select THERMAL_GOV_USER_SPACE
106 Select this if you want to let the user space manage the
109 config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
110 bool "power_allocator"
111 select THERMAL_GOV_POWER_ALLOCATOR
113 Select this if you want to control temperature based on
114 system and device power allocation. This governor can only
115 operate on cooling devices that implement the power API.
119 config THERMAL_GOV_FAIR_SHARE
120 bool "Fair-share thermal governor"
122 Enable this to manage platform thermals using fair-share governor.
124 config THERMAL_GOV_STEP_WISE
125 bool "Step_wise thermal governor"
127 Enable this to manage platform thermals using a simple linear
130 config THERMAL_GOV_BANG_BANG
131 bool "Bang Bang thermal governor"
134 Enable this to manage platform thermals using bang bang governor.
136 Say 'Y' here if you want to use two point temperature regulation
137 used for fans without throttling. Some fan drivers depend on this
138 governor to be enabled (e.g. acerhdf).
140 config THERMAL_GOV_USER_SPACE
141 bool "User_space thermal governor"
143 Enable this to let the user space manage the platform thermals.
145 config THERMAL_GOV_POWER_ALLOCATOR
146 bool "Power allocator thermal governor"
148 Enable this to manage platform thermals by dynamically
149 allocating and limiting power to devices.
152 bool "Generic cpu cooling support"
154 depends on THERMAL_OF
156 This implements the generic cpu cooling mechanism through frequency
157 reduction. An ACPI version of this already exists
158 (drivers/acpi/processor_thermal.c).
159 This will be useful for platforms using the generic thermal interface
160 and not the ACPI interface.
162 If you want this support, you should say Y here.
165 bool "Generic clock cooling support"
166 depends on COMMON_CLK
169 This entry implements the generic clock cooling mechanism through
170 frequency clipping. Typically used to cool off co-processors. The
171 device that is configured to use this cooling mechanism will be
172 controlled to reduce clock frequency whenever temperature is high.
174 config DEVFREQ_THERMAL
175 bool "Generic device cooling support"
176 depends on PM_DEVFREQ
179 This implements the generic devfreq cooling mechanism through
180 frequency reduction for devices using devfreq.
182 This will throttle the device by limiting the maximum allowed DVFS
183 frequency corresponding to the cooling level.
185 In order to use the power extensions of the cooling device,
186 devfreq should use the simple_ondemand governor.
188 If you want this support, you should say Y here.
190 config THERMAL_EMULATION
191 bool "Thermal emulation mode support"
193 Enable this option to make a emul_temp sysfs node in thermal zone
194 directory to support temperature emulation. With emulation sysfs node,
195 user can manually input temperature and test the different trip
196 threshold behaviour for simulation purpose.
198 WARNING: Be careful while enabling this option on production systems,
199 because userland can easily disable the thermal policy by simply
200 flooding this sysfs node with low temperature values.
203 tristate "Generic Thermal MMIO driver"
204 depends on OF || COMPILE_TEST
207 This option enables the generic thermal MMIO driver that will use
208 memory-mapped reads to get the temperature. Any HW/System that
209 allows temperature reading by a single memory-mapped reading, be it
210 register or shared memory, is a potential candidate to work with this
214 tristate "Hisilicon thermal driver"
215 depends on ARCH_HISI || COMPILE_TEST
220 Enable this to plug hisilicon's thermal sensor driver into the Linux
221 thermal framework. cpufreq is used as the cooling device to throttle
222 CPUs when the passive trip is crossed.
225 tristate "Temperature sensor driver for Freescale i.MX SoCs"
226 depends on ARCH_MXC || COMPILE_TEST
227 depends on NVMEM || !NVMEM
228 depends on MFD_SYSCON
231 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
232 It supports one critical trip point and one passive trip point. The
233 cpufreq is used as the cooling device to throttle CPUs when the
234 passive trip is crossed.
236 config MAX77620_THERMAL
237 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
238 depends on MFD_MAX77620
241 Support for die junction temperature warning alarm for Maxim
242 Semiconductor PMIC MAX77620 device. Device generates two alarm
243 interrupts when PMIC die temperature cross the threshold of
244 120 degC and 140 degC.
247 tristate "QorIQ Thermal Monitoring Unit"
248 depends on THERMAL_OF
251 Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
252 It supports one critical trip point and one passive trip point. The
253 cpufreq is used as the cooling device to throttle CPUs when the
254 passive trip is crossed.
257 tristate "SPEAr thermal sensor driver"
258 depends on PLAT_SPEAR || COMPILE_TEST
262 Enable this to plug the SPEAr thermal sensor driver into the Linux
265 config ROCKCHIP_THERMAL
266 tristate "Rockchip thermal driver"
267 depends on ARCH_ROCKCHIP || COMPILE_TEST
268 depends on RESET_CONTROLLER
271 Rockchip thermal driver provides support for Temperature sensor
272 ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
273 trip point. Cpufreq is used as the cooling device and will throttle
274 CPUs when the Temperature crosses the passive trip point.
277 tristate "Renesas R-Car thermal driver"
278 depends on ARCH_RENESAS || COMPILE_TEST
281 Enable this to plug the R-Car thermal sensor driver into the Linux
284 config RCAR_GEN3_THERMAL
285 tristate "Renesas R-Car Gen3 thermal driver"
286 depends on ARCH_RENESAS || COMPILE_TEST
290 Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
293 config KIRKWOOD_THERMAL
294 tristate "Temperature sensor on Marvell Kirkwood SoCs"
295 depends on MACH_KIRKWOOD || COMPILE_TEST
299 Support for the Kirkwood thermal sensor driver into the Linux thermal
300 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
303 tristate "Temperature sensor on Marvell Dove SoCs"
304 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
308 Support for the Dove thermal sensor driver in the Linux thermal
311 config DB8500_THERMAL
312 tristate "DB8500 thermal management"
313 depends on MFD_DB8500_PRCMU && OF
316 Adds DB8500 thermal management implementation according to the thermal
317 management framework. A thermal zone with several trip points will be
318 created. Cooling devices can be bound to the trip points to cool this
319 thermal zone if trip points reached.
321 config ARMADA_THERMAL
322 tristate "Marvell EBU Armada SoCs thermal management"
323 depends on ARCH_MVEBU || COMPILE_TEST
327 Enable this option if you want to have support for thermal management
328 controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
330 config DA9062_THERMAL
331 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
332 depends on MFD_DA9062 || COMPILE_TEST
335 Enable this for the Dialog Semiconductor thermal sensor driver.
336 This will report PMIC junction over-temperature for one thermal trip
338 Compatible with the DA9062 and DA9061 PMICs.
341 tristate "Temperature sensor driver for mediatek SoCs"
342 depends on ARCH_MEDIATEK || COMPILE_TEST
344 depends on NVMEM || NVMEM=n
345 depends on RESET_CONTROLLER
348 Enable this option if you want to have support for thermal management
349 controller present in Mediatek SoCs
351 menu "Intel thermal drivers"
352 depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
353 source "drivers/thermal/intel/Kconfig"
356 menu "Broadcom thermal drivers"
357 depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
359 source "drivers/thermal/broadcom/Kconfig"
362 menu "Texas Instruments thermal drivers"
363 depends on ARCH_HAS_BANDGAP || COMPILE_TEST
365 source "drivers/thermal/ti-soc-thermal/Kconfig"
368 menu "Samsung thermal drivers"
369 depends on ARCH_EXYNOS || COMPILE_TEST
370 source "drivers/thermal/samsung/Kconfig"
373 menu "STMicroelectronics thermal drivers"
374 depends on (ARCH_STI || ARCH_STM32) && OF
375 source "drivers/thermal/st/Kconfig"
379 tristate "Tango thermal management"
380 depends on ARCH_TANGO || COMPILE_TEST
382 Enable the Tango thermal driver, which supports the primitive
383 temperature sensor embedded in Tango chips since the SMP8758.
384 This sensor only generates a 1-bit signal to indicate whether
385 the die temperature exceeds a programmable threshold.
387 source "drivers/thermal/tegra/Kconfig"
389 config GENERIC_ADC_THERMAL
390 tristate "Generic ADC based thermal sensor"
393 This enabled a thermal sysfs driver for the temperature sensor
394 which is connected to the General Purpose ADC. The ADC channel
395 is read via IIO framework and the channel information is provided
396 to this driver. This driver reports the temperature by reading ADC
397 channel and converts it to temperature based on lookup table.
399 menu "Qualcomm thermal drivers"
400 depends on (ARCH_QCOM && OF) || COMPILE_TEST
401 source "drivers/thermal/qcom/Kconfig"
404 config ZX2967_THERMAL
405 tristate "Thermal sensors on zx2967 SoC"
406 depends on ARCH_ZX || COMPILE_TEST
408 Enable the zx2967 thermal sensors driver, which supports
409 the primitive temperature sensor embedded in zx2967 SoCs.
410 This sensor generates the real time die temperature.
412 config UNIPHIER_THERMAL
413 tristate "Socionext UniPhier thermal driver"
414 depends on ARCH_UNIPHIER || COMPILE_TEST
415 depends on THERMAL_OF && MFD_SYSCON
417 Enable this to plug in UniPhier on-chip PVT thermal driver into the
418 thermal framework. The driver supports CPU thermal zone temperature
419 reporting and a couple of trip points.