]> git.ipfire.org Git - thirdparty/kernel/stable.git/blob - drivers/thermal/Kconfig
Merge branch 'thermal-soc' into next
[thirdparty/kernel/stable.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 MFD_SYSCON
210 depends on OF
211 help
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.
216
217 config MAX77620_THERMAL
218 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
219 depends on MFD_MAX77620
220 depends on OF
221 help
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.
226
227 config QORIQ_THERMAL
228 tristate "QorIQ Thermal Monitoring Unit"
229 depends on THERMAL_OF
230 depends on HAS_IOMEM
231 help
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.
236
237 config SPEAR_THERMAL
238 tristate "SPEAr thermal sensor driver"
239 depends on PLAT_SPEAR || COMPILE_TEST
240 depends on HAS_IOMEM
241 depends on OF
242 help
243 Enable this to plug the SPEAr thermal sensor driver into the Linux
244 thermal framework.
245
246 config ROCKCHIP_THERMAL
247 tristate "Rockchip thermal driver"
248 depends on ARCH_ROCKCHIP || COMPILE_TEST
249 depends on RESET_CONTROLLER
250 depends on HAS_IOMEM
251 help
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.
256
257 config RCAR_THERMAL
258 tristate "Renesas R-Car thermal driver"
259 depends on ARCH_RENESAS || COMPILE_TEST
260 depends on HAS_IOMEM
261 help
262 Enable this to plug the R-Car thermal sensor driver into the Linux
263 thermal framework.
264
265 config RCAR_GEN3_THERMAL
266 tristate "Renesas R-Car Gen3 thermal driver"
267 depends on ARCH_RENESAS || COMPILE_TEST
268 depends on HAS_IOMEM
269 depends on OF
270 help
271 Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
272 thermal framework.
273
274 config KIRKWOOD_THERMAL
275 tristate "Temperature sensor on Marvell Kirkwood SoCs"
276 depends on MACH_KIRKWOOD || COMPILE_TEST
277 depends on HAS_IOMEM
278 depends on OF
279 help
280 Support for the Kirkwood thermal sensor driver into the Linux thermal
281 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
282
283 config DOVE_THERMAL
284 tristate "Temperature sensor on Marvell Dove SoCs"
285 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
286 depends on HAS_IOMEM
287 depends on OF
288 help
289 Support for the Dove thermal sensor driver in the Linux thermal
290 framework.
291
292 config DB8500_THERMAL
293 tristate "DB8500 thermal management"
294 depends on MFD_DB8500_PRCMU
295 default y
296 help
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.
301
302 config ARMADA_THERMAL
303 tristate "Armada 370/XP thermal management"
304 depends on ARCH_MVEBU || COMPILE_TEST
305 depends on HAS_IOMEM
306 depends on OF
307 help
308 Enable this option if you want to have support for thermal management
309 controller present in Armada 370 and Armada XP SoC.
310
311 config DB8500_CPUFREQ_COOLING
312 tristate "DB8500 cpufreq cooling"
313 depends on ARCH_U8500 || COMPILE_TEST
314 depends on HAS_IOMEM
315 depends on CPU_THERMAL
316 default y
317 help
318 Adds DB8500 cpufreq cooling devices, and these cooling devices can be
319 bound to thermal zone trip points. When a trip point reached, the
320 bound cpufreq cooling device turns active to set CPU frequency low to
321 cool down the CPU.
322
323 config DA9062_THERMAL
324 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
325 depends on MFD_DA9062 || COMPILE_TEST
326 depends on OF
327 help
328 Enable this for the Dialog Semiconductor thermal sensor driver.
329 This will report PMIC junction over-temperature for one thermal trip
330 zone.
331 Compatible with the DA9062 and DA9061 PMICs.
332
333 config INTEL_POWERCLAMP
334 tristate "Intel PowerClamp idle injection driver"
335 depends on THERMAL
336 depends on X86
337 depends on CPU_SUP_INTEL
338 help
339 Enable this to enable Intel PowerClamp idle injection driver. This
340 enforce idle time which results in more package C-state residency. The
341 user interface is exposed via generic thermal framework.
342
343 config X86_PKG_TEMP_THERMAL
344 tristate "X86 package temperature thermal driver"
345 depends on X86_THERMAL_VECTOR
346 select THERMAL_GOV_USER_SPACE
347 select THERMAL_WRITABLE_TRIPS
348 default m
349 help
350 Enable this to register CPU digital sensor for package temperature as
351 thermal zone. Each package will have its own thermal zone. There are
352 two trip points which can be set by user to get notifications via thermal
353 notification methods.
354
355 config INTEL_SOC_DTS_IOSF_CORE
356 tristate
357 depends on X86
358 select IOSF_MBI
359 help
360 This is becoming a common feature for Intel SoCs to expose the additional
361 digital temperature sensors (DTSs) using side band interface (IOSF). This
362 implements the common set of helper functions to register, get temperature
363 and get/set thresholds on DTSs.
364
365 config INTEL_SOC_DTS_THERMAL
366 tristate "Intel SoCs DTS thermal driver"
367 depends on X86
368 select INTEL_SOC_DTS_IOSF_CORE
369 select THERMAL_WRITABLE_TRIPS
370 help
371 Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
372 temperature sensor (DTS). These SoCs have two additional DTSs in
373 addition to DTSs on CPU cores. Each DTS will be registered as a
374 thermal zone. There are two trip points. One of the trip point can
375 be set by user mode programs to get notifications via Linux thermal
376 notification methods.The other trip is a critical trip point, which
377 was set by the driver based on the TJ MAX temperature.
378
379 config INTEL_QUARK_DTS_THERMAL
380 tristate "Intel Quark DTS thermal driver"
381 depends on X86_INTEL_QUARK
382 help
383 Enable this to register Intel Quark SoC (e.g. X1000) platform digital
384 temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
385 The DTS will be registered as a thermal zone. There are two trip points:
386 hot & critical. The critical trip point default value is set by
387 underlying BIOS/Firmware.
388
389 menu "ACPI INT340X thermal drivers"
390 source drivers/thermal/int340x_thermal/Kconfig
391 endmenu
392
393 config INTEL_BXT_PMIC_THERMAL
394 tristate "Intel Broxton PMIC thermal driver"
395 depends on X86 && INTEL_SOC_PMIC && REGMAP
396 help
397 Select this driver for Intel Broxton PMIC with ADC channels monitoring
398 system temperature measurements and alerts.
399 This driver is used for monitoring the ADC channels of PMIC and handles
400 the alert trip point interrupts and notifies the thermal framework with
401 the trip point and temperature details of the zone.
402
403 config INTEL_PCH_THERMAL
404 tristate "Intel PCH Thermal Reporting Driver"
405 depends on X86 && PCI
406 help
407 Enable this to support thermal reporting on certain intel PCHs.
408 Thermal reporting device will provide temperature reading,
409 programmable trip points and other information.
410
411 config MTK_THERMAL
412 tristate "Temperature sensor driver for mediatek SoCs"
413 depends on ARCH_MEDIATEK || COMPILE_TEST
414 depends on HAS_IOMEM
415 depends on NVMEM || NVMEM=n
416 depends on RESET_CONTROLLER
417 default y
418 help
419 Enable this option if you want to have support for thermal management
420 controller present in Mediatek SoCs
421
422 menu "Broadcom thermal drivers"
423 depends on ARCH_BCM || COMPILE_TEST
424 source "drivers/thermal/broadcom/Kconfig"
425 endmenu
426
427 menu "Texas Instruments thermal drivers"
428 depends on ARCH_HAS_BANDGAP || COMPILE_TEST
429 depends on HAS_IOMEM
430 source "drivers/thermal/ti-soc-thermal/Kconfig"
431 endmenu
432
433 menu "Samsung thermal drivers"
434 depends on ARCH_EXYNOS || COMPILE_TEST
435 source "drivers/thermal/samsung/Kconfig"
436 endmenu
437
438 menu "STMicroelectronics thermal drivers"
439 depends on ARCH_STI && OF
440 source "drivers/thermal/st/Kconfig"
441 endmenu
442
443 config TANGO_THERMAL
444 tristate "Tango thermal management"
445 depends on ARCH_TANGO || COMPILE_TEST
446 help
447 Enable the Tango thermal driver, which supports the primitive
448 temperature sensor embedded in Tango chips since the SMP8758.
449 This sensor only generates a 1-bit signal to indicate whether
450 the die temperature exceeds a programmable threshold.
451
452 source "drivers/thermal/tegra/Kconfig"
453
454 config QCOM_SPMI_TEMP_ALARM
455 tristate "Qualcomm SPMI PMIC Temperature Alarm"
456 depends on OF && SPMI && IIO
457 select REGMAP_SPMI
458 help
459 This enables a thermal sysfs driver for Qualcomm plug-and-play (QPNP)
460 PMIC devices. It shows up in sysfs as a thermal sensor with multiple
461 trip points. The temperature reported by the thermal sensor reflects the
462 real time die temperature if an ADC is present or an estimate of the
463 temperature based upon the over temperature stage value.
464
465 config GENERIC_ADC_THERMAL
466 tristate "Generic ADC based thermal sensor"
467 depends on IIO
468 help
469 This enabled a thermal sysfs driver for the temperature sensor
470 which is connected to the General Purpose ADC. The ADC channel
471 is read via IIO framework and the channel information is provided
472 to this driver. This driver reports the temperature by reading ADC
473 channel and converts it to temperature based on lookup table.
474
475 menu "Qualcomm thermal drivers"
476 depends on (ARCH_QCOM && OF) || COMPILE_TEST
477 source "drivers/thermal/qcom/Kconfig"
478 endmenu
479
480 config ZX2967_THERMAL
481 tristate "Thermal sensors on zx2967 SoC"
482 depends on ARCH_ZX || COMPILE_TEST
483 help
484 Enable the zx2967 thermal sensors driver, which supports
485 the primitive temperature sensor embedded in zx2967 SoCs.
486 This sensor generates the real time die temperature.
487
488 endif