]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blob - drivers/thermal/Kconfig
thermal: exynos: Reading temperature makes sense only when TMU is turned on
[mirror_ubuntu-bionic-kernel.git] / drivers / thermal / Kconfig
1 #
2 # Generic thermal sysfs drivers configuration
3 #
4
5 menuconfig THERMAL
6 tristate "Generic Thermal sysfs driver"
7 help
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,
12 cooling devices.
13 All platforms with ACPI thermal support can use this driver.
14 If you want this support, you should say Y or M here.
15
16 if THERMAL
17
18 config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
19 int "Emergency poweroff delay in milli-seconds"
20 depends on THERMAL
21 default 0
22 help
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.
32
33 In doubt, leave as 0.
34
35 config THERMAL_HWMON
36 bool
37 prompt "Expose thermal sensors as hwmon device"
38 depends on HWMON=y || HWMON=THERMAL
39 default y
40 help
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.
45
46 Say 'Y' here if you want all thermal sensors to
47 have hwmon sysfs interface too.
48
49 config THERMAL_OF
50 bool
51 prompt "APIs to parse thermal data out of device tree"
52 depends on OF
53 default y
54 help
55 This options provides helpers to add the support to
56 read and parse thermal data definitions out of the
57 device tree blob.
58
59 Say 'Y' here if you need to build thermal infrastructure
60 based on device tree.
61
62 config THERMAL_WRITABLE_TRIPS
63 bool "Enable writable trip points"
64 help
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.
69
70 Say 'Y' here if you would like to allow userspace tools to
71 change trip temperatures.
72
73 choice
74 prompt "Default Thermal governor"
75 default THERMAL_DEFAULT_GOV_STEP_WISE
76 help
77 This option sets which thermal governor shall be loaded at
78 startup. If in doubt, select 'step_wise'.
79
80 config THERMAL_DEFAULT_GOV_STEP_WISE
81 bool "step_wise"
82 select THERMAL_GOV_STEP_WISE
83 help
84 Use the step_wise governor as default. This throttles the
85 devices one step at a time.
86
87 config THERMAL_DEFAULT_GOV_FAIR_SHARE
88 bool "fair_share"
89 select THERMAL_GOV_FAIR_SHARE
90 help
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.
94
95 config THERMAL_DEFAULT_GOV_USER_SPACE
96 bool "user_space"
97 select THERMAL_GOV_USER_SPACE
98 help
99 Select this if you want to let the user space manage the
100 platform thermals.
101
102 config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
103 bool "power_allocator"
104 select THERMAL_GOV_POWER_ALLOCATOR
105 help
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.
109
110 endchoice
111
112 config THERMAL_GOV_FAIR_SHARE
113 bool "Fair-share thermal governor"
114 help
115 Enable this to manage platform thermals using fair-share governor.
116
117 config THERMAL_GOV_STEP_WISE
118 bool "Step_wise thermal governor"
119 help
120 Enable this to manage platform thermals using a simple linear
121 governor.
122
123 config THERMAL_GOV_BANG_BANG
124 bool "Bang Bang thermal governor"
125 default n
126 help
127 Enable this to manage platform thermals using bang bang governor.
128
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).
132
133 config THERMAL_GOV_USER_SPACE
134 bool "User_space thermal governor"
135 help
136 Enable this to let the user space manage the platform thermals.
137
138 config THERMAL_GOV_POWER_ALLOCATOR
139 bool "Power allocator thermal governor"
140 help
141 Enable this to manage platform thermals by dynamically
142 allocating and limiting power to devices.
143
144 config CPU_THERMAL
145 bool "generic cpu cooling support"
146 depends on CPU_FREQ
147 depends on THERMAL_OF
148 help
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.
154
155 If you want this support, you should say Y here.
156
157 config CLOCK_THERMAL
158 bool "Generic clock cooling support"
159 depends on COMMON_CLK
160 depends on PM_OPP
161 help
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.
166
167 config DEVFREQ_THERMAL
168 bool "Generic device cooling support"
169 depends on PM_DEVFREQ
170 depends on PM_OPP
171 help
172 This implements the generic devfreq cooling mechanism through
173 frequency reduction for devices using devfreq.
174
175 This will throttle the device by limiting the maximum allowed DVFS
176 frequency corresponding to the cooling level.
177
178 In order to use the power extensions of the cooling device,
179 devfreq should use the simple_ondemand governor.
180
181 If you want this support, you should say Y here.
182
183 config THERMAL_EMULATION
184 bool "Thermal emulation mode support"
185 help
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.
190
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.
194
195 config HISI_THERMAL
196 tristate "Hisilicon thermal driver"
197 depends on ARCH_HISI || COMPILE_TEST
198 depends on HAS_IOMEM
199 depends on OF
200 default y
201 help
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.
205
206 config IMX_THERMAL
207 tristate "Temperature sensor driver for Freescale i.MX SoCs"
208 depends on (ARCH_MXC && CPU_THERMAL) || COMPILE_TEST
209 depends on NVMEM || !NVMEM
210 depends on MFD_SYSCON
211 depends on OF
212 help
213 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
214 It supports one critical trip point and one passive trip point. The
215 cpufreq is used as the cooling device to throttle CPUs when the
216 passive trip is crossed.
217
218 config MAX77620_THERMAL
219 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
220 depends on MFD_MAX77620
221 depends on OF
222 help
223 Support for die junction temperature warning alarm for Maxim
224 Semiconductor PMIC MAX77620 device. Device generates two alarm
225 interrupts when PMIC die temperature cross the threshold of
226 120 degC and 140 degC.
227
228 config QORIQ_THERMAL
229 tristate "QorIQ Thermal Monitoring Unit"
230 depends on THERMAL_OF
231 depends on HAS_IOMEM
232 help
233 Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
234 It supports one critical trip point and one passive trip point. The
235 cpufreq is used as the cooling device to throttle CPUs when the
236 passive trip is crossed.
237
238 config SPEAR_THERMAL
239 tristate "SPEAr thermal sensor driver"
240 depends on PLAT_SPEAR || COMPILE_TEST
241 depends on HAS_IOMEM
242 depends on OF
243 help
244 Enable this to plug the SPEAr thermal sensor driver into the Linux
245 thermal framework.
246
247 config ROCKCHIP_THERMAL
248 tristate "Rockchip thermal driver"
249 depends on ARCH_ROCKCHIP || COMPILE_TEST
250 depends on RESET_CONTROLLER
251 depends on HAS_IOMEM
252 help
253 Rockchip thermal driver provides support for Temperature sensor
254 ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
255 trip point. Cpufreq is used as the cooling device and will throttle
256 CPUs when the Temperature crosses the passive trip point.
257
258 config RCAR_THERMAL
259 tristate "Renesas R-Car thermal driver"
260 depends on ARCH_RENESAS || COMPILE_TEST
261 depends on HAS_IOMEM
262 help
263 Enable this to plug the R-Car thermal sensor driver into the Linux
264 thermal framework.
265
266 config RCAR_GEN3_THERMAL
267 tristate "Renesas R-Car Gen3 thermal driver"
268 depends on ARCH_RENESAS || COMPILE_TEST
269 depends on HAS_IOMEM
270 depends on OF
271 help
272 Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
273 thermal framework.
274
275 config KIRKWOOD_THERMAL
276 tristate "Temperature sensor on Marvell Kirkwood SoCs"
277 depends on MACH_KIRKWOOD || COMPILE_TEST
278 depends on HAS_IOMEM
279 depends on OF
280 help
281 Support for the Kirkwood thermal sensor driver into the Linux thermal
282 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
283
284 config DOVE_THERMAL
285 tristate "Temperature sensor on Marvell Dove SoCs"
286 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
287 depends on HAS_IOMEM
288 depends on OF
289 help
290 Support for the Dove thermal sensor driver in the Linux thermal
291 framework.
292
293 config DB8500_THERMAL
294 tristate "DB8500 thermal management"
295 depends on MFD_DB8500_PRCMU
296 default y
297 help
298 Adds DB8500 thermal management implementation according to the thermal
299 management framework. A thermal zone with several trip points will be
300 created. Cooling devices can be bound to the trip points to cool this
301 thermal zone if trip points reached.
302
303 config ARMADA_THERMAL
304 tristate "Armada 370/XP thermal management"
305 depends on ARCH_MVEBU || COMPILE_TEST
306 depends on HAS_IOMEM
307 depends on OF
308 help
309 Enable this option if you want to have support for thermal management
310 controller present in Armada 370 and Armada XP SoC.
311
312 config DA9062_THERMAL
313 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
314 depends on MFD_DA9062 || COMPILE_TEST
315 depends on OF
316 help
317 Enable this for the Dialog Semiconductor thermal sensor driver.
318 This will report PMIC junction over-temperature for one thermal trip
319 zone.
320 Compatible with the DA9062 and DA9061 PMICs.
321
322 config INTEL_POWERCLAMP
323 tristate "Intel PowerClamp idle injection driver"
324 depends on THERMAL
325 depends on X86
326 depends on CPU_SUP_INTEL
327 help
328 Enable this to enable Intel PowerClamp idle injection driver. This
329 enforce idle time which results in more package C-state residency. The
330 user interface is exposed via generic thermal framework.
331
332 config X86_PKG_TEMP_THERMAL
333 tristate "X86 package temperature thermal driver"
334 depends on X86_THERMAL_VECTOR
335 select THERMAL_GOV_USER_SPACE
336 select THERMAL_WRITABLE_TRIPS
337 default m
338 help
339 Enable this to register CPU digital sensor for package temperature as
340 thermal zone. Each package will have its own thermal zone. There are
341 two trip points which can be set by user to get notifications via thermal
342 notification methods.
343
344 config INTEL_SOC_DTS_IOSF_CORE
345 tristate
346 depends on X86 && PCI
347 select IOSF_MBI
348 help
349 This is becoming a common feature for Intel SoCs to expose the additional
350 digital temperature sensors (DTSs) using side band interface (IOSF). This
351 implements the common set of helper functions to register, get temperature
352 and get/set thresholds on DTSs.
353
354 config INTEL_SOC_DTS_THERMAL
355 tristate "Intel SoCs DTS thermal driver"
356 depends on X86 && PCI
357 select INTEL_SOC_DTS_IOSF_CORE
358 select THERMAL_WRITABLE_TRIPS
359 help
360 Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
361 temperature sensor (DTS). These SoCs have two additional DTSs in
362 addition to DTSs on CPU cores. Each DTS will be registered as a
363 thermal zone. There are two trip points. One of the trip point can
364 be set by user mode programs to get notifications via Linux thermal
365 notification methods.The other trip is a critical trip point, which
366 was set by the driver based on the TJ MAX temperature.
367
368 config INTEL_QUARK_DTS_THERMAL
369 tristate "Intel Quark DTS thermal driver"
370 depends on X86_INTEL_QUARK
371 help
372 Enable this to register Intel Quark SoC (e.g. X1000) platform digital
373 temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
374 The DTS will be registered as a thermal zone. There are two trip points:
375 hot & critical. The critical trip point default value is set by
376 underlying BIOS/Firmware.
377
378 menu "ACPI INT340X thermal drivers"
379 source drivers/thermal/int340x_thermal/Kconfig
380 endmenu
381
382 config INTEL_BXT_PMIC_THERMAL
383 tristate "Intel Broxton PMIC thermal driver"
384 depends on X86 && INTEL_SOC_PMIC_BXTWC && REGMAP
385 help
386 Select this driver for Intel Broxton PMIC with ADC channels monitoring
387 system temperature measurements and alerts.
388 This driver is used for monitoring the ADC channels of PMIC and handles
389 the alert trip point interrupts and notifies the thermal framework with
390 the trip point and temperature details of the zone.
391
392 config INTEL_PCH_THERMAL
393 tristate "Intel PCH Thermal Reporting Driver"
394 depends on X86 && PCI
395 help
396 Enable this to support thermal reporting on certain intel PCHs.
397 Thermal reporting device will provide temperature reading,
398 programmable trip points and other information.
399
400 config MTK_THERMAL
401 tristate "Temperature sensor driver for mediatek SoCs"
402 depends on ARCH_MEDIATEK || COMPILE_TEST
403 depends on HAS_IOMEM
404 depends on NVMEM || NVMEM=n
405 depends on RESET_CONTROLLER
406 default y
407 help
408 Enable this option if you want to have support for thermal management
409 controller present in Mediatek SoCs
410
411 menu "Broadcom thermal drivers"
412 depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || COMPILE_TEST
413 source "drivers/thermal/broadcom/Kconfig"
414 endmenu
415
416 menu "Texas Instruments thermal drivers"
417 depends on ARCH_HAS_BANDGAP || COMPILE_TEST
418 depends on HAS_IOMEM
419 source "drivers/thermal/ti-soc-thermal/Kconfig"
420 endmenu
421
422 menu "Samsung thermal drivers"
423 depends on ARCH_EXYNOS || COMPILE_TEST
424 source "drivers/thermal/samsung/Kconfig"
425 endmenu
426
427 menu "STMicroelectronics thermal drivers"
428 depends on ARCH_STI && OF
429 source "drivers/thermal/st/Kconfig"
430 endmenu
431
432 config TANGO_THERMAL
433 tristate "Tango thermal management"
434 depends on ARCH_TANGO || COMPILE_TEST
435 help
436 Enable the Tango thermal driver, which supports the primitive
437 temperature sensor embedded in Tango chips since the SMP8758.
438 This sensor only generates a 1-bit signal to indicate whether
439 the die temperature exceeds a programmable threshold.
440
441 source "drivers/thermal/tegra/Kconfig"
442
443 config QCOM_SPMI_TEMP_ALARM
444 tristate "Qualcomm SPMI PMIC Temperature Alarm"
445 depends on OF && SPMI && IIO
446 select REGMAP_SPMI
447 help
448 This enables a thermal sysfs driver for Qualcomm plug-and-play (QPNP)
449 PMIC devices. It shows up in sysfs as a thermal sensor with multiple
450 trip points. The temperature reported by the thermal sensor reflects the
451 real time die temperature if an ADC is present or an estimate of the
452 temperature based upon the over temperature stage value.
453
454 config GENERIC_ADC_THERMAL
455 tristate "Generic ADC based thermal sensor"
456 depends on IIO
457 help
458 This enabled a thermal sysfs driver for the temperature sensor
459 which is connected to the General Purpose ADC. The ADC channel
460 is read via IIO framework and the channel information is provided
461 to this driver. This driver reports the temperature by reading ADC
462 channel and converts it to temperature based on lookup table.
463
464 menu "Qualcomm thermal drivers"
465 depends on (ARCH_QCOM && OF) || COMPILE_TEST
466 source "drivers/thermal/qcom/Kconfig"
467 endmenu
468
469 config ZX2967_THERMAL
470 tristate "Thermal sensors on zx2967 SoC"
471 depends on ARCH_ZX || COMPILE_TEST
472 help
473 Enable the zx2967 thermal sensors driver, which supports
474 the primitive temperature sensor embedded in zx2967 SoCs.
475 This sensor generates the real time die temperature.
476
477 config UNIPHIER_THERMAL
478 tristate "Socionext UniPhier thermal driver"
479 depends on ARCH_UNIPHIER || COMPILE_TEST
480 depends on THERMAL_OF && MFD_SYSCON
481 help
482 Enable this to plug in UniPhier on-chip PVT thermal driver into the
483 thermal framework. The driver supports CPU thermal zone temperature
484 reporting and a couple of trip points.
485 endif