Kconfig 7.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251
  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_HWMON
  16. bool
  17. prompt "Expose thermal sensors as hwmon device"
  18. depends on HWMON=y || HWMON=THERMAL
  19. default y
  20. help
  21. In case a sensor is registered with the thermal
  22. framework, this option will also register it
  23. as a hwmon. The sensor will then have the common
  24. hwmon sysfs interface.
  25. Say 'Y' here if you want all thermal sensors to
  26. have hwmon sysfs interface too.
  27. config THERMAL_OF
  28. bool
  29. prompt "APIs to parse thermal data out of device tree"
  30. depends on OF
  31. default y
  32. help
  33. This options provides helpers to add the support to
  34. read and parse thermal data definitions out of the
  35. device tree blob.
  36. Say 'Y' here if you need to build thermal infrastructure
  37. based on device tree.
  38. choice
  39. prompt "Default Thermal governor"
  40. default THERMAL_DEFAULT_GOV_STEP_WISE
  41. help
  42. This option sets which thermal governor shall be loaded at
  43. startup. If in doubt, select 'step_wise'.
  44. config THERMAL_DEFAULT_GOV_STEP_WISE
  45. bool "step_wise"
  46. select THERMAL_GOV_STEP_WISE
  47. help
  48. Use the step_wise governor as default. This throttles the
  49. devices one step at a time.
  50. config THERMAL_DEFAULT_GOV_FAIR_SHARE
  51. bool "fair_share"
  52. select THERMAL_GOV_FAIR_SHARE
  53. help
  54. Use the fair_share governor as default. This throttles the
  55. devices based on their 'contribution' to a zone. The
  56. contribution should be provided through platform data.
  57. config THERMAL_DEFAULT_GOV_USER_SPACE
  58. bool "user_space"
  59. select THERMAL_GOV_USER_SPACE
  60. help
  61. Select this if you want to let the user space manage the
  62. platform thermals.
  63. endchoice
  64. config THERMAL_GOV_FAIR_SHARE
  65. bool "Fair-share thermal governor"
  66. help
  67. Enable this to manage platform thermals using fair-share governor.
  68. config THERMAL_GOV_STEP_WISE
  69. bool "Step_wise thermal governor"
  70. help
  71. Enable this to manage platform thermals using a simple linear
  72. governor.
  73. config THERMAL_GOV_USER_SPACE
  74. bool "User_space thermal governor"
  75. help
  76. Enable this to let the user space manage the platform thermals.
  77. config CPU_THERMAL
  78. bool "generic cpu cooling support"
  79. depends on CPU_FREQ
  80. depends on THERMAL_OF
  81. help
  82. This implements the generic cpu cooling mechanism through frequency
  83. reduction. An ACPI version of this already exists
  84. (drivers/acpi/processor_thermal.c).
  85. This will be useful for platforms using the generic thermal interface
  86. and not the ACPI interface.
  87. If you want this support, you should say Y here.
  88. config THERMAL_EMULATION
  89. bool "Thermal emulation mode support"
  90. help
  91. Enable this option to make a emul_temp sysfs node in thermal zone
  92. directory to support temperature emulation. With emulation sysfs node,
  93. user can manually input temperature and test the different trip
  94. threshold behaviour for simulation purpose.
  95. WARNING: Be careful while enabling this option on production systems,
  96. because userland can easily disable the thermal policy by simply
  97. flooding this sysfs node with low temperature values.
  98. config IMX_THERMAL
  99. tristate "Temperature sensor driver for Freescale i.MX SoCs"
  100. depends on CPU_THERMAL
  101. depends on MFD_SYSCON
  102. depends on OF
  103. help
  104. Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
  105. It supports one critical trip point and one passive trip point. The
  106. cpufreq is used as the cooling device to throttle CPUs when the
  107. passive trip is crossed.
  108. config SPEAR_THERMAL
  109. bool "SPEAr thermal sensor driver"
  110. depends on PLAT_SPEAR
  111. depends on OF
  112. help
  113. Enable this to plug the SPEAr thermal sensor driver into the Linux
  114. thermal framework.
  115. config RCAR_THERMAL
  116. tristate "Renesas R-Car thermal driver"
  117. depends on ARCH_SHMOBILE || COMPILE_TEST
  118. depends on HAS_IOMEM
  119. help
  120. Enable this to plug the R-Car thermal sensor driver into the Linux
  121. thermal framework.
  122. config KIRKWOOD_THERMAL
  123. tristate "Temperature sensor on Marvell Kirkwood SoCs"
  124. depends on MACH_KIRKWOOD
  125. depends on OF
  126. help
  127. Support for the Kirkwood thermal sensor driver into the Linux thermal
  128. framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
  129. config DOVE_THERMAL
  130. tristate "Temperature sensor on Marvell Dove SoCs"
  131. depends on ARCH_DOVE || MACH_DOVE
  132. depends on OF
  133. help
  134. Support for the Dove thermal sensor driver in the Linux thermal
  135. framework.
  136. config DB8500_THERMAL
  137. bool "DB8500 thermal management"
  138. depends on ARCH_U8500
  139. default y
  140. help
  141. Adds DB8500 thermal management implementation according to the thermal
  142. management framework. A thermal zone with several trip points will be
  143. created. Cooling devices can be bound to the trip points to cool this
  144. thermal zone if trip points reached.
  145. config ARMADA_THERMAL
  146. tristate "Armada 370/XP thermal management"
  147. depends on ARCH_MVEBU
  148. depends on OF
  149. help
  150. Enable this option if you want to have support for thermal management
  151. controller present in Armada 370 and Armada XP SoC.
  152. config DB8500_CPUFREQ_COOLING
  153. tristate "DB8500 cpufreq cooling"
  154. depends on ARCH_U8500
  155. depends on CPU_THERMAL
  156. default y
  157. help
  158. Adds DB8500 cpufreq cooling devices, and these cooling devices can be
  159. bound to thermal zone trip points. When a trip point reached, the
  160. bound cpufreq cooling device turns active to set CPU frequency low to
  161. cool down the CPU.
  162. config INTEL_POWERCLAMP
  163. tristate "Intel PowerClamp idle injection driver"
  164. depends on THERMAL
  165. depends on X86
  166. depends on CPU_SUP_INTEL
  167. help
  168. Enable this to enable Intel PowerClamp idle injection driver. This
  169. enforce idle time which results in more package C-state residency. The
  170. user interface is exposed via generic thermal framework.
  171. config X86_PKG_TEMP_THERMAL
  172. tristate "X86 package temperature thermal driver"
  173. depends on X86_THERMAL_VECTOR
  174. select THERMAL_GOV_USER_SPACE
  175. default m
  176. help
  177. Enable this to register CPU digital sensor for package temperature as
  178. thermal zone. Each package will have its own thermal zone. There are
  179. two trip points which can be set by user to get notifications via thermal
  180. notification methods.
  181. config ACPI_INT3403_THERMAL
  182. tristate "ACPI INT3403 thermal driver"
  183. depends on X86 && ACPI
  184. help
  185. Newer laptops and tablets that use ACPI may have thermal sensors
  186. outside the core CPU/SOC for thermal safety reasons. These
  187. temperature sensors are also exposed for the OS to use via the so
  188. called INT3403 ACPI object. This driver will, on devices that have
  189. such sensors, expose the temperature information from these sensors
  190. to userspace via the normal thermal framework. This means that a wide
  191. range of applications and GUI widgets can show this information to
  192. the user or use this information for making decisions. For example,
  193. the Intel Thermal Daemon can use this information to allow the user
  194. to select his laptop to run without turning on the fans.
  195. config INTEL_SOC_DTS_THERMAL
  196. tristate "Intel SoCs DTS thermal driver"
  197. depends on X86 && IOSF_MBI
  198. help
  199. Enable this to register Intel SoCs (e.g. Bay Trail) platform digital
  200. temperature sensor (DTS). These SoCs have two additional DTSs in
  201. addition to DTSs on CPU cores. Each DTS will be registered as a
  202. thermal zone. There are two trip points. One of the trip point can
  203. be set by user mode programs to get notifications via Linux thermal
  204. notification methods.The other trip is a critical trip point, which
  205. was set by the driver based on the TJ MAX temperature.
  206. menu "Texas Instruments thermal drivers"
  207. source "drivers/thermal/ti-soc-thermal/Kconfig"
  208. endmenu
  209. menu "Samsung thermal drivers"
  210. depends on ARCH_EXYNOS
  211. source "drivers/thermal/samsung/Kconfig"
  212. endmenu
  213. menu "STMicroelectronics thermal drivers"
  214. depends on ARCH_STI && OF
  215. source "drivers/thermal/st/Kconfig"
  216. endmenu
  217. endif