Kconfig 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357
  1. menuconfig NEW_LEDS
  2. bool "LED Support"
  3. help
  4. Say Y to enable Linux LED support. This allows control of supported
  5. LEDs from both userspace and optionally, by kernel events (triggers).
  6. This is not related to standard keyboard LEDs which are controlled
  7. via the input system.
  8. if NEW_LEDS
  9. config LEDS_CLASS
  10. tristate "LED Class Support"
  11. help
  12. This option enables the led sysfs class in /sys/class/leds. You'll
  13. need this to do anything useful with LEDs. If unsure, say N.
  14. if LEDS_CLASS
  15. comment "LED drivers"
  16. config LEDS_88PM860X
  17. tristate "LED Support for Marvell 88PM860x PMIC"
  18. depends on LEDS_CLASS && MFD_88PM860X
  19. help
  20. This option enables support for on-chip LED drivers found on Marvell
  21. Semiconductor 88PM8606 PMIC.
  22. config LEDS_ATMEL_PWM
  23. tristate "LED Support using Atmel PWM outputs"
  24. depends on ATMEL_PWM
  25. help
  26. This option enables support for LEDs driven using outputs
  27. of the dedicated PWM controller found on newer Atmel SOCs.
  28. config LEDS_LOCOMO
  29. tristate "LED Support for Locomo device"
  30. depends on SHARP_LOCOMO
  31. help
  32. This option enables support for the LEDs on Sharp Locomo.
  33. Zaurus models SL-5500 and SL-5600.
  34. config LEDS_MIKROTIK_RB532
  35. tristate "LED Support for Mikrotik Routerboard 532"
  36. depends on MIKROTIK_RB532
  37. help
  38. This option enables support for the so called "User LED" of
  39. Mikrotik's Routerboard 532.
  40. config LEDS_S3C24XX
  41. tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  42. depends on ARCH_S3C2410
  43. help
  44. This option enables support for LEDs connected to GPIO lines
  45. on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  46. config LEDS_AMS_DELTA
  47. tristate "LED Support for the Amstrad Delta (E3)"
  48. depends on MACH_AMS_DELTA
  49. help
  50. This option enables support for the LEDs on Amstrad Delta (E3).
  51. config LEDS_NET48XX
  52. tristate "LED Support for Soekris net48xx series Error LED"
  53. depends on SCx200_GPIO
  54. help
  55. This option enables support for the Soekris net4801 and net4826 error
  56. LED.
  57. config LEDS_FSG
  58. tristate "LED Support for the Freecom FSG-3"
  59. depends on MACH_FSG
  60. help
  61. This option enables support for the LEDs on the Freecom FSG-3.
  62. config LEDS_WRAP
  63. tristate "LED Support for the WRAP series LEDs"
  64. depends on SCx200_GPIO
  65. help
  66. This option enables support for the PCEngines WRAP programmable LEDs.
  67. config LEDS_ALIX2
  68. tristate "LED Support for ALIX.2 and ALIX.3 series"
  69. depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
  70. help
  71. This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
  72. You have to set leds-alix2.force=1 for boards with Award BIOS.
  73. config LEDS_H1940
  74. tristate "LED Support for iPAQ H1940 device"
  75. depends on ARCH_H1940
  76. help
  77. This option enables support for the LEDs on the h1940.
  78. config LEDS_COBALT_QUBE
  79. tristate "LED Support for the Cobalt Qube series front LED"
  80. depends on MIPS_COBALT
  81. help
  82. This option enables support for the front LED on Cobalt Qube series
  83. config LEDS_COBALT_RAQ
  84. bool "LED Support for the Cobalt Raq series"
  85. depends on LEDS_CLASS=y && MIPS_COBALT
  86. select LEDS_TRIGGERS
  87. help
  88. This option enables support for the Cobalt Raq series LEDs.
  89. config LEDS_SUNFIRE
  90. tristate "LED support for SunFire servers."
  91. depends on SPARC64
  92. select LEDS_TRIGGERS
  93. help
  94. This option enables support for the Left, Middle, and Right
  95. LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
  96. config LEDS_HP6XX
  97. tristate "LED Support for the HP Jornada 6xx"
  98. depends on SH_HP6XX
  99. help
  100. This option enables LED support for the handheld
  101. HP Jornada 620/660/680/690.
  102. config LEDS_PCA9532
  103. tristate "LED driver for PCA9532 dimmer"
  104. depends on I2C && INPUT && EXPERIMENTAL
  105. help
  106. This option enables support for NXP pca9532
  107. LED controller. It is generally only useful
  108. as a platform driver
  109. config LEDS_GPIO
  110. tristate "LED Support for GPIO connected LEDs"
  111. depends on GENERIC_GPIO
  112. help
  113. This option enables support for the LEDs connected to GPIO
  114. outputs. To be useful the particular board must have LEDs
  115. and they must be connected to the GPIO lines. The LEDs must be
  116. defined as platform devices and/or OpenFirmware platform devices.
  117. The code to use these bindings can be selected below.
  118. config LEDS_GPIO_PLATFORM
  119. bool "Platform device bindings for GPIO LEDs"
  120. depends on LEDS_GPIO
  121. default y
  122. help
  123. Let the leds-gpio driver drive LEDs which have been defined as
  124. platform devices. If you don't know what this means, say yes.
  125. config LEDS_GPIO_OF
  126. bool "OpenFirmware platform device bindings for GPIO LEDs"
  127. depends on LEDS_GPIO && OF_DEVICE
  128. default y
  129. help
  130. Let the leds-gpio driver drive LEDs which have been defined as
  131. of_platform devices. For instance, LEDs which are listed in a "dts"
  132. file.
  133. config LEDS_LP3944
  134. tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
  135. depends on I2C
  136. help
  137. This option enables support for LEDs connected to the National
  138. Semiconductor LP3944 Lighting Management Unit (LMU) also known as
  139. Fun Light Chip.
  140. To compile this driver as a module, choose M here: the
  141. module will be called leds-lp3944.
  142. config LEDS_CLEVO_MAIL
  143. tristate "Mail LED on Clevo notebook"
  144. depends on X86 && SERIO_I8042 && DMI
  145. help
  146. This driver makes the mail LED accessible from userspace
  147. programs through the leds subsystem. This LED have three
  148. known mode: off, blink at 0.5Hz and blink at 1Hz.
  149. The driver supports two kinds of interface: using ledtrig-timer
  150. or through /sys/class/leds/clevo::mail/brightness. As this LED
  151. cannot change it's brightness it blinks instead. The brightness
  152. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  153. blink at 1Hz.
  154. This module can drive the mail LED for the following notebooks:
  155. Clevo D400P
  156. Clevo D410J
  157. Clevo D410V
  158. Clevo D400V/D470V (not tested, but might work)
  159. Clevo M540N
  160. Clevo M5x0N (not tested, but might work)
  161. Positivo Mobile (Clevo M5x0V)
  162. If your model is not listed here you can try the "nodetect"
  163. module parameter.
  164. To compile this driver as a module, choose M here: the
  165. module will be called leds-clevo-mail.
  166. config LEDS_PCA955X
  167. tristate "LED Support for PCA955x I2C chips"
  168. depends on I2C
  169. help
  170. This option enables support for LEDs connected to PCA955x
  171. LED driver chips accessed via the I2C bus. Supported
  172. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  173. config LEDS_WM831X_STATUS
  174. tristate "LED support for status LEDs on WM831x PMICs"
  175. depends on MFD_WM831X
  176. help
  177. This option enables support for the status LEDs of the WM831x
  178. series of PMICs.
  179. config LEDS_WM8350
  180. tristate "LED Support for WM8350 AudioPlus PMIC"
  181. depends on MFD_WM8350
  182. help
  183. This option enables support for LEDs driven by the Wolfson
  184. Microelectronics WM8350 AudioPlus PMIC.
  185. config LEDS_DA903X
  186. tristate "LED Support for DA9030/DA9034 PMIC"
  187. depends on PMIC_DA903X
  188. help
  189. This option enables support for on-chip LED drivers found
  190. on Dialog Semiconductor DA9030/DA9034 PMICs.
  191. config LEDS_DAC124S085
  192. tristate "LED Support for DAC124S085 SPI DAC"
  193. depends on SPI
  194. help
  195. This option enables support for DAC124S085 SPI DAC from NatSemi,
  196. which can be used to control up to four LEDs.
  197. config LEDS_PWM
  198. tristate "PWM driven LED Support"
  199. depends on HAVE_PWM
  200. help
  201. This option enables support for pwm driven LEDs
  202. config LEDS_REGULATOR
  203. tristate "REGULATOR driven LED support"
  204. depends on REGULATOR
  205. help
  206. This option enables support for regulator driven LEDs.
  207. config LEDS_BD2802
  208. tristate "LED driver for BD2802 RGB LED"
  209. depends on I2C
  210. help
  211. This option enables support for BD2802GU RGB LED driver chips
  212. accessed via the I2C bus.
  213. config LEDS_INTEL_SS4200
  214. tristate "LED driver for Intel NAS SS4200 series"
  215. depends on PCI && DMI
  216. help
  217. This option enables support for the Intel SS4200 series of
  218. Network Attached Storage servers. You may control the hard
  219. drive or power LEDs on the front panel. Using this driver
  220. can stop the front LED from blinking after startup.
  221. config LEDS_LT3593
  222. tristate "LED driver for LT3593 controllers"
  223. depends on GENERIC_GPIO
  224. help
  225. This option enables support for LEDs driven by a Linear Technology
  226. LT3593 controller. This controller uses a special one-wire pulse
  227. coding protocol to set the brightness.
  228. config LEDS_ADP5520
  229. tristate "LED Support for ADP5520/ADP5501 PMIC"
  230. depends on PMIC_ADP5520
  231. help
  232. This option enables support for on-chip LED drivers found
  233. on Analog Devices ADP5520/ADP5501 PMICs.
  234. To compile this driver as a module, choose M here: the module will
  235. be called leds-adp5520.
  236. config LEDS_DELL_NETBOOKS
  237. tristate "External LED on Dell Business Netbooks"
  238. depends on X86 && ACPI_WMI
  239. help
  240. This adds support for the Latitude 2100 and similar
  241. notebooks that have an external LED.
  242. config LEDS_TRIGGERS
  243. bool "LED Trigger support"
  244. help
  245. This option enables trigger support for the leds class.
  246. These triggers allow kernel events to drive the LEDs and can
  247. be configured via sysfs. If unsure, say Y.
  248. if LEDS_TRIGGERS
  249. comment "LED Triggers"
  250. config LEDS_TRIGGER_TIMER
  251. tristate "LED Timer Trigger"
  252. help
  253. This allows LEDs to be controlled by a programmable timer
  254. via sysfs. Some LED hardware can be programmed to start
  255. blinking the LED without any further software interaction.
  256. For more details read Documentation/leds-class.txt.
  257. If unsure, say Y.
  258. config LEDS_TRIGGER_IDE_DISK
  259. bool "LED IDE Disk Trigger"
  260. depends on IDE_GD_ATA
  261. help
  262. This allows LEDs to be controlled by IDE disk activity.
  263. If unsure, say Y.
  264. config LEDS_TRIGGER_HEARTBEAT
  265. tristate "LED Heartbeat Trigger"
  266. help
  267. This allows LEDs to be controlled by a CPU load average.
  268. The flash frequency is a hyperbolic function of the 1-minute
  269. load average.
  270. If unsure, say Y.
  271. config LEDS_TRIGGER_BACKLIGHT
  272. tristate "LED backlight Trigger"
  273. help
  274. This allows LEDs to be controlled as a backlight device: they
  275. turn off and on when the display is blanked and unblanked.
  276. If unsure, say N.
  277. config LEDS_TRIGGER_GPIO
  278. tristate "LED GPIO Trigger"
  279. depends on GPIOLIB
  280. help
  281. This allows LEDs to be controlled by gpio events. It's good
  282. when using gpios as switches and triggering the needed LEDs
  283. from there. One use case is n810's keypad LEDs that could
  284. be triggered by this trigger when user slides up to show
  285. keypad.
  286. If unsure, say N.
  287. config LEDS_TRIGGER_DEFAULT_ON
  288. tristate "LED Default ON Trigger"
  289. help
  290. This allows LEDs to be initialised in the ON state.
  291. If unsure, say Y.
  292. comment "iptables trigger is under Netfilter config (LED target)"
  293. depends on LEDS_TRIGGERS
  294. endif # LEDS_TRIGGERS
  295. endif # LEDS_CLASS
  296. endif # NEW_LEDS