Loading...
1#
2# Generic thermal sysfs drivers configuration
3#
4
5menuconfig 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
16if THERMAL
17
18config THERMAL_HWMON
19 bool
20 prompt "Expose thermal sensors as hwmon device"
21 depends on HWMON=y || HWMON=THERMAL
22 default y
23 help
24 In case a sensor is registered with the thermal
25 framework, this option will also register it
26 as a hwmon. The sensor will then have the common
27 hwmon sysfs interface.
28
29 Say 'Y' here if you want all thermal sensors to
30 have hwmon sysfs interface too.
31
32config THERMAL_OF
33 bool
34 prompt "APIs to parse thermal data out of device tree"
35 depends on OF
36 default y
37 help
38 This options provides helpers to add the support to
39 read and parse thermal data definitions out of the
40 device tree blob.
41
42 Say 'Y' here if you need to build thermal infrastructure
43 based on device tree.
44
45choice
46 prompt "Default Thermal governor"
47 default THERMAL_DEFAULT_GOV_STEP_WISE
48 help
49 This option sets which thermal governor shall be loaded at
50 startup. If in doubt, select 'step_wise'.
51
52config THERMAL_DEFAULT_GOV_STEP_WISE
53 bool "step_wise"
54 select THERMAL_GOV_STEP_WISE
55 help
56 Use the step_wise governor as default. This throttles the
57 devices one step at a time.
58
59config THERMAL_DEFAULT_GOV_FAIR_SHARE
60 bool "fair_share"
61 select THERMAL_GOV_FAIR_SHARE
62 help
63 Use the fair_share governor as default. This throttles the
64 devices based on their 'contribution' to a zone. The
65 contribution should be provided through platform data.
66
67config THERMAL_DEFAULT_GOV_USER_SPACE
68 bool "user_space"
69 select THERMAL_GOV_USER_SPACE
70 help
71 Select this if you want to let the user space manage the
72 platform thermals.
73
74endchoice
75
76config THERMAL_GOV_FAIR_SHARE
77 bool "Fair-share thermal governor"
78 help
79 Enable this to manage platform thermals using fair-share governor.
80
81config THERMAL_GOV_STEP_WISE
82 bool "Step_wise thermal governor"
83 help
84 Enable this to manage platform thermals using a simple linear
85 governor.
86
87config THERMAL_GOV_USER_SPACE
88 bool "User_space thermal governor"
89 help
90 Enable this to let the user space manage the platform thermals.
91
92config CPU_THERMAL
93 bool "generic cpu cooling support"
94 depends on CPU_FREQ
95 depends on THERMAL_OF
96 help
97 This implements the generic cpu cooling mechanism through frequency
98 reduction. An ACPI version of this already exists
99 (drivers/acpi/processor_thermal.c).
100 This will be useful for platforms using the generic thermal interface
101 and not the ACPI interface.
102
103 If you want this support, you should say Y here.
104
105config THERMAL_EMULATION
106 bool "Thermal emulation mode support"
107 help
108 Enable this option to make a emul_temp sysfs node in thermal zone
109 directory to support temperature emulation. With emulation sysfs node,
110 user can manually input temperature and test the different trip
111 threshold behaviour for simulation purpose.
112
113 WARNING: Be careful while enabling this option on production systems,
114 because userland can easily disable the thermal policy by simply
115 flooding this sysfs node with low temperature values.
116
117config IMX_THERMAL
118 tristate "Temperature sensor driver for Freescale i.MX SoCs"
119 depends on CPU_THERMAL
120 depends on MFD_SYSCON
121 depends on OF
122 help
123 Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
124 It supports one critical trip point and one passive trip point. The
125 cpufreq is used as the cooling device to throttle CPUs when the
126 passive trip is crossed.
127
128config SPEAR_THERMAL
129 bool "SPEAr thermal sensor driver"
130 depends on PLAT_SPEAR
131 depends on OF
132 help
133 Enable this to plug the SPEAr thermal sensor driver into the Linux
134 thermal framework.
135
136config RCAR_THERMAL
137 tristate "Renesas R-Car thermal driver"
138 depends on ARCH_SHMOBILE || COMPILE_TEST
139 depends on HAS_IOMEM
140 help
141 Enable this to plug the R-Car thermal sensor driver into the Linux
142 thermal framework.
143
144config KIRKWOOD_THERMAL
145 tristate "Temperature sensor on Marvell Kirkwood SoCs"
146 depends on ARCH_KIRKWOOD || MACH_KIRKWOOD
147 depends on OF
148 help
149 Support for the Kirkwood thermal sensor driver into the Linux thermal
150 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
151
152config DOVE_THERMAL
153 tristate "Temperature sensor on Marvell Dove SoCs"
154 depends on ARCH_DOVE
155 depends on OF
156 help
157 Support for the Dove thermal sensor driver in the Linux thermal
158 framework.
159
160config DB8500_THERMAL
161 bool "DB8500 thermal management"
162 depends on ARCH_U8500
163 default y
164 help
165 Adds DB8500 thermal management implementation according to the thermal
166 management framework. A thermal zone with several trip points will be
167 created. Cooling devices can be bound to the trip points to cool this
168 thermal zone if trip points reached.
169
170config ARMADA_THERMAL
171 tristate "Armada 370/XP thermal management"
172 depends on ARCH_MVEBU
173 depends on OF
174 help
175 Enable this option if you want to have support for thermal management
176 controller present in Armada 370 and Armada XP SoC.
177
178config DB8500_CPUFREQ_COOLING
179 tristate "DB8500 cpufreq cooling"
180 depends on ARCH_U8500
181 depends on CPU_THERMAL
182 default y
183 help
184 Adds DB8500 cpufreq cooling devices, and these cooling devices can be
185 bound to thermal zone trip points. When a trip point reached, the
186 bound cpufreq cooling device turns active to set CPU frequency low to
187 cool down the CPU.
188
189config INTEL_POWERCLAMP
190 tristate "Intel PowerClamp idle injection driver"
191 depends on THERMAL
192 depends on X86
193 depends on CPU_SUP_INTEL
194 help
195 Enable this to enable Intel PowerClamp idle injection driver. This
196 enforce idle time which results in more package C-state residency. The
197 user interface is exposed via generic thermal framework.
198
199config X86_PKG_TEMP_THERMAL
200 tristate "X86 package temperature thermal driver"
201 depends on X86_THERMAL_VECTOR
202 select THERMAL_GOV_USER_SPACE
203 default m
204 help
205 Enable this to register CPU digital sensor for package temperature as
206 thermal zone. Each package will have its own thermal zone. There are
207 two trip points which can be set by user to get notifications via thermal
208 notification methods.
209
210config ACPI_INT3403_THERMAL
211 tristate "ACPI INT3403 thermal driver"
212 depends on X86 && ACPI
213 help
214 Newer laptops and tablets that use ACPI may have thermal sensors
215 outside the core CPU/SOC for thermal safety reasons. These
216 temperature sensors are also exposed for the OS to use via the so
217 called INT3403 ACPI object. This driver will, on devices that have
218 such sensors, expose the temperature information from these sensors
219 to userspace via the normal thermal framework. This means that a wide
220 range of applications and GUI widgets can show this information to
221 the user or use this information for making decisions. For example,
222 the Intel Thermal Daemon can use this information to allow the user
223 to select his laptop to run without turning on the fans.
224
225menu "Texas Instruments thermal drivers"
226source "drivers/thermal/ti-soc-thermal/Kconfig"
227endmenu
228
229menu "Samsung thermal drivers"
230depends on PLAT_SAMSUNG
231source "drivers/thermal/samsung/Kconfig"
232endmenu
233
234endif
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Generic thermal sysfs drivers configuration
4#
5
6menuconfig THERMAL
7 bool "Generic Thermal sysfs driver"
8 help
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,
13 cooling devices.
14 All platforms with ACPI thermal support can use this driver.
15 If you want this support, you should say Y here.
16
17if THERMAL
18
19config THERMAL_STATISTICS
20 bool "Thermal state transition statistics"
21 help
22 Export thermal state transition statistics information through sysfs.
23
24 If in doubt, say N.
25
26config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
27 int "Emergency poweroff delay in milli-seconds"
28 default 0
29 help
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.
39
40 In doubt, leave as 0.
41
42config THERMAL_HWMON
43 bool
44 prompt "Expose thermal sensors as hwmon device"
45 depends on HWMON=y || HWMON=THERMAL
46 default y
47 help
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.
52
53 Say 'Y' here if you want all thermal sensors to
54 have hwmon sysfs interface too.
55
56config THERMAL_OF
57 bool
58 prompt "APIs to parse thermal data out of device tree"
59 depends on OF
60 default y
61 help
62 This options provides helpers to add the support to
63 read and parse thermal data definitions out of the
64 device tree blob.
65
66 Say 'Y' here if you need to build thermal infrastructure
67 based on device tree.
68
69config THERMAL_WRITABLE_TRIPS
70 bool "Enable writable trip points"
71 help
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.
76
77 Say 'Y' here if you would like to allow userspace tools to
78 change trip temperatures.
79
80choice
81 prompt "Default Thermal governor"
82 default THERMAL_DEFAULT_GOV_STEP_WISE
83 help
84 This option sets which thermal governor shall be loaded at
85 startup. If in doubt, select 'step_wise'.
86
87config THERMAL_DEFAULT_GOV_STEP_WISE
88 bool "step_wise"
89 select THERMAL_GOV_STEP_WISE
90 help
91 Use the step_wise governor as default. This throttles the
92 devices one step at a time.
93
94config THERMAL_DEFAULT_GOV_FAIR_SHARE
95 bool "fair_share"
96 select THERMAL_GOV_FAIR_SHARE
97 help
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.
101
102config THERMAL_DEFAULT_GOV_USER_SPACE
103 bool "user_space"
104 select THERMAL_GOV_USER_SPACE
105 help
106 Select this if you want to let the user space manage the
107 platform thermals.
108
109config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
110 bool "power_allocator"
111 select THERMAL_GOV_POWER_ALLOCATOR
112 help
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.
116
117endchoice
118
119config THERMAL_GOV_FAIR_SHARE
120 bool "Fair-share thermal governor"
121 help
122 Enable this to manage platform thermals using fair-share governor.
123
124config THERMAL_GOV_STEP_WISE
125 bool "Step_wise thermal governor"
126 help
127 Enable this to manage platform thermals using a simple linear
128 governor.
129
130config THERMAL_GOV_BANG_BANG
131 bool "Bang Bang thermal governor"
132 default n
133 help
134 Enable this to manage platform thermals using bang bang governor.
135
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).
139
140config THERMAL_GOV_USER_SPACE
141 bool "User_space thermal governor"
142 help
143 Enable this to let the user space manage the platform thermals.
144
145config THERMAL_GOV_POWER_ALLOCATOR
146 bool "Power allocator thermal governor"
147 help
148 Enable this to manage platform thermals by dynamically
149 allocating and limiting power to devices.
150
151config CPU_THERMAL
152 bool "Generic cpu cooling support"
153 depends on CPU_FREQ
154 depends on THERMAL_OF
155 help
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.
161
162 If you want this support, you should say Y here.
163
164config CLOCK_THERMAL
165 bool "Generic clock cooling support"
166 depends on COMMON_CLK
167 depends on PM_OPP
168 help
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.
173
174config DEVFREQ_THERMAL
175 bool "Generic device cooling support"
176 depends on PM_DEVFREQ
177 depends on PM_OPP
178 help
179 This implements the generic devfreq cooling mechanism through
180 frequency reduction for devices using devfreq.
181
182 This will throttle the device by limiting the maximum allowed DVFS
183 frequency corresponding to the cooling level.
184
185 In order to use the power extensions of the cooling device,
186 devfreq should use the simple_ondemand governor.
187
188 If you want this support, you should say Y here.
189
190config THERMAL_EMULATION
191 bool "Thermal emulation mode support"
192 help
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.
197
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.
201
202config THERMAL_MMIO
203 tristate "Generic Thermal MMIO driver"
204 depends on OF || COMPILE_TEST
205 depends on HAS_IOMEM
206 help
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
211 driver.
212
213config HISI_THERMAL
214 tristate "Hisilicon thermal driver"
215 depends on ARCH_HISI || COMPILE_TEST
216 depends on HAS_IOMEM
217 depends on OF
218 default y
219 help
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.
223
224config IMX_THERMAL
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
229 depends on OF
230 help
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.
235
236config MAX77620_THERMAL
237 tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
238 depends on MFD_MAX77620
239 depends on OF
240 help
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.
245
246config QORIQ_THERMAL
247 tristate "QorIQ Thermal Monitoring Unit"
248 depends on THERMAL_OF
249 depends on HAS_IOMEM
250 help
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.
255
256config SPEAR_THERMAL
257 tristate "SPEAr thermal sensor driver"
258 depends on PLAT_SPEAR || COMPILE_TEST
259 depends on HAS_IOMEM
260 depends on OF
261 help
262 Enable this to plug the SPEAr thermal sensor driver into the Linux
263 thermal framework.
264
265config ROCKCHIP_THERMAL
266 tristate "Rockchip thermal driver"
267 depends on ARCH_ROCKCHIP || COMPILE_TEST
268 depends on RESET_CONTROLLER
269 depends on HAS_IOMEM
270 help
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.
275
276config RCAR_THERMAL
277 tristate "Renesas R-Car thermal driver"
278 depends on ARCH_RENESAS || COMPILE_TEST
279 depends on HAS_IOMEM
280 help
281 Enable this to plug the R-Car thermal sensor driver into the Linux
282 thermal framework.
283
284config RCAR_GEN3_THERMAL
285 tristate "Renesas R-Car Gen3 thermal driver"
286 depends on ARCH_RENESAS || COMPILE_TEST
287 depends on HAS_IOMEM
288 depends on OF
289 help
290 Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
291 thermal framework.
292
293config KIRKWOOD_THERMAL
294 tristate "Temperature sensor on Marvell Kirkwood SoCs"
295 depends on MACH_KIRKWOOD || COMPILE_TEST
296 depends on HAS_IOMEM
297 depends on OF
298 help
299 Support for the Kirkwood thermal sensor driver into the Linux thermal
300 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
301
302config DOVE_THERMAL
303 tristate "Temperature sensor on Marvell Dove SoCs"
304 depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
305 depends on HAS_IOMEM
306 depends on OF
307 help
308 Support for the Dove thermal sensor driver in the Linux thermal
309 framework.
310
311config DB8500_THERMAL
312 tristate "DB8500 thermal management"
313 depends on MFD_DB8500_PRCMU && OF
314 default y
315 help
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.
320
321config ARMADA_THERMAL
322 tristate "Marvell EBU Armada SoCs thermal management"
323 depends on ARCH_MVEBU || COMPILE_TEST
324 depends on HAS_IOMEM
325 depends on OF
326 help
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).
329
330config DA9062_THERMAL
331 tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
332 depends on MFD_DA9062 || COMPILE_TEST
333 depends on OF
334 help
335 Enable this for the Dialog Semiconductor thermal sensor driver.
336 This will report PMIC junction over-temperature for one thermal trip
337 zone.
338 Compatible with the DA9062 and DA9061 PMICs.
339
340config MTK_THERMAL
341 tristate "Temperature sensor driver for mediatek SoCs"
342 depends on ARCH_MEDIATEK || COMPILE_TEST
343 depends on HAS_IOMEM
344 depends on NVMEM || NVMEM=n
345 depends on RESET_CONTROLLER
346 default y
347 help
348 Enable this option if you want to have support for thermal management
349 controller present in Mediatek SoCs
350
351menu "Intel thermal drivers"
352depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
353source "drivers/thermal/intel/Kconfig"
354endmenu
355
356menu "Broadcom thermal drivers"
357depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
358 COMPILE_TEST
359source "drivers/thermal/broadcom/Kconfig"
360endmenu
361
362menu "Texas Instruments thermal drivers"
363depends on ARCH_HAS_BANDGAP || COMPILE_TEST
364depends on HAS_IOMEM
365source "drivers/thermal/ti-soc-thermal/Kconfig"
366endmenu
367
368menu "Samsung thermal drivers"
369depends on ARCH_EXYNOS || COMPILE_TEST
370source "drivers/thermal/samsung/Kconfig"
371endmenu
372
373menu "STMicroelectronics thermal drivers"
374depends on (ARCH_STI || ARCH_STM32) && OF
375source "drivers/thermal/st/Kconfig"
376endmenu
377
378config TANGO_THERMAL
379 tristate "Tango thermal management"
380 depends on ARCH_TANGO || COMPILE_TEST
381 help
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.
386
387source "drivers/thermal/tegra/Kconfig"
388
389config GENERIC_ADC_THERMAL
390 tristate "Generic ADC based thermal sensor"
391 depends on IIO
392 help
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.
398
399menu "Qualcomm thermal drivers"
400depends on (ARCH_QCOM && OF) || COMPILE_TEST
401source "drivers/thermal/qcom/Kconfig"
402endmenu
403
404config ZX2967_THERMAL
405 tristate "Thermal sensors on zx2967 SoC"
406 depends on ARCH_ZX || COMPILE_TEST
407 help
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.
411
412config UNIPHIER_THERMAL
413 tristate "Socionext UniPhier thermal driver"
414 depends on ARCH_UNIPHIER || COMPILE_TEST
415 depends on THERMAL_OF && MFD_SYSCON
416 help
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.
420endif