2 # Generic thermal sysfs drivers configuration
6 tristate "Generic Thermal sysfs driver"
8 Generic Thermal Sysfs driver offers a generic mechanism for
9 thermal management. Usually it's made up of one or more thermal
10 zone and cooling device.
11 Each thermal zone contains its own temperature, trip points,
13 All platforms with ACPI thermal support can use this driver.
14 If you want this support, you should say Y or M here.
18 config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
19 int "Emergency poweroff delay in milli-seconds"
23 Thermal subsystem will issue a graceful shutdown when
24 critical temperatures are reached using orderly_poweroff(). In
25 case of failure of an orderly_poweroff(), the thermal emergency
26 poweroff kicks in after a delay has elapsed and shuts down the system.
27 This config is number of milliseconds to delay before emergency
28 poweroff kicks in. Similarly to the critical trip point,
29 the delay should be carefully profiled so as to give adequate
30 time for orderly_poweroff() to finish on regular execution.
31 If set to 0 emergency poweroff will not be supported.
37 prompt "Expose thermal sensors as hwmon device"
38 depends on HWMON=y || HWMON=THERMAL
41 In case a sensor is registered with the thermal
42 framework, this option will also register it
43 as a hwmon. The sensor will then have the common
44 hwmon sysfs interface.
46 Say 'Y' here if you want all thermal sensors to
47 have hwmon sysfs interface too.
51 prompt "APIs to parse thermal data out of device tree"
55 This options provides helpers to add the support to
56 read and parse thermal data definitions out of the
59 Say 'Y' here if you need to build thermal infrastructure
62 config THERMAL_WRITABLE_TRIPS
63 bool "Enable writable trip points"
65 This option allows the system integrator to choose whether
66 trip temperatures can be changed from userspace. The
67 writable trips need to be specified when setting up the
68 thermal zone but the choice here takes precedence.
70 Say 'Y' here if you would like to allow userspace tools to
71 change trip temperatures.
74 prompt "Default Thermal governor"
75 default THERMAL_DEFAULT_GOV_STEP_WISE
77 This option sets which thermal governor shall be loaded at
78 startup. If in doubt, select 'step_wise'.
80 config THERMAL_DEFAULT_GOV_STEP_WISE
82 select THERMAL_GOV_STEP_WISE
84 Use the step_wise governor as default. This throttles the
85 devices one step at a time.
87 config THERMAL_DEFAULT_GOV_FAIR_SHARE
89 select THERMAL_GOV_FAIR_SHARE
91 Use the fair_share governor as default. This throttles the
92 devices based on their 'contribution' to a zone. The
93 contribution should be provided through platform data.
95 config THERMAL_DEFAULT_GOV_USER_SPACE
97 select THERMAL_GOV_USER_SPACE
99 Select this if you want to let the user space manage the
102 config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
103 bool "power_allocator"
104 select THERMAL_GOV_POWER_ALLOCATOR
106 Select this if you want to control temperature based on
107 system and device power allocation. This governor can only
108 operate on cooling devices that implement the power API.
112 config THERMAL_GOV_FAIR_SHARE
113 bool "Fair-share thermal governor"
115 Enable this to manage platform thermals using fair-share governor.
117 config THERMAL_GOV_STEP_WISE
118 bool "Step_wise thermal governor"
120 Enable this to manage platform thermals using a simple linear
123 config THERMAL_GOV_BANG_BANG
124 bool "Bang Bang thermal governor"
127 Enable this to manage platform thermals using bang bang governor.
129 Say 'Y' here if you want to use two point temperature regulation
130 used for fans without throttling. Some fan drivers depend on this
131 governor to be enabled (e.g. acerhdf).
133 config THERMAL_GOV_USER_SPACE
134 bool "User_space thermal governor"
136 Enable this to let the user space manage the platform thermals.
138 config THERMAL_GOV_POWER_ALLOCATOR
139 bool "Power allocator thermal governor"
141 Enable this to manage platform thermals by dynamically
142 allocating and limiting power to devices.
145 bool "generic cpu cooling support"
147 depends on THERMAL_OF
149 This implements the generic cpu cooling mechanism through frequency
150 reduction. An ACPI version of this already exists
151 (drivers/acpi/processor_thermal.c).
152 This will be useful for platforms using the generic thermal interface
153 and not the ACPI interface.
155 If you want this support, you should say Y here.
158 bool "Generic clock cooling support"
159 depends on COMMON_CLK
162 This entry implements the generic clock cooling mechanism through
163 frequency clipping. Typically used to cool off co-processors. The
164 device that is configured to use this cooling mechanism will be
165 controlled to reduce clock frequency whenever temperature is high.
167 config DEVFREQ_THERMAL
168 bool "Generic device cooling support"
169 depends on PM_DEVFREQ
172 This implements the generic devfreq cooling mechanism through
173 frequency reduction for devices using devfreq.
175 This will throttle the device by limiting the maximum allowed DVFS
176 frequency corresponding to the cooling level.
178 In order to use the power extensions of the cooling device,
179 devfreq should use the simple_ondemand governor.
181 If you want this support, you should say Y here.
183 config THERMAL_EMULATION
184 bool "Thermal emulation mode support"
186 Enable this option to make a emul_temp sysfs node in thermal zone
187 directory to support temperature emulation. With emulation sysfs node,
188 user can manually input temperature and test the different trip
189 threshold behaviour for simulation purpose.
191 WARNING: Be careful while enabling this option on production systems,
192 because userland can easily disable the thermal policy by simply
193 flooding this sysfs node with low temperature values.
196 tristate "Hisilicon thermal driver"
197 depends on ARCH_HISI || COMPILE_TEST
202 Enable this to plug hisilicon's thermal sensor driver into the Linux
203 thermal framework. cpufreq is used as the cooling device to throttle
204 CPUs when the passive trip is crossed.
207 tristate "Temperature sensor driver for Freescale i.MX SoCs"
208 depends on (ARCH_MXC && CPU_THERMAL) || COMPILE_TEST
209 depends on MFD_SYSCON
212 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
213 It supports one critical trip point and one passive trip point. The
214 cpufreq is used as the cooling device to throttle CPUs when the
215 passive trip is crossed.
217 config MAX77620_THERMAL
218 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
219 depends on MFD_MAX77620
222 Support for die junction temperature warning alarm for Maxim
223 Semiconductor PMIC MAX77620 device. Device generates two alarm
224 interrupts when PMIC die temperature cross the threshold of
225 120 degC and 140 degC.
228 tristate "QorIQ Thermal Monitoring Unit"
229 depends on THERMAL_OF
232 Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
233 It supports one critical trip point and one passive trip point. The
234 cpufreq is used as the cooling device to throttle CPUs when the
235 passive trip is crossed.
238 tristate "SPEAr thermal sensor driver"
239 depends on PLAT_SPEAR || COMPILE_TEST
243 Enable this to plug the SPEAr thermal sensor driver into the Linux
246 config ROCKCHIP_THERMAL
247 tristate "Rockchip thermal driver"
248 depends on ARCH_ROCKCHIP || COMPILE_TEST
249 depends on RESET_CONTROLLER
252 Rockchip thermal driver provides support for Temperature sensor
253 ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
254 trip point. Cpufreq is used as the cooling device and will throttle
255 CPUs when the Temperature crosses the passive trip point.
258 tristate "Renesas R-Car thermal driver"
259 depends on ARCH_RENESAS || COMPILE_TEST
262 Enable this to plug the R-Car thermal sensor driver into the Linux
265 config RCAR_GEN3_THERMAL
266 tristate "Renesas R-Car Gen3 thermal driver"
267 depends on ARCH_RENESAS || COMPILE_TEST
271 Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
274 config KIRKWOOD_THERMAL
275 tristate "Temperature sensor on Marvell Kirkwood SoCs"
276 depends on MACH_KIRKWOOD || COMPILE_TEST
280 Support for the Kirkwood thermal sensor driver into the Linux thermal
281 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
284 tristate "Temperature sensor on Marvell Dove SoCs"
285 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
289 Support for the Dove thermal sensor driver in the Linux thermal
292 config DB8500_THERMAL
293 tristate "DB8500 thermal management"
294 depends on MFD_DB8500_PRCMU
297 Adds DB8500 thermal management implementation according to the thermal
298 management framework. A thermal zone with several trip points will be
299 created. Cooling devices can be bound to the trip points to cool this
300 thermal zone if trip points reached.
302 config ARMADA_THERMAL
303 tristate "Armada 370/XP thermal management"
304 depends on ARCH_MVEBU || COMPILE_TEST
308 Enable this option if you want to have support for thermal management
309 controller present in Armada 370 and Armada XP SoC.
311 config DA9062_THERMAL
312 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
313 depends on MFD_DA9062 || COMPILE_TEST
316 Enable this for the Dialog Semiconductor thermal sensor driver.
317 This will report PMIC junction over-temperature for one thermal trip
319 Compatible with the DA9062 and DA9061 PMICs.
321 config INTEL_POWERCLAMP
322 tristate "Intel PowerClamp idle injection driver"
325 depends on CPU_SUP_INTEL
327 Enable this to enable Intel PowerClamp idle injection driver. This
328 enforce idle time which results in more package C-state residency. The
329 user interface is exposed via generic thermal framework.
331 config X86_PKG_TEMP_THERMAL
332 tristate "X86 package temperature thermal driver"
333 depends on X86_THERMAL_VECTOR
334 select THERMAL_GOV_USER_SPACE
335 select THERMAL_WRITABLE_TRIPS
338 Enable this to register CPU digital sensor for package temperature as
339 thermal zone. Each package will have its own thermal zone. There are
340 two trip points which can be set by user to get notifications via thermal
341 notification methods.
343 config INTEL_SOC_DTS_IOSF_CORE
345 depends on X86 && PCI
348 This is becoming a common feature for Intel SoCs to expose the additional
349 digital temperature sensors (DTSs) using side band interface (IOSF). This
350 implements the common set of helper functions to register, get temperature
351 and get/set thresholds on DTSs.
353 config INTEL_SOC_DTS_THERMAL
354 tristate "Intel SoCs DTS thermal driver"
355 depends on X86 && PCI
356 select INTEL_SOC_DTS_IOSF_CORE
357 select THERMAL_WRITABLE_TRIPS
359 Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
360 temperature sensor (DTS). These SoCs have two additional DTSs in
361 addition to DTSs on CPU cores. Each DTS will be registered as a
362 thermal zone. There are two trip points. One of the trip point can
363 be set by user mode programs to get notifications via Linux thermal
364 notification methods.The other trip is a critical trip point, which
365 was set by the driver based on the TJ MAX temperature.
367 config INTEL_QUARK_DTS_THERMAL
368 tristate "Intel Quark DTS thermal driver"
369 depends on X86_INTEL_QUARK
371 Enable this to register Intel Quark SoC (e.g. X1000) platform digital
372 temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
373 The DTS will be registered as a thermal zone. There are two trip points:
374 hot & critical. The critical trip point default value is set by
375 underlying BIOS/Firmware.
377 menu "ACPI INT340X thermal drivers"
378 source drivers/thermal/int340x_thermal/Kconfig
381 config INTEL_BXT_PMIC_THERMAL
382 tristate "Intel Broxton PMIC thermal driver"
383 depends on X86 && INTEL_SOC_PMIC_BXTWC && REGMAP
385 Select this driver for Intel Broxton PMIC with ADC channels monitoring
386 system temperature measurements and alerts.
387 This driver is used for monitoring the ADC channels of PMIC and handles
388 the alert trip point interrupts and notifies the thermal framework with
389 the trip point and temperature details of the zone.
391 config INTEL_PCH_THERMAL
392 tristate "Intel PCH Thermal Reporting Driver"
393 depends on X86 && PCI
395 Enable this to support thermal reporting on certain intel PCHs.
396 Thermal reporting device will provide temperature reading,
397 programmable trip points and other information.
400 tristate "Temperature sensor driver for mediatek SoCs"
401 depends on ARCH_MEDIATEK || COMPILE_TEST
403 depends on NVMEM || NVMEM=n
404 depends on RESET_CONTROLLER
407 Enable this option if you want to have support for thermal management
408 controller present in Mediatek SoCs
410 menu "Broadcom thermal drivers"
411 depends on ARCH_BCM || ARCH_BCM2835 || COMPILE_TEST
412 source "drivers/thermal/broadcom/Kconfig"
415 menu "Texas Instruments thermal drivers"
416 depends on ARCH_HAS_BANDGAP || COMPILE_TEST
418 source "drivers/thermal/ti-soc-thermal/Kconfig"
421 menu "Samsung thermal drivers"
422 depends on ARCH_EXYNOS || COMPILE_TEST
423 source "drivers/thermal/samsung/Kconfig"
426 menu "STMicroelectronics thermal drivers"
427 depends on ARCH_STI && OF
428 source "drivers/thermal/st/Kconfig"
432 tristate "Tango thermal management"
433 depends on ARCH_TANGO || COMPILE_TEST
435 Enable the Tango thermal driver, which supports the primitive
436 temperature sensor embedded in Tango chips since the SMP8758.
437 This sensor only generates a 1-bit signal to indicate whether
438 the die temperature exceeds a programmable threshold.
440 source "drivers/thermal/tegra/Kconfig"
442 config QCOM_SPMI_TEMP_ALARM
443 tristate "Qualcomm SPMI PMIC Temperature Alarm"
444 depends on OF && SPMI && IIO
447 This enables a thermal sysfs driver for Qualcomm plug-and-play (QPNP)
448 PMIC devices. It shows up in sysfs as a thermal sensor with multiple
449 trip points. The temperature reported by the thermal sensor reflects the
450 real time die temperature if an ADC is present or an estimate of the
451 temperature based upon the over temperature stage value.
453 config GENERIC_ADC_THERMAL
454 tristate "Generic ADC based thermal sensor"
457 This enabled a thermal sysfs driver for the temperature sensor
458 which is connected to the General Purpose ADC. The ADC channel
459 is read via IIO framework and the channel information is provided
460 to this driver. This driver reports the temperature by reading ADC
461 channel and converts it to temperature based on lookup table.
463 menu "Qualcomm thermal drivers"
464 depends on (ARCH_QCOM && OF) || COMPILE_TEST
465 source "drivers/thermal/qcom/Kconfig"
468 config ZX2967_THERMAL
469 tristate "Thermal sensors on zx2967 SoC"
470 depends on ARCH_ZX || COMPILE_TEST
472 Enable the zx2967 thermal sensors driver, which supports
473 the primitive temperature sensor embedded in zx2967 SoCs.
474 This sensor generates the real time die temperature.
476 config UNIPHIER_THERMAL
477 tristate "Socionext UniPhier thermal driver"
478 depends on ARCH_UNIPHIER || COMPILE_TEST
479 depends on THERMAL_OF && MFD_SYSCON
481 Enable this to plug in UniPhier on-chip PVT thermal driver into the
482 thermal framework. The driver supports CPU thermal zone temperature
483 reporting and a couple of trip points.