xref: /linux/drivers/thermal/Kconfig (revision 4f3c8320c78cdd11c8fdd23c33787407f719322e)
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Generic thermal drivers configuration
4#
5
6menuconfig THERMAL
7	bool "Thermal drivers"
8	help
9	  Thermal drivers offer a generic mechanism for
10	  thermal management. Usually it's made up of one or more thermal
11	  zones and cooling devices.
12	  Each thermal zone contains its own temperature, trip points,
13	  and cooling devices.
14	  All platforms with ACPI or Open Firmware thermal support can use
15	  this driver.
16	  If you want this support, you should say Y here.
17
18if THERMAL
19
20config THERMAL_NETLINK
21	bool "Thermal netlink management"
22	depends on NET
23	help
24	  The thermal framework has a netlink interface to do thermal
25	  zones discovery, temperature readings and events such as
26	  trip point crossed, cooling device update or governor
27	  change. It is recommended to enable the feature.
28
29config THERMAL_STATISTICS
30	bool "Thermal state transition statistics"
31	help
32	  Export thermal state transition statistics information through sysfs.
33
34	  If in doubt, say N.
35
36config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
37	int "Emergency poweroff delay in milli-seconds"
38	default 0
39	help
40	  Thermal subsystem will issue a graceful shutdown when
41	  critical temperatures are reached using orderly_poweroff(). In
42	  case of failure of an orderly_poweroff(), the thermal emergency
43	  poweroff kicks in after a delay has elapsed and shuts down the system.
44	  This config is number of milliseconds to delay before emergency
45	  poweroff kicks in. Similarly to the critical trip point,
46	  the delay should be carefully profiled so as to give adequate
47	  time for orderly_poweroff() to finish on regular execution.
48	  If set to 0 emergency poweroff will not be supported.
49
50	  In doubt, leave as 0.
51
52config THERMAL_HWMON
53	bool
54	prompt "Expose thermal sensors as hwmon device"
55	depends on HWMON=y || HWMON=THERMAL
56	default y
57	help
58	  In case a sensor is registered with the thermal
59	  framework, this option will also register it
60	  as a hwmon. The sensor will then have the common
61	  hwmon sysfs interface.
62
63	  Say 'Y' here if you want all thermal sensors to
64	  have hwmon sysfs interface too.
65
66config THERMAL_OF
67	bool
68	prompt "APIs to parse thermal data out of device tree"
69	depends on OF
70	default y
71	help
72	  This options provides helpers to add the support to
73	  read and parse thermal data definitions out of the
74	  device tree blob.
75
76	  Say 'Y' here if you need to build thermal infrastructure
77	  based on device tree.
78
79config THERMAL_WRITABLE_TRIPS
80	bool "Enable writable trip points"
81	help
82	  This option allows the system integrator to choose whether
83	  trip temperatures can be changed from userspace. The
84	  writable trips need to be specified when setting up the
85	  thermal zone but the choice here takes precedence.
86
87	  Say 'Y' here if you would like to allow userspace tools to
88	  change trip temperatures.
89
90choice
91	prompt "Default Thermal governor"
92	default THERMAL_DEFAULT_GOV_STEP_WISE
93	help
94	  This option sets which thermal governor shall be loaded at
95	  startup. If in doubt, select 'step_wise'.
96
97config THERMAL_DEFAULT_GOV_STEP_WISE
98	bool "step_wise"
99	select THERMAL_GOV_STEP_WISE
100	help
101	  Use the step_wise governor as default. This throttles the
102	  devices one step at a time.
103
104config THERMAL_DEFAULT_GOV_FAIR_SHARE
105	bool "fair_share"
106	select THERMAL_GOV_FAIR_SHARE
107	help
108	  Use the fair_share governor as default. This throttles the
109	  devices based on their 'contribution' to a zone. The
110	  contribution should be provided through platform data.
111
112config THERMAL_DEFAULT_GOV_USER_SPACE
113	bool "user_space"
114	select THERMAL_GOV_USER_SPACE
115	help
116	  Select this if you want to let the user space manage the
117	  platform thermals.
118
119config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
120	bool "power_allocator"
121	depends on THERMAL_GOV_POWER_ALLOCATOR
122	help
123	  Select this if you want to control temperature based on
124	  system and device power allocation. This governor can only
125	  operate on cooling devices that implement the power API.
126
127endchoice
128
129config THERMAL_GOV_FAIR_SHARE
130	bool "Fair-share thermal governor"
131	help
132	  Enable this to manage platform thermals using fair-share governor.
133
134config THERMAL_GOV_STEP_WISE
135	bool "Step_wise thermal governor"
136	help
137	  Enable this to manage platform thermals using a simple linear
138	  governor.
139
140config THERMAL_GOV_BANG_BANG
141	bool "Bang Bang thermal governor"
142	default n
143	help
144	  Enable this to manage platform thermals using bang bang governor.
145
146	  Say 'Y' here if you want to use two point temperature regulation
147	  used for fans without throttling.  Some fan drivers depend on this
148	  governor to be enabled (e.g. acerhdf).
149
150config THERMAL_GOV_USER_SPACE
151	bool "User_space thermal governor"
152	help
153	  Enable this to let the user space manage the platform thermals.
154
155config THERMAL_GOV_POWER_ALLOCATOR
156	bool "Power allocator thermal governor"
157	depends on ENERGY_MODEL
158	help
159	  Enable this to manage platform thermals by dynamically
160	  allocating and limiting power to devices.
161
162config CPU_THERMAL
163	bool "Generic cpu cooling support"
164	depends on THERMAL_OF
165	help
166	  Enable the CPU cooling features. If the system has no active
167	  cooling device available, this option allows to use the CPU
168	  as a cooling device.
169
170if CPU_THERMAL
171
172config CPU_FREQ_THERMAL
173	bool "CPU frequency cooling device"
174	depends on CPU_FREQ
175	default y
176	help
177	  This implements the generic cpu cooling mechanism through frequency
178	  reduction. An ACPI version of this already exists
179	  (drivers/acpi/processor_thermal.c).
180	  This will be useful for platforms using the generic thermal interface
181	  and not the ACPI interface.
182
183config CPU_IDLE_THERMAL
184	bool "CPU idle cooling device"
185	depends on IDLE_INJECT
186	help
187	  This implements the CPU cooling mechanism through
188	  idle injection. This will throttle the CPU by injecting
189	  idle cycle.
190endif
191
192config DEVFREQ_THERMAL
193	bool "Generic device cooling support"
194	depends on PM_DEVFREQ
195	depends on PM_OPP
196	help
197	  This implements the generic devfreq cooling mechanism through
198	  frequency reduction for devices using devfreq.
199
200	  This will throttle the device by limiting the maximum allowed DVFS
201	  frequency corresponding to the cooling level.
202
203	  In order to use the power extensions of the cooling device,
204	  devfreq should use the simple_ondemand governor.
205
206	  If you want this support, you should say Y here.
207
208config THERMAL_EMULATION
209	bool "Thermal emulation mode support"
210	help
211	  Enable this option to make a emul_temp sysfs node in thermal zone
212	  directory to support temperature emulation. With emulation sysfs node,
213	  user can manually input temperature and test the different trip
214	  threshold behaviour for simulation purpose.
215
216	  WARNING: Be careful while enabling this option on production systems,
217	  because userland can easily disable the thermal policy by simply
218	  flooding this sysfs node with low temperature values.
219
220config THERMAL_MMIO
221	tristate "Generic Thermal MMIO driver"
222	depends on OF || COMPILE_TEST
223	depends on HAS_IOMEM
224	help
225	  This option enables the generic thermal MMIO driver that will use
226	  memory-mapped reads to get the temperature.  Any HW/System that
227	  allows temperature reading by a single memory-mapped reading, be it
228	  register or shared memory, is a potential candidate to work with this
229	  driver.
230
231config HISI_THERMAL
232	tristate "Hisilicon thermal driver"
233	depends on ARCH_HISI || COMPILE_TEST
234	depends on HAS_IOMEM
235	depends on OF
236	default y
237	help
238	  Enable this to plug hisilicon's thermal sensor driver into the Linux
239	  thermal framework. cpufreq is used as the cooling device to throttle
240	  CPUs when the passive trip is crossed.
241
242config IMX_THERMAL
243	tristate "Temperature sensor driver for Freescale i.MX SoCs"
244	depends on ARCH_MXC || COMPILE_TEST
245	depends on NVMEM || !NVMEM
246	depends on MFD_SYSCON
247	depends on OF
248	help
249	  Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
250	  It supports one critical trip point and one passive trip point.  The
251	  cpufreq is used as the cooling device to throttle CPUs when the
252	  passive trip is crossed.
253
254config IMX_SC_THERMAL
255	tristate "Temperature sensor driver for NXP i.MX SoCs with System Controller"
256	depends on IMX_SCU
257	depends on OF
258	help
259	  Support for Temperature Monitor (TEMPMON) found on NXP i.MX SoCs with
260	  system controller inside, Linux kernel has to communicate with system
261	  controller via MU (message unit) IPC to get temperature from thermal
262	  sensor. It supports one critical trip point and one
263	  passive trip point for each thermal sensor.
264
265config IMX8MM_THERMAL
266	tristate "Temperature sensor driver for Freescale i.MX8MM SoC"
267	depends on ARCH_MXC || COMPILE_TEST
268	depends on OF
269	help
270	  Support for Thermal Monitoring Unit (TMU) found on Freescale i.MX8MM SoC.
271	  It supports one critical trip point and one passive trip point. The
272	  cpufreq is used as the cooling device to throttle CPUs when the passive
273	  trip is crossed.
274
275config K3_THERMAL
276	tristate "Texas Instruments K3 thermal support"
277	depends on ARCH_K3 || COMPILE_TEST
278	help
279	  If you say yes here you get thermal support for the Texas Instruments
280	  K3 SoC family. The current chip supported is:
281	  - AM654
282
283	  This includes temperature reading functionality.
284
285config MAX77620_THERMAL
286	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
287	depends on MFD_MAX77620
288	depends on OF
289	help
290	  Support for die junction temperature warning alarm for Maxim
291	  Semiconductor PMIC MAX77620 device. Device generates two alarm
292	  interrupts when PMIC die temperature cross the threshold of
293	  120 degC and 140 degC.
294
295config QORIQ_THERMAL
296	tristate "QorIQ Thermal Monitoring Unit"
297	depends on THERMAL_OF && HAS_IOMEM
298	depends on PPC_E500MC || SOC_LS1021A || ARCH_LAYERSCAPE || (ARCH_MXC && ARM64) || COMPILE_TEST
299	select REGMAP_MMIO
300	help
301	  Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
302	  It supports one critical trip point and one passive trip point. The
303	  cpufreq is used as the cooling device to throttle CPUs when the
304	  passive trip is crossed.
305
306config SPEAR_THERMAL
307	tristate "SPEAr thermal sensor driver"
308	depends on PLAT_SPEAR || COMPILE_TEST
309	depends on HAS_IOMEM
310	depends on OF
311	help
312	  Enable this to plug the SPEAr thermal sensor driver into the Linux
313	  thermal framework.
314
315config SUN8I_THERMAL
316	tristate "Allwinner sun8i thermal driver"
317	depends on ARCH_SUNXI || COMPILE_TEST
318	depends on HAS_IOMEM
319	depends on NVMEM
320	depends on OF
321	depends on RESET_CONTROLLER
322	help
323	  Support for the sun8i thermal sensor driver into the Linux thermal
324	  framework.
325
326	  To compile this driver as a module, choose M here: the
327	  module will be called sun8i-thermal.
328
329config ROCKCHIP_THERMAL
330	tristate "Rockchip thermal driver"
331	depends on ARCH_ROCKCHIP || COMPILE_TEST
332	depends on RESET_CONTROLLER
333	depends on HAS_IOMEM
334	help
335	  Rockchip thermal driver provides support for Temperature sensor
336	  ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
337	  trip point. Cpufreq is used as the cooling device and will throttle
338	  CPUs when the Temperature crosses the passive trip point.
339
340config RCAR_THERMAL
341	tristate "Renesas R-Car thermal driver"
342	depends on ARCH_RENESAS || COMPILE_TEST
343	depends on HAS_IOMEM
344	help
345	  Enable this to plug the R-Car thermal sensor driver into the Linux
346	  thermal framework.
347
348config RCAR_GEN3_THERMAL
349	tristate "Renesas R-Car Gen3 and RZ/G2 thermal driver"
350	depends on ARCH_RENESAS || COMPILE_TEST
351	depends on HAS_IOMEM
352	depends on OF
353	help
354	  Enable this to plug the R-Car Gen3 or RZ/G2 thermal sensor driver into
355	  the Linux thermal framework.
356
357config KIRKWOOD_THERMAL
358	tristate "Temperature sensor on Marvell Kirkwood SoCs"
359	depends on MACH_KIRKWOOD || COMPILE_TEST
360	depends on HAS_IOMEM
361	depends on OF
362	help
363	  Support for the Kirkwood thermal sensor driver into the Linux thermal
364	  framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
365
366config DOVE_THERMAL
367	tristate "Temperature sensor on Marvell Dove SoCs"
368	depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
369	depends on HAS_IOMEM
370	depends on OF
371	help
372	  Support for the Dove thermal sensor driver in the Linux thermal
373	  framework.
374
375config DB8500_THERMAL
376	tristate "DB8500 thermal management"
377	depends on MFD_DB8500_PRCMU && OF
378	default y
379	help
380	  Adds DB8500 thermal management implementation according to the thermal
381	  management framework. A thermal zone with several trip points will be
382	  created. Cooling devices can be bound to the trip points to cool this
383	  thermal zone if trip points reached.
384
385config ARMADA_THERMAL
386	tristate "Marvell EBU Armada SoCs thermal management"
387	depends on ARCH_MVEBU || COMPILE_TEST
388	depends on HAS_IOMEM
389	depends on OF
390	help
391	  Enable this option if you want to have support for thermal management
392	  controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
393
394config DA9062_THERMAL
395	tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
396	depends on MFD_DA9062 || COMPILE_TEST
397	depends on OF
398	help
399	  Enable this for the Dialog Semiconductor thermal sensor driver.
400	  This will report PMIC junction over-temperature for one thermal trip
401	  zone.
402	  Compatible with the DA9062 and DA9061 PMICs.
403
404config MTK_THERMAL
405	tristate "Temperature sensor driver for mediatek SoCs"
406	depends on ARCH_MEDIATEK || COMPILE_TEST
407	depends on HAS_IOMEM
408	depends on NVMEM || NVMEM=n
409	depends on RESET_CONTROLLER
410	default y
411	help
412	  Enable this option if you want to have support for thermal management
413	  controller present in Mediatek SoCs
414
415config AMLOGIC_THERMAL
416	tristate "Amlogic Thermal Support"
417	default ARCH_MESON
418	depends on OF && ARCH_MESON
419	help
420	  If you say yes here you get support for Amlogic Thermal
421	  for G12 SoC Family.
422
423	  This driver can also be built as a module. If so, the module will
424	  be called amlogic_thermal.
425
426menu "Intel thermal drivers"
427depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
428source "drivers/thermal/intel/Kconfig"
429endmenu
430
431menu "Broadcom thermal drivers"
432depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
433		COMPILE_TEST
434source "drivers/thermal/broadcom/Kconfig"
435endmenu
436
437menu "Texas Instruments thermal drivers"
438depends on ARCH_HAS_BANDGAP || COMPILE_TEST
439depends on HAS_IOMEM
440source "drivers/thermal/ti-soc-thermal/Kconfig"
441endmenu
442
443menu "Samsung thermal drivers"
444depends on ARCH_EXYNOS || COMPILE_TEST
445source "drivers/thermal/samsung/Kconfig"
446endmenu
447
448menu "STMicroelectronics thermal drivers"
449depends on (ARCH_STI || ARCH_STM32) && OF
450source "drivers/thermal/st/Kconfig"
451endmenu
452
453config TANGO_THERMAL
454	tristate "Tango thermal management"
455	depends on ARCH_TANGO || COMPILE_TEST
456	help
457	  Enable the Tango thermal driver, which supports the primitive
458	  temperature sensor embedded in Tango chips since the SMP8758.
459	  This sensor only generates a 1-bit signal to indicate whether
460	  the die temperature exceeds a programmable threshold.
461
462source "drivers/thermal/tegra/Kconfig"
463
464config GENERIC_ADC_THERMAL
465	tristate "Generic ADC based thermal sensor"
466	depends on IIO
467	help
468	  This enabled a thermal sysfs driver for the temperature sensor
469	  which is connected to the General Purpose ADC. The ADC channel
470	  is read via IIO framework and the channel information is provided
471	  to this driver. This driver reports the temperature by reading ADC
472	  channel and converts it to temperature based on lookup table.
473
474menu "Qualcomm thermal drivers"
475depends on (ARCH_QCOM && OF) || COMPILE_TEST
476source "drivers/thermal/qcom/Kconfig"
477endmenu
478
479config ZX2967_THERMAL
480	tristate "Thermal sensors on zx2967 SoC"
481	depends on ARCH_ZX || COMPILE_TEST
482	help
483	  Enable the zx2967 thermal sensors driver, which supports
484	  the primitive temperature sensor embedded in zx2967 SoCs.
485	  This sensor generates the real time die temperature.
486
487config UNIPHIER_THERMAL
488	tristate "Socionext UniPhier thermal driver"
489	depends on ARCH_UNIPHIER || COMPILE_TEST
490	depends on THERMAL_OF && MFD_SYSCON
491	help
492	  Enable this to plug in UniPhier on-chip PVT thermal driver into the
493	  thermal framework. The driver supports CPU thermal zone temperature
494	  reporting and a couple of trip points.
495
496config SPRD_THERMAL
497	tristate "Temperature sensor on Spreadtrum SoCs"
498	depends on ARCH_SPRD || COMPILE_TEST
499	help
500	  Support for the Spreadtrum thermal sensor driver in the Linux thermal
501	  framework.
502
503config KHADAS_MCU_FAN_THERMAL
504	tristate "Khadas MCU controller FAN cooling support"
505	depends on OF || COMPILE_TEST
506	depends on MFD_KHADAS_MCU
507	select MFD_CORE
508	select REGMAP
509	help
510	  If you say yes here you get support for the FAN controlled
511	  by the Microcontroller found on the Khadas VIM boards.
512
513endif
514