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 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
453source "drivers/thermal/tegra/Kconfig"
454
455config GENERIC_ADC_THERMAL
456	tristate "Generic ADC based thermal sensor"
457	depends on IIO
458	help
459	  This enabled a thermal sysfs driver for the temperature sensor
460	  which is connected to the General Purpose ADC. The ADC channel
461	  is read via IIO framework and the channel information is provided
462	  to this driver. This driver reports the temperature by reading ADC
463	  channel and converts it to temperature based on lookup table.
464
465menu "Qualcomm thermal drivers"
466depends on (ARCH_QCOM && OF) || COMPILE_TEST
467source "drivers/thermal/qcom/Kconfig"
468endmenu
469
470config UNIPHIER_THERMAL
471	tristate "Socionext UniPhier thermal driver"
472	depends on ARCH_UNIPHIER || COMPILE_TEST
473	depends on THERMAL_OF && MFD_SYSCON
474	help
475	  Enable this to plug in UniPhier on-chip PVT thermal driver into the
476	  thermal framework. The driver supports CPU thermal zone temperature
477	  reporting and a couple of trip points.
478
479config SPRD_THERMAL
480	tristate "Temperature sensor on Spreadtrum SoCs"
481	depends on ARCH_SPRD || COMPILE_TEST
482	help
483	  Support for the Spreadtrum thermal sensor driver in the Linux thermal
484	  framework.
485
486config KHADAS_MCU_FAN_THERMAL
487	tristate "Khadas MCU controller FAN cooling support"
488	depends on OF || COMPILE_TEST
489	depends on MFD_KHADAS_MCU
490	select MFD_CORE
491	select REGMAP
492	help
493	  If you say yes here you get support for the FAN controlled
494	  by the Microcontroller found on the Khadas VIM boards.
495
496endif