Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460
  1. config LEDS_GPIO_REGISTER
  2. bool
  3. help
  4. This option provides the function gpio_led_register_device.
  5. As this function is used by arch code it must not be compiled as a
  6. module.
  7. menuconfig NEW_LEDS
  8. bool "LED Support"
  9. help
  10. Say Y to enable Linux LED support. This allows control of supported
  11. LEDs from both userspace and optionally, by kernel events (triggers).
  12. This is not related to standard keyboard LEDs which are controlled
  13. via the input system.
  14. if NEW_LEDS
  15. config LEDS_CLASS
  16. bool "LED Class Support"
  17. help
  18. This option enables the led sysfs class in /sys/class/leds. You'll
  19. need this to do anything useful with LEDs. If unsure, say N.
  20. comment "LED drivers"
  21. config LEDS_88PM860X
  22. tristate "LED Support for Marvell 88PM860x PMIC"
  23. depends on LEDS_CLASS
  24. depends on MFD_88PM860X
  25. help
  26. This option enables support for on-chip LED drivers found on Marvell
  27. Semiconductor 88PM8606 PMIC.
  28. config LEDS_ATMEL_PWM
  29. tristate "LED Support using Atmel PWM outputs"
  30. depends on LEDS_CLASS
  31. depends on ATMEL_PWM
  32. help
  33. This option enables support for LEDs driven using outputs
  34. of the dedicated PWM controller found on newer Atmel SOCs.
  35. config LEDS_LM3530
  36. tristate "LCD Backlight driver for LM3530"
  37. depends on LEDS_CLASS
  38. depends on I2C
  39. help
  40. This option enables support for the LCD backlight using
  41. LM3530 ambient light sensor chip. This ALS chip can be
  42. controlled manually or using PWM input or using ambient
  43. light automatically.
  44. config LEDS_LOCOMO
  45. tristate "LED Support for Locomo device"
  46. depends on LEDS_CLASS
  47. depends on SHARP_LOCOMO
  48. help
  49. This option enables support for the LEDs on Sharp Locomo.
  50. Zaurus models SL-5500 and SL-5600.
  51. config LEDS_MIKROTIK_RB532
  52. tristate "LED Support for Mikrotik Routerboard 532"
  53. depends on LEDS_CLASS
  54. depends on MIKROTIK_RB532
  55. help
  56. This option enables support for the so called "User LED" of
  57. Mikrotik's Routerboard 532.
  58. config LEDS_S3C24XX
  59. tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  60. depends on LEDS_CLASS
  61. depends on ARCH_S3C2410
  62. help
  63. This option enables support for LEDs connected to GPIO lines
  64. on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  65. config LEDS_AMS_DELTA
  66. tristate "LED Support for the Amstrad Delta (E3)"
  67. depends on LEDS_CLASS
  68. depends on MACH_AMS_DELTA
  69. help
  70. This option enables support for the LEDs on Amstrad Delta (E3).
  71. config LEDS_NET48XX
  72. tristate "LED Support for Soekris net48xx series Error LED"
  73. depends on LEDS_CLASS
  74. depends on SCx200_GPIO
  75. help
  76. This option enables support for the Soekris net4801 and net4826 error
  77. LED.
  78. config LEDS_NET5501
  79. tristate "LED Support for Soekris net5501 series Error LED"
  80. depends on LEDS_TRIGGERS
  81. depends on X86 && GPIO_CS5535
  82. select LEDS_TRIGGER_DEFAULT_ON
  83. default n
  84. help
  85. Add support for the Soekris net5501 board (detection, error led
  86. and GPIO).
  87. config LEDS_FSG
  88. tristate "LED Support for the Freecom FSG-3"
  89. depends on LEDS_CLASS
  90. depends on MACH_FSG
  91. help
  92. This option enables support for the LEDs on the Freecom FSG-3.
  93. config LEDS_WRAP
  94. tristate "LED Support for the WRAP series LEDs"
  95. depends on LEDS_CLASS
  96. depends on SCx200_GPIO
  97. help
  98. This option enables support for the PCEngines WRAP programmable LEDs.
  99. config LEDS_COBALT_QUBE
  100. tristate "LED Support for the Cobalt Qube series front LED"
  101. depends on LEDS_CLASS
  102. depends on MIPS_COBALT
  103. help
  104. This option enables support for the front LED on Cobalt Qube series
  105. config LEDS_COBALT_RAQ
  106. bool "LED Support for the Cobalt Raq series"
  107. depends on LEDS_CLASS=y && MIPS_COBALT
  108. select LEDS_TRIGGERS
  109. help
  110. This option enables support for the Cobalt Raq series LEDs.
  111. config LEDS_SUNFIRE
  112. tristate "LED support for SunFire servers."
  113. depends on LEDS_CLASS
  114. depends on SPARC64
  115. select LEDS_TRIGGERS
  116. help
  117. This option enables support for the Left, Middle, and Right
  118. LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
  119. config LEDS_HP6XX
  120. tristate "LED Support for the HP Jornada 6xx"
  121. depends on LEDS_CLASS
  122. depends on SH_HP6XX
  123. help
  124. This option enables LED support for the handheld
  125. HP Jornada 620/660/680/690.
  126. config LEDS_PCA9532
  127. tristate "LED driver for PCA9532 dimmer"
  128. depends on LEDS_CLASS
  129. depends on I2C && INPUT && EXPERIMENTAL
  130. help
  131. This option enables support for NXP pca9532
  132. LED controller. It is generally only useful
  133. as a platform driver
  134. config LEDS_PCA9532_GPIO
  135. bool "Enable GPIO support for PCA9532"
  136. depends on LEDS_PCA9532
  137. depends on GPIOLIB
  138. help
  139. Allow unused pins on PCA9532 to be used as gpio.
  140. To use a pin as gpio pca9532_type in pca9532_platform data needs to
  141. set to PCA9532_TYPE_GPIO.
  142. config LEDS_GPIO
  143. tristate "LED Support for GPIO connected LEDs"
  144. depends on LEDS_CLASS
  145. depends on GENERIC_GPIO
  146. help
  147. This option enables support for the LEDs connected to GPIO
  148. outputs. To be useful the particular board must have LEDs
  149. and they must be connected to the GPIO lines. The LEDs must be
  150. defined as platform devices and/or OpenFirmware platform devices.
  151. The code to use these bindings can be selected below.
  152. config LEDS_LP3944
  153. tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
  154. depends on LEDS_CLASS
  155. depends on I2C
  156. help
  157. This option enables support for LEDs connected to the National
  158. Semiconductor LP3944 Lighting Management Unit (LMU) also known as
  159. Fun Light Chip.
  160. To compile this driver as a module, choose M here: the
  161. module will be called leds-lp3944.
  162. config LEDS_LP5521
  163. tristate "LED Support for N.S. LP5521 LED driver chip"
  164. depends on LEDS_CLASS && I2C
  165. help
  166. If you say yes here you get support for the National Semiconductor
  167. LP5521 LED driver. It is 3 channel chip with programmable engines.
  168. Driver provides direct control via LED class and interface for
  169. programming the engines.
  170. config LEDS_LP5523
  171. tristate "LED Support for N.S. LP5523 LED driver chip"
  172. depends on LEDS_CLASS && I2C
  173. help
  174. If you say yes here you get support for the National Semiconductor
  175. LP5523 LED driver. It is 9 channel chip with programmable engines.
  176. Driver provides direct control via LED class and interface for
  177. programming the engines.
  178. config LEDS_CLEVO_MAIL
  179. tristate "Mail LED on Clevo notebook"
  180. depends on LEDS_CLASS
  181. depends on X86 && SERIO_I8042 && DMI
  182. help
  183. This driver makes the mail LED accessible from userspace
  184. programs through the leds subsystem. This LED have three
  185. known mode: off, blink at 0.5Hz and blink at 1Hz.
  186. The driver supports two kinds of interface: using ledtrig-timer
  187. or through /sys/class/leds/clevo::mail/brightness. As this LED
  188. cannot change it's brightness it blinks instead. The brightness
  189. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  190. blink at 1Hz.
  191. This module can drive the mail LED for the following notebooks:
  192. Clevo D400P
  193. Clevo D410J
  194. Clevo D410V
  195. Clevo D400V/D470V (not tested, but might work)
  196. Clevo M540N
  197. Clevo M5x0N (not tested, but might work)
  198. Positivo Mobile (Clevo M5x0V)
  199. If your model is not listed here you can try the "nodetect"
  200. module parameter.
  201. To compile this driver as a module, choose M here: the
  202. module will be called leds-clevo-mail.
  203. config LEDS_PCA955X
  204. tristate "LED Support for PCA955x I2C chips"
  205. depends on LEDS_CLASS
  206. depends on I2C
  207. help
  208. This option enables support for LEDs connected to PCA955x
  209. LED driver chips accessed via the I2C bus. Supported
  210. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  211. config LEDS_WM831X_STATUS
  212. tristate "LED support for status LEDs on WM831x PMICs"
  213. depends on LEDS_CLASS
  214. depends on MFD_WM831X
  215. help
  216. This option enables support for the status LEDs of the WM831x
  217. series of PMICs.
  218. config LEDS_WM8350
  219. tristate "LED Support for WM8350 AudioPlus PMIC"
  220. depends on LEDS_CLASS
  221. depends on MFD_WM8350
  222. help
  223. This option enables support for LEDs driven by the Wolfson
  224. Microelectronics WM8350 AudioPlus PMIC.
  225. config LEDS_DA903X
  226. tristate "LED Support for DA9030/DA9034 PMIC"
  227. depends on LEDS_CLASS
  228. depends on PMIC_DA903X
  229. help
  230. This option enables support for on-chip LED drivers found
  231. on Dialog Semiconductor DA9030/DA9034 PMICs.
  232. config LEDS_DAC124S085
  233. tristate "LED Support for DAC124S085 SPI DAC"
  234. depends on LEDS_CLASS
  235. depends on SPI
  236. help
  237. This option enables support for DAC124S085 SPI DAC from NatSemi,
  238. which can be used to control up to four LEDs.
  239. config LEDS_PWM
  240. tristate "PWM driven LED Support"
  241. depends on LEDS_CLASS
  242. depends on HAVE_PWM
  243. help
  244. This option enables support for pwm driven LEDs
  245. config LEDS_REGULATOR
  246. tristate "REGULATOR driven LED support"
  247. depends on LEDS_CLASS
  248. depends on REGULATOR
  249. help
  250. This option enables support for regulator driven LEDs.
  251. config LEDS_BD2802
  252. tristate "LED driver for BD2802 RGB LED"
  253. depends on LEDS_CLASS
  254. depends on I2C
  255. help
  256. This option enables support for BD2802GU RGB LED driver chips
  257. accessed via the I2C bus.
  258. config LEDS_INTEL_SS4200
  259. tristate "LED driver for Intel NAS SS4200 series"
  260. depends on LEDS_CLASS
  261. depends on PCI && DMI
  262. help
  263. This option enables support for the Intel SS4200 series of
  264. Network Attached Storage servers. You may control the hard
  265. drive or power LEDs on the front panel. Using this driver
  266. can stop the front LED from blinking after startup.
  267. config LEDS_LT3593
  268. tristate "LED driver for LT3593 controllers"
  269. depends on LEDS_CLASS
  270. depends on GENERIC_GPIO
  271. help
  272. This option enables support for LEDs driven by a Linear Technology
  273. LT3593 controller. This controller uses a special one-wire pulse
  274. coding protocol to set the brightness.
  275. config LEDS_ADP5520
  276. tristate "LED Support for ADP5520/ADP5501 PMIC"
  277. depends on LEDS_CLASS
  278. depends on PMIC_ADP5520
  279. help
  280. This option enables support for on-chip LED drivers found
  281. on Analog Devices ADP5520/ADP5501 PMICs.
  282. To compile this driver as a module, choose M here: the module will
  283. be called leds-adp5520.
  284. config LEDS_DELL_NETBOOKS
  285. tristate "External LED on Dell Business Netbooks"
  286. depends on LEDS_CLASS
  287. depends on X86 && ACPI_WMI
  288. help
  289. This adds support for the Latitude 2100 and similar
  290. notebooks that have an external LED.
  291. config LEDS_MC13783
  292. tristate "LED Support for MC13783 PMIC"
  293. depends on LEDS_CLASS
  294. depends on MFD_MC13783
  295. help
  296. This option enable support for on-chip LED drivers found
  297. on Freescale Semiconductor MC13783 PMIC.
  298. config LEDS_NS2
  299. tristate "LED support for Network Space v2 GPIO LEDs"
  300. depends on LEDS_CLASS
  301. depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
  302. default y
  303. help
  304. This option enable support for the dual-GPIO LED found on the
  305. Network Space v2 board (and parents). This include Internet Space v2,
  306. Network Space (Max) v2 and d2 Network v2 boards.
  307. config LEDS_NETXBIG
  308. tristate "LED support for Big Network series LEDs"
  309. depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
  310. depends on LEDS_CLASS
  311. default y
  312. help
  313. This option enable support for LEDs found on the LaCie 2Big
  314. and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
  315. controlled through a GPIO extension bus.
  316. config LEDS_ASIC3
  317. bool "LED support for the HTC ASIC3"
  318. depends on LEDS_CLASS
  319. depends on MFD_ASIC3
  320. default y
  321. help
  322. This option enables support for the LEDs on the HTC ASIC3. The HTC
  323. ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
  324. cannot be used. This driver supports hardware blinking with an on+off
  325. period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
  326. config LEDS_RENESAS_TPU
  327. bool "LED support for Renesas TPU"
  328. depends on LEDS_CLASS && HAVE_CLK && GENERIC_GPIO
  329. help
  330. This option enables build of the LED TPU platform driver,
  331. suitable to drive any TPU channel on newer Renesas SoCs.
  332. The driver controls the GPIO pin connected to the LED via
  333. the GPIO framework and expects the LED to be connected to
  334. a pin that can be driven in both GPIO mode and using TPU
  335. pin function. The latter to support brightness control.
  336. Brightness control is supported but hardware blinking is not.
  337. config LEDS_TRIGGERS
  338. bool "LED Trigger support"
  339. depends on LEDS_CLASS
  340. help
  341. This option enables trigger support for the leds class.
  342. These triggers allow kernel events to drive the LEDs and can
  343. be configured via sysfs. If unsure, say Y.
  344. comment "LED Triggers"
  345. config LEDS_TRIGGER_TIMER
  346. tristate "LED Timer Trigger"
  347. depends on LEDS_TRIGGERS
  348. help
  349. This allows LEDs to be controlled by a programmable timer
  350. via sysfs. Some LED hardware can be programmed to start
  351. blinking the LED without any further software interaction.
  352. For more details read Documentation/leds/leds-class.txt.
  353. If unsure, say Y.
  354. config LEDS_TRIGGER_IDE_DISK
  355. bool "LED IDE Disk Trigger"
  356. depends on IDE_GD_ATA
  357. depends on LEDS_TRIGGERS
  358. help
  359. This allows LEDs to be controlled by IDE disk activity.
  360. If unsure, say Y.
  361. config LEDS_TRIGGER_HEARTBEAT
  362. tristate "LED Heartbeat Trigger"
  363. depends on LEDS_TRIGGERS
  364. help
  365. This allows LEDs to be controlled by a CPU load average.
  366. The flash frequency is a hyperbolic function of the 1-minute
  367. load average.
  368. If unsure, say Y.
  369. config LEDS_TRIGGER_BACKLIGHT
  370. tristate "LED backlight Trigger"
  371. depends on LEDS_TRIGGERS
  372. help
  373. This allows LEDs to be controlled as a backlight device: they
  374. turn off and on when the display is blanked and unblanked.
  375. If unsure, say N.
  376. config LEDS_TRIGGER_GPIO
  377. tristate "LED GPIO Trigger"
  378. depends on LEDS_TRIGGERS
  379. depends on GPIOLIB
  380. help
  381. This allows LEDs to be controlled by gpio events. It's good
  382. when using gpios as switches and triggering the needed LEDs
  383. from there. One use case is n810's keypad LEDs that could
  384. be triggered by this trigger when user slides up to show
  385. keypad.
  386. If unsure, say N.
  387. config LEDS_TRIGGER_DEFAULT_ON
  388. tristate "LED Default ON Trigger"
  389. depends on LEDS_TRIGGERS
  390. help
  391. This allows LEDs to be initialised in the ON state.
  392. If unsure, say Y.
  393. comment "iptables trigger is under Netfilter config (LED target)"
  394. depends on LEDS_TRIGGERS
  395. endif # NEW_LEDS