xref: /linux/drivers/thermal/Kconfig (revision 4e0ae876f77bc01a7e77724dea57b4b82bd53244)
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_STATISTICS
19	bool "Thermal state transition statistics"
20	help
21	  Export thermal state transition statistics information through sysfs.
22
23	  If in doubt, say N.
24
25config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
26	int "Emergency poweroff delay in milli-seconds"
27	depends on THERMAL
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	depends on THERMAL=y
156	help
157	  This implements the generic cpu cooling mechanism through frequency
158	  reduction. An ACPI version of this already exists
159	  (drivers/acpi/processor_thermal.c).
160	  This will be useful for platforms using the generic thermal interface
161	  and not the ACPI interface.
162
163	  If you want this support, you should say Y here.
164
165config CLOCK_THERMAL
166	bool "Generic clock cooling support"
167	depends on COMMON_CLK
168	depends on PM_OPP
169	help
170	  This entry implements the generic clock cooling mechanism through
171	  frequency clipping. Typically used to cool off co-processors. The
172	  device that is configured to use this cooling mechanism will be
173	  controlled to reduce clock frequency whenever temperature is high.
174
175config DEVFREQ_THERMAL
176	bool "Generic device cooling support"
177	depends on PM_DEVFREQ
178	depends on PM_OPP
179	help
180	  This implements the generic devfreq cooling mechanism through
181	  frequency reduction for devices using devfreq.
182
183	  This will throttle the device by limiting the maximum allowed DVFS
184	  frequency corresponding to the cooling level.
185
186	  In order to use the power extensions of the cooling device,
187	  devfreq should use the simple_ondemand governor.
188
189	  If you want this support, you should say Y here.
190
191config THERMAL_EMULATION
192	bool "Thermal emulation mode support"
193	help
194	  Enable this option to make a emul_temp sysfs node in thermal zone
195	  directory to support temperature emulation. With emulation sysfs node,
196	  user can manually input temperature and test the different trip
197	  threshold behaviour for simulation purpose.
198
199	  WARNING: Be careful while enabling this option on production systems,
200	  because userland can easily disable the thermal policy by simply
201	  flooding this sysfs node with low temperature values.
202
203config HISI_THERMAL
204	tristate "Hisilicon thermal driver"
205	depends on ARCH_HISI || COMPILE_TEST
206	depends on HAS_IOMEM
207	depends on OF
208	default y
209	help
210	  Enable this to plug hisilicon's thermal sensor driver into the Linux
211	  thermal framework. cpufreq is used as the cooling device to throttle
212	  CPUs when the passive trip is crossed.
213
214config IMX_THERMAL
215	tristate "Temperature sensor driver for Freescale i.MX SoCs"
216	depends on ARCH_MXC || COMPILE_TEST
217	depends on NVMEM || !NVMEM
218	depends on MFD_SYSCON
219	depends on OF
220	help
221	  Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
222	  It supports one critical trip point and one passive trip point.  The
223	  cpufreq is used as the cooling device to throttle CPUs when the
224	  passive trip is crossed.
225
226config MAX77620_THERMAL
227	tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
228	depends on MFD_MAX77620
229	depends on OF
230	help
231	  Support for die junction temperature warning alarm for Maxim
232	  Semiconductor PMIC MAX77620 device. Device generates two alarm
233	  interrupts when PMIC die temperature cross the threshold of
234	  120 degC and 140 degC.
235
236config QORIQ_THERMAL
237	tristate "QorIQ Thermal Monitoring Unit"
238	depends on THERMAL_OF
239	depends on HAS_IOMEM
240	help
241	  Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
242	  It supports one critical trip point and one passive trip point. The
243	  cpufreq is used as the cooling device to throttle CPUs when the
244	  passive trip is crossed.
245
246config SPEAR_THERMAL
247	tristate "SPEAr thermal sensor driver"
248	depends on PLAT_SPEAR || COMPILE_TEST
249	depends on HAS_IOMEM
250	depends on OF
251	help
252	  Enable this to plug the SPEAr thermal sensor driver into the Linux
253	  thermal framework.
254
255config ROCKCHIP_THERMAL
256	tristate "Rockchip thermal driver"
257	depends on ARCH_ROCKCHIP || COMPILE_TEST
258	depends on RESET_CONTROLLER
259	depends on HAS_IOMEM
260	help
261	  Rockchip thermal driver provides support for Temperature sensor
262	  ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
263	  trip point. Cpufreq is used as the cooling device and will throttle
264	  CPUs when the Temperature crosses the passive trip point.
265
266config RCAR_THERMAL
267	tristate "Renesas R-Car thermal driver"
268	depends on ARCH_RENESAS || COMPILE_TEST
269	depends on HAS_IOMEM
270	help
271	  Enable this to plug the R-Car thermal sensor driver into the Linux
272	  thermal framework.
273
274config RCAR_GEN3_THERMAL
275	tristate "Renesas R-Car Gen3 thermal driver"
276	depends on ARCH_RENESAS || COMPILE_TEST
277	depends on HAS_IOMEM
278	depends on OF
279	help
280	  Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
281	  thermal framework.
282
283config KIRKWOOD_THERMAL
284	tristate "Temperature sensor on Marvell Kirkwood SoCs"
285	depends on MACH_KIRKWOOD || COMPILE_TEST
286	depends on HAS_IOMEM
287	depends on OF
288	help
289	  Support for the Kirkwood thermal sensor driver into the Linux thermal
290	  framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
291
292config DOVE_THERMAL
293	tristate "Temperature sensor on Marvell Dove SoCs"
294	depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
295	depends on HAS_IOMEM
296	depends on OF
297	help
298	  Support for the Dove thermal sensor driver in the Linux thermal
299	  framework.
300
301config DB8500_THERMAL
302	tristate "DB8500 thermal management"
303	depends on MFD_DB8500_PRCMU
304	default y
305	help
306	  Adds DB8500 thermal management implementation according to the thermal
307	  management framework. A thermal zone with several trip points will be
308	  created. Cooling devices can be bound to the trip points to cool this
309	  thermal zone if trip points reached.
310
311config ARMADA_THERMAL
312	tristate "Marvell EBU Armada SoCs thermal management"
313	depends on ARCH_MVEBU || COMPILE_TEST
314	depends on HAS_IOMEM
315	depends on OF
316	help
317	  Enable this option if you want to have support for thermal management
318	  controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
319
320config DA9062_THERMAL
321	tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
322	depends on MFD_DA9062 || COMPILE_TEST
323	depends on OF
324	help
325	  Enable this for the Dialog Semiconductor thermal sensor driver.
326	  This will report PMIC junction over-temperature for one thermal trip
327	  zone.
328	  Compatible with the DA9062 and DA9061 PMICs.
329
330config MTK_THERMAL
331	tristate "Temperature sensor driver for mediatek SoCs"
332	depends on ARCH_MEDIATEK || COMPILE_TEST
333	depends on HAS_IOMEM
334	depends on NVMEM || NVMEM=n
335	depends on RESET_CONTROLLER
336	default y
337	help
338	  Enable this option if you want to have support for thermal management
339	  controller present in Mediatek SoCs
340
341menu "Intel thermal drivers"
342depends on X86 || X86_INTEL_QUARK || COMPILE_TEST
343source "drivers/thermal/intel/Kconfig"
344endmenu
345
346menu "Broadcom thermal drivers"
347depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || ARCH_BCM_IPROC || \
348		COMPILE_TEST
349source "drivers/thermal/broadcom/Kconfig"
350endmenu
351
352menu "Texas Instruments thermal drivers"
353depends on ARCH_HAS_BANDGAP || COMPILE_TEST
354depends on HAS_IOMEM
355source "drivers/thermal/ti-soc-thermal/Kconfig"
356endmenu
357
358menu "Samsung thermal drivers"
359depends on ARCH_EXYNOS || COMPILE_TEST
360source "drivers/thermal/samsung/Kconfig"
361endmenu
362
363menu "STMicroelectronics thermal drivers"
364depends on (ARCH_STI || ARCH_STM32) && OF
365source "drivers/thermal/st/Kconfig"
366endmenu
367
368config TANGO_THERMAL
369	tristate "Tango thermal management"
370	depends on ARCH_TANGO || COMPILE_TEST
371	help
372	  Enable the Tango thermal driver, which supports the primitive
373	  temperature sensor embedded in Tango chips since the SMP8758.
374	  This sensor only generates a 1-bit signal to indicate whether
375	  the die temperature exceeds a programmable threshold.
376
377source "drivers/thermal/tegra/Kconfig"
378
379config GENERIC_ADC_THERMAL
380	tristate "Generic ADC based thermal sensor"
381	depends on IIO
382	help
383	  This enabled a thermal sysfs driver for the temperature sensor
384	  which is connected to the General Purpose ADC. The ADC channel
385	  is read via IIO framework and the channel information is provided
386	  to this driver. This driver reports the temperature by reading ADC
387	  channel and converts it to temperature based on lookup table.
388
389menu "Qualcomm thermal drivers"
390depends on (ARCH_QCOM && OF) || COMPILE_TEST
391source "drivers/thermal/qcom/Kconfig"
392endmenu
393
394config ZX2967_THERMAL
395	tristate "Thermal sensors on zx2967 SoC"
396	depends on ARCH_ZX || COMPILE_TEST
397	help
398	  Enable the zx2967 thermal sensors driver, which supports
399	  the primitive temperature sensor embedded in zx2967 SoCs.
400	  This sensor generates the real time die temperature.
401
402config UNIPHIER_THERMAL
403	tristate "Socionext UniPhier thermal driver"
404	depends on ARCH_UNIPHIER || COMPILE_TEST
405	depends on THERMAL_OF && MFD_SYSCON
406	help
407	  Enable this to plug in UniPhier on-chip PVT thermal driver into the
408	  thermal framework. The driver supports CPU thermal zone temperature
409	  reporting and a couple of trip points.
410endif
411