Kconfig 16 KB

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