Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485
  1. #
  2. # Generic thermal sysfs drivers configuration
  3. #
  4. menuconfig THERMAL
  5. tristate "Generic Thermal sysfs driver"
  6. help
  7. Generic Thermal Sysfs driver offers a generic mechanism for
  8. thermal management. Usually it's made up of one or more thermal
  9. zone and cooling device.
  10. Each thermal zone contains its own temperature, trip points,
  11. cooling devices.
  12. All platforms with ACPI thermal support can use this driver.
  13. If you want this support, you should say Y or M here.
  14. if THERMAL
  15. config THERMAL_EMERGENCY_POWEROFF_DELAY_MS
  16. int "Emergency poweroff delay in milli-seconds"
  17. depends on THERMAL
  18. default 0
  19. help
  20. Thermal subsystem will issue a graceful shutdown when
  21. critical temperatures are reached using orderly_poweroff(). In
  22. case of failure of an orderly_poweroff(), the thermal emergency
  23. poweroff kicks in after a delay has elapsed and shuts down the system.
  24. This config is number of milliseconds to delay before emergency
  25. poweroff kicks in. Similarly to the critical trip point,
  26. the delay should be carefully profiled so as to give adequate
  27. time for orderly_poweroff() to finish on regular execution.
  28. If set to 0 emergency poweroff will not be supported.
  29. In doubt, leave as 0.
  30. config THERMAL_HWMON
  31. bool
  32. prompt "Expose thermal sensors as hwmon device"
  33. depends on HWMON=y || HWMON=THERMAL
  34. default y
  35. help
  36. In case a sensor is registered with the thermal
  37. framework, this option will also register it
  38. as a hwmon. The sensor will then have the common
  39. hwmon sysfs interface.
  40. Say 'Y' here if you want all thermal sensors to
  41. have hwmon sysfs interface too.
  42. config THERMAL_OF
  43. bool
  44. prompt "APIs to parse thermal data out of device tree"
  45. depends on OF
  46. default y
  47. help
  48. This options provides helpers to add the support to
  49. read and parse thermal data definitions out of the
  50. device tree blob.
  51. Say 'Y' here if you need to build thermal infrastructure
  52. based on device tree.
  53. config THERMAL_WRITABLE_TRIPS
  54. bool "Enable writable trip points"
  55. help
  56. This option allows the system integrator to choose whether
  57. trip temperatures can be changed from userspace. The
  58. writable trips need to be specified when setting up the
  59. thermal zone but the choice here takes precedence.
  60. Say 'Y' here if you would like to allow userspace tools to
  61. change trip temperatures.
  62. choice
  63. prompt "Default Thermal governor"
  64. default THERMAL_DEFAULT_GOV_STEP_WISE
  65. help
  66. This option sets which thermal governor shall be loaded at
  67. startup. If in doubt, select 'step_wise'.
  68. config THERMAL_DEFAULT_GOV_STEP_WISE
  69. bool "step_wise"
  70. select THERMAL_GOV_STEP_WISE
  71. help
  72. Use the step_wise governor as default. This throttles the
  73. devices one step at a time.
  74. config THERMAL_DEFAULT_GOV_FAIR_SHARE
  75. bool "fair_share"
  76. select THERMAL_GOV_FAIR_SHARE
  77. help
  78. Use the fair_share governor as default. This throttles the
  79. devices based on their 'contribution' to a zone. The
  80. contribution should be provided through platform data.
  81. config THERMAL_DEFAULT_GOV_USER_SPACE
  82. bool "user_space"
  83. select THERMAL_GOV_USER_SPACE
  84. help
  85. Select this if you want to let the user space manage the
  86. platform thermals.
  87. config THERMAL_DEFAULT_GOV_POWER_ALLOCATOR
  88. bool "power_allocator"
  89. select THERMAL_GOV_POWER_ALLOCATOR
  90. help
  91. Select this if you want to control temperature based on
  92. system and device power allocation. This governor can only
  93. operate on cooling devices that implement the power API.
  94. endchoice
  95. config THERMAL_GOV_FAIR_SHARE
  96. bool "Fair-share thermal governor"
  97. help
  98. Enable this to manage platform thermals using fair-share governor.
  99. config THERMAL_GOV_STEP_WISE
  100. bool "Step_wise thermal governor"
  101. help
  102. Enable this to manage platform thermals using a simple linear
  103. governor.
  104. config THERMAL_GOV_BANG_BANG
  105. bool "Bang Bang thermal governor"
  106. default n
  107. help
  108. Enable this to manage platform thermals using bang bang governor.
  109. Say 'Y' here if you want to use two point temperature regulation
  110. used for fans without throttling. Some fan drivers depend on this
  111. governor to be enabled (e.g. acerhdf).
  112. config THERMAL_GOV_USER_SPACE
  113. bool "User_space thermal governor"
  114. help
  115. Enable this to let the user space manage the platform thermals.
  116. config THERMAL_GOV_POWER_ALLOCATOR
  117. bool "Power allocator thermal governor"
  118. help
  119. Enable this to manage platform thermals by dynamically
  120. allocating and limiting power to devices.
  121. config CPU_THERMAL
  122. bool "generic cpu cooling support"
  123. depends on CPU_FREQ
  124. depends on THERMAL_OF
  125. help
  126. This implements the generic cpu cooling mechanism through frequency
  127. reduction. An ACPI version of this already exists
  128. (drivers/acpi/processor_thermal.c).
  129. This will be useful for platforms using the generic thermal interface
  130. and not the ACPI interface.
  131. If you want this support, you should say Y here.
  132. config CLOCK_THERMAL
  133. bool "Generic clock cooling support"
  134. depends on COMMON_CLK
  135. depends on PM_OPP
  136. help
  137. This entry implements the generic clock cooling mechanism through
  138. frequency clipping. Typically used to cool off co-processors. The
  139. device that is configured to use this cooling mechanism will be
  140. controlled to reduce clock frequency whenever temperature is high.
  141. config DEVFREQ_THERMAL
  142. bool "Generic device cooling support"
  143. depends on PM_DEVFREQ
  144. depends on PM_OPP
  145. help
  146. This implements the generic devfreq cooling mechanism through
  147. frequency reduction for devices using devfreq.
  148. This will throttle the device by limiting the maximum allowed DVFS
  149. frequency corresponding to the cooling level.
  150. In order to use the power extensions of the cooling device,
  151. devfreq should use the simple_ondemand governor.
  152. If you want this support, you should say Y here.
  153. config THERMAL_EMULATION
  154. bool "Thermal emulation mode support"
  155. help
  156. Enable this option to make a emul_temp sysfs node in thermal zone
  157. directory to support temperature emulation. With emulation sysfs node,
  158. user can manually input temperature and test the different trip
  159. threshold behaviour for simulation purpose.
  160. WARNING: Be careful while enabling this option on production systems,
  161. because userland can easily disable the thermal policy by simply
  162. flooding this sysfs node with low temperature values.
  163. config HISI_THERMAL
  164. tristate "Hisilicon thermal driver"
  165. depends on ARCH_HISI || COMPILE_TEST
  166. depends on HAS_IOMEM
  167. depends on OF
  168. default y
  169. help
  170. Enable this to plug hisilicon's thermal sensor driver into the Linux
  171. thermal framework. cpufreq is used as the cooling device to throttle
  172. CPUs when the passive trip is crossed.
  173. config IMX_THERMAL
  174. tristate "Temperature sensor driver for Freescale i.MX SoCs"
  175. depends on (ARCH_MXC && CPU_THERMAL) || COMPILE_TEST
  176. depends on NVMEM || !NVMEM
  177. depends on MFD_SYSCON
  178. depends on OF
  179. help
  180. Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
  181. It supports one critical trip point and one passive trip point. The
  182. cpufreq is used as the cooling device to throttle CPUs when the
  183. passive trip is crossed.
  184. config MAX77620_THERMAL
  185. tristate "Temperature sensor driver for Maxim MAX77620 PMIC"
  186. depends on MFD_MAX77620
  187. depends on OF
  188. help
  189. Support for die junction temperature warning alarm for Maxim
  190. Semiconductor PMIC MAX77620 device. Device generates two alarm
  191. interrupts when PMIC die temperature cross the threshold of
  192. 120 degC and 140 degC.
  193. config QORIQ_THERMAL
  194. tristate "QorIQ Thermal Monitoring Unit"
  195. depends on THERMAL_OF
  196. depends on HAS_IOMEM
  197. help
  198. Support for Thermal Monitoring Unit (TMU) found on QorIQ platforms.
  199. It supports one critical trip point and one passive trip point. The
  200. cpufreq is used as the cooling device to throttle CPUs when the
  201. passive trip is crossed.
  202. config SPEAR_THERMAL
  203. tristate "SPEAr thermal sensor driver"
  204. depends on PLAT_SPEAR || COMPILE_TEST
  205. depends on HAS_IOMEM
  206. depends on OF
  207. help
  208. Enable this to plug the SPEAr thermal sensor driver into the Linux
  209. thermal framework.
  210. config ROCKCHIP_THERMAL
  211. tristate "Rockchip thermal driver"
  212. depends on ARCH_ROCKCHIP || COMPILE_TEST
  213. depends on RESET_CONTROLLER
  214. depends on HAS_IOMEM
  215. help
  216. Rockchip thermal driver provides support for Temperature sensor
  217. ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
  218. trip point. Cpufreq is used as the cooling device and will throttle
  219. CPUs when the Temperature crosses the passive trip point.
  220. config RCAR_THERMAL
  221. tristate "Renesas R-Car thermal driver"
  222. depends on ARCH_RENESAS || COMPILE_TEST
  223. depends on HAS_IOMEM
  224. help
  225. Enable this to plug the R-Car thermal sensor driver into the Linux
  226. thermal framework.
  227. config RCAR_GEN3_THERMAL
  228. tristate "Renesas R-Car Gen3 thermal driver"
  229. depends on ARCH_RENESAS || COMPILE_TEST
  230. depends on HAS_IOMEM
  231. depends on OF
  232. help
  233. Enable this to plug the R-Car Gen3 thermal sensor driver into the Linux
  234. thermal framework.
  235. config KIRKWOOD_THERMAL
  236. tristate "Temperature sensor on Marvell Kirkwood SoCs"
  237. depends on MACH_KIRKWOOD || COMPILE_TEST
  238. depends on HAS_IOMEM
  239. depends on OF
  240. help
  241. Support for the Kirkwood thermal sensor driver into the Linux thermal
  242. framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
  243. config DOVE_THERMAL
  244. tristate "Temperature sensor on Marvell Dove SoCs"
  245. depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
  246. depends on HAS_IOMEM
  247. depends on OF
  248. help
  249. Support for the Dove thermal sensor driver in the Linux thermal
  250. framework.
  251. config DB8500_THERMAL
  252. tristate "DB8500 thermal management"
  253. depends on MFD_DB8500_PRCMU
  254. default y
  255. help
  256. Adds DB8500 thermal management implementation according to the thermal
  257. management framework. A thermal zone with several trip points will be
  258. created. Cooling devices can be bound to the trip points to cool this
  259. thermal zone if trip points reached.
  260. config ARMADA_THERMAL
  261. tristate "Marvell EBU Armada SoCs thermal management"
  262. depends on ARCH_MVEBU || COMPILE_TEST
  263. depends on HAS_IOMEM
  264. depends on OF
  265. help
  266. Enable this option if you want to have support for thermal management
  267. controller present in Marvell EBU Armada SoCs (370,375,XP,38x,7K,8K).
  268. config DA9062_THERMAL
  269. tristate "DA9062/DA9061 Dialog Semiconductor thermal driver"
  270. depends on MFD_DA9062 || COMPILE_TEST
  271. depends on OF
  272. help
  273. Enable this for the Dialog Semiconductor thermal sensor driver.
  274. This will report PMIC junction over-temperature for one thermal trip
  275. zone.
  276. Compatible with the DA9062 and DA9061 PMICs.
  277. config INTEL_POWERCLAMP
  278. tristate "Intel PowerClamp idle injection driver"
  279. depends on THERMAL
  280. depends on X86
  281. depends on CPU_SUP_INTEL
  282. help
  283. Enable this to enable Intel PowerClamp idle injection driver. This
  284. enforce idle time which results in more package C-state residency. The
  285. user interface is exposed via generic thermal framework.
  286. config X86_PKG_TEMP_THERMAL
  287. tristate "X86 package temperature thermal driver"
  288. depends on X86_THERMAL_VECTOR
  289. select THERMAL_GOV_USER_SPACE
  290. select THERMAL_WRITABLE_TRIPS
  291. default m
  292. help
  293. Enable this to register CPU digital sensor for package temperature as
  294. thermal zone. Each package will have its own thermal zone. There are
  295. two trip points which can be set by user to get notifications via thermal
  296. notification methods.
  297. config INTEL_SOC_DTS_IOSF_CORE
  298. tristate
  299. depends on X86 && PCI
  300. select IOSF_MBI
  301. help
  302. This is becoming a common feature for Intel SoCs to expose the additional
  303. digital temperature sensors (DTSs) using side band interface (IOSF). This
  304. implements the common set of helper functions to register, get temperature
  305. and get/set thresholds on DTSs.
  306. config INTEL_SOC_DTS_THERMAL
  307. tristate "Intel SoCs DTS thermal driver"
  308. depends on X86 && PCI
  309. select INTEL_SOC_DTS_IOSF_CORE
  310. select THERMAL_WRITABLE_TRIPS
  311. help
  312. Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
  313. temperature sensor (DTS). These SoCs have two additional DTSs in
  314. addition to DTSs on CPU cores. Each DTS will be registered as a
  315. thermal zone. There are two trip points. One of the trip point can
  316. be set by user mode programs to get notifications via Linux thermal
  317. notification methods.The other trip is a critical trip point, which
  318. was set by the driver based on the TJ MAX temperature.
  319. config INTEL_QUARK_DTS_THERMAL
  320. tristate "Intel Quark DTS thermal driver"
  321. depends on X86_INTEL_QUARK
  322. help
  323. Enable this to register Intel Quark SoC (e.g. X1000) platform digital
  324. temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
  325. The DTS will be registered as a thermal zone. There are two trip points:
  326. hot & critical. The critical trip point default value is set by
  327. underlying BIOS/Firmware.
  328. menu "ACPI INT340X thermal drivers"
  329. source drivers/thermal/int340x_thermal/Kconfig
  330. endmenu
  331. config INTEL_BXT_PMIC_THERMAL
  332. tristate "Intel Broxton PMIC thermal driver"
  333. depends on X86 && INTEL_SOC_PMIC_BXTWC && REGMAP
  334. help
  335. Select this driver for Intel Broxton PMIC with ADC channels monitoring
  336. system temperature measurements and alerts.
  337. This driver is used for monitoring the ADC channels of PMIC and handles
  338. the alert trip point interrupts and notifies the thermal framework with
  339. the trip point and temperature details of the zone.
  340. config INTEL_PCH_THERMAL
  341. tristate "Intel PCH Thermal Reporting Driver"
  342. depends on X86 && PCI
  343. help
  344. Enable this to support thermal reporting on certain intel PCHs.
  345. Thermal reporting device will provide temperature reading,
  346. programmable trip points and other information.
  347. config MTK_THERMAL
  348. tristate "Temperature sensor driver for mediatek SoCs"
  349. depends on ARCH_MEDIATEK || COMPILE_TEST
  350. depends on HAS_IOMEM
  351. depends on NVMEM || NVMEM=n
  352. depends on RESET_CONTROLLER
  353. default y
  354. help
  355. Enable this option if you want to have support for thermal management
  356. controller present in Mediatek SoCs
  357. menu "Broadcom thermal drivers"
  358. depends on ARCH_BCM || ARCH_BRCMSTB || ARCH_BCM2835 || COMPILE_TEST
  359. source "drivers/thermal/broadcom/Kconfig"
  360. endmenu
  361. menu "Texas Instruments thermal drivers"
  362. depends on ARCH_HAS_BANDGAP || COMPILE_TEST
  363. depends on HAS_IOMEM
  364. source "drivers/thermal/ti-soc-thermal/Kconfig"
  365. endmenu
  366. menu "Samsung thermal drivers"
  367. depends on ARCH_EXYNOS || COMPILE_TEST
  368. source "drivers/thermal/samsung/Kconfig"
  369. endmenu
  370. menu "STMicroelectronics thermal drivers"
  371. depends on ARCH_STI && OF
  372. source "drivers/thermal/st/Kconfig"
  373. endmenu
  374. config TANGO_THERMAL
  375. tristate "Tango thermal management"
  376. depends on ARCH_TANGO || COMPILE_TEST
  377. help
  378. Enable the Tango thermal driver, which supports the primitive
  379. temperature sensor embedded in Tango chips since the SMP8758.
  380. This sensor only generates a 1-bit signal to indicate whether
  381. the die temperature exceeds a programmable threshold.
  382. source "drivers/thermal/tegra/Kconfig"
  383. config QCOM_SPMI_TEMP_ALARM
  384. tristate "Qualcomm SPMI PMIC Temperature Alarm"
  385. depends on OF && SPMI && IIO
  386. select REGMAP_SPMI
  387. help
  388. This enables a thermal sysfs driver for Qualcomm plug-and-play (QPNP)
  389. PMIC devices. It shows up in sysfs as a thermal sensor with multiple
  390. trip points. The temperature reported by the thermal sensor reflects the
  391. real time die temperature if an ADC is present or an estimate of the
  392. temperature based upon the over temperature stage value.
  393. config GENERIC_ADC_THERMAL
  394. tristate "Generic ADC based thermal sensor"
  395. depends on IIO
  396. help
  397. This enabled a thermal sysfs driver for the temperature sensor
  398. which is connected to the General Purpose ADC. The ADC channel
  399. is read via IIO framework and the channel information is provided
  400. to this driver. This driver reports the temperature by reading ADC
  401. channel and converts it to temperature based on lookup table.
  402. menu "Qualcomm thermal drivers"
  403. depends on (ARCH_QCOM && OF) || COMPILE_TEST
  404. source "drivers/thermal/qcom/Kconfig"
  405. endmenu
  406. config ZX2967_THERMAL
  407. tristate "Thermal sensors on zx2967 SoC"
  408. depends on ARCH_ZX || COMPILE_TEST
  409. help
  410. Enable the zx2967 thermal sensors driver, which supports
  411. the primitive temperature sensor embedded in zx2967 SoCs.
  412. This sensor generates the real time die temperature.
  413. config UNIPHIER_THERMAL
  414. tristate "Socionext UniPhier thermal driver"
  415. depends on ARCH_UNIPHIER || COMPILE_TEST
  416. depends on THERMAL_OF && MFD_SYSCON
  417. help
  418. Enable this to plug in UniPhier on-chip PVT thermal driver into the
  419. thermal framework. The driver supports CPU thermal zone temperature
  420. reporting and a couple of trip points.
  421. endif