Kconfig 14 KB

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