Kconfig 32 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config LEDS_GPIO_REGISTER
  3. bool
  4. help
  5. This option provides the function gpio_led_register_device.
  6. As this function is used by arch code it must not be compiled as a
  7. module.
  8. # This library does not depend on NEW_LEDS and must be independent so it can be
  9. # selected from other subsystems (specifically backlight).
  10. config LEDS_EXPRESSWIRE
  11. bool
  12. depends on GPIOLIB
  13. menuconfig NEW_LEDS
  14. bool "LED Support"
  15. help
  16. Say Y to enable Linux LED support. This allows control of supported
  17. LEDs from both userspace and optionally, by kernel events (triggers).
  18. if NEW_LEDS
  19. config LEDS_CLASS
  20. tristate "LED Class Support"
  21. help
  22. This option enables the LED sysfs class in /sys/class/leds. You'll
  23. need this to do anything useful with LEDs. If unsure, say Y.
  24. config LEDS_CLASS_FLASH
  25. tristate "LED Flash Class Support"
  26. depends on LEDS_CLASS
  27. help
  28. This option enables the flash LED sysfs class in /sys/class/leds.
  29. It wraps LED Class and adds flash LEDs specific sysfs attributes
  30. and kernel internal API to it. You'll need this to provide support
  31. for the flash related features of a LED device. It can be built
  32. as a module.
  33. config LEDS_CLASS_MULTICOLOR
  34. tristate "LED Multicolor Class Support"
  35. depends on LEDS_CLASS
  36. help
  37. This option enables the multicolor LED sysfs class in /sys/class/leds.
  38. It wraps LED class and adds multicolor LED specific sysfs attributes
  39. and kernel internal API to it. You'll need this to provide support
  40. for multicolor LEDs that are grouped together. This class is not
  41. intended for single color LEDs. It can be built as a module.
  42. config LEDS_BRIGHTNESS_HW_CHANGED
  43. bool "LED Class brightness_hw_changed attribute support"
  44. depends on LEDS_CLASS
  45. help
  46. This option enables support for the brightness_hw_changed attribute
  47. for LED sysfs class devices under /sys/class/leds.
  48. See Documentation/ABI/testing/sysfs-class-led for details.
  49. config LEDS_KUNIT_TEST
  50. tristate "KUnit tests for LEDs"
  51. depends on KUNIT && LEDS_CLASS
  52. default KUNIT_ALL_TESTS
  53. help
  54. Say Y here to enable KUnit testing for the LEDs framework.
  55. comment "LED drivers"
  56. config LEDS_88PM860X
  57. tristate "LED Support for Marvell 88PM860x PMIC"
  58. depends on LEDS_CLASS
  59. depends on MFD_88PM860X
  60. help
  61. This option enables support for on-chip LED drivers found on Marvell
  62. Semiconductor 88PM8606 PMIC.
  63. config LEDS_AN30259A
  64. tristate "LED support for Panasonic AN30259A"
  65. depends on LEDS_CLASS && I2C && OF
  66. help
  67. This option enables support for the AN30259A 3-channel
  68. LED driver.
  69. To compile this driver as a module, choose M here: the module
  70. will be called leds-an30259a.
  71. config LEDS_APU
  72. tristate "Front panel LED support for PC Engines APU/APU2/APU3 boards"
  73. depends on LEDS_CLASS
  74. depends on X86 && DMI
  75. help
  76. This driver makes the PC Engines APU1 front panel LEDs
  77. accessible from userspace programs through the LED subsystem.
  78. If you're looking for APU2/3, use the pcengines-apu2 driver.
  79. (symbol CONFIG_PCENGINES_APU2)
  80. To compile this driver as a module, choose M here: the
  81. module will be called leds-apu.
  82. config LEDS_ARIEL
  83. tristate "Dell Wyse 3020 status LED support"
  84. depends on LEDS_CLASS
  85. depends on (MACH_MMP3_DT && MFD_ENE_KB3930) || COMPILE_TEST
  86. help
  87. This driver adds support for controlling the front panel status
  88. LEDs on Dell Wyse 3020 (Ariel) board via the KB3930 Embedded
  89. Controller.
  90. Say Y to if your machine is a Dell Wyse 3020 thin client.
  91. config LEDS_OSRAM_AMS_AS3668
  92. tristate "LED support for Osram AMS AS3668"
  93. depends on LEDS_CLASS
  94. depends on I2C
  95. help
  96. This option enables support for the Osram AMS AS3668 LED controller.
  97. The AS3668 provides up to four LED channels and is controlled via
  98. the I2C bus. This driver offers basic brightness control for each
  99. channel, without support for blinking or other advanced features.
  100. To compile this driver as a module, choose M here: the module
  101. will be called leds-as3668.
  102. config LEDS_AW200XX
  103. tristate "LED support for Awinic AW20036/AW20054/AW20072/AW20108"
  104. depends on LEDS_CLASS
  105. depends on I2C
  106. help
  107. This option enables support for the Awinic AW200XX LED controllers.
  108. It is a matrix LED driver programmed via an I2C interface. Devices have
  109. a set of individually controlled LEDs and support 3 pattern controllers
  110. for auto breathing or group dimming control. Supported devices:
  111. - AW20036 (3x12) 36 LEDs
  112. - AW20054 (6x9) 54 LEDs
  113. - AW20072 (6x12) 72 LEDs
  114. - AW20108 (9x12) 108 LEDs
  115. To compile this driver as a module, choose M here: the module
  116. will be called leds-aw200xx.
  117. config LEDS_AW2013
  118. tristate "LED support for Awinic AW2013"
  119. depends on LEDS_CLASS && I2C && OF
  120. select REGMAP_I2C
  121. help
  122. This option enables support for the AW2013 3-channel
  123. LED driver.
  124. To compile this driver as a module, choose M here: the module
  125. will be called leds-aw2013.
  126. config LEDS_BCM6328
  127. tristate "LED Support for Broadcom BCM6328"
  128. depends on LEDS_CLASS
  129. depends on HAS_IOMEM
  130. depends on OF
  131. help
  132. This option enables support for LEDs connected to the BCM6328
  133. LED HW controller accessed via MMIO registers.
  134. config LEDS_BCM6358
  135. tristate "LED Support for Broadcom BCM6358"
  136. depends on LEDS_CLASS
  137. depends on HAS_IOMEM
  138. depends on OF
  139. help
  140. This option enables support for LEDs connected to the BCM6358
  141. LED HW controller accessed via MMIO registers.
  142. config LEDS_CHT_WCOVE
  143. tristate "LED support for Intel Cherry Trail Whiskey Cove PMIC"
  144. depends on LEDS_CLASS
  145. depends on INTEL_SOC_PMIC_CHTWC
  146. help
  147. This option enables support for charger and general purpose LEDs
  148. connected to the Intel Cherrytrail Whiskey Cove PMIC.
  149. To compile this driver as a module, choose M here: the module
  150. will be called leds-cht-wcove.
  151. config LEDS_CPCAP
  152. tristate "LED Support for Motorola CPCAP"
  153. depends on LEDS_CLASS
  154. depends on MFD_CPCAP
  155. depends on OF
  156. help
  157. This option enables support for LEDs offered by Motorola's
  158. CPCAP PMIC.
  159. config LEDS_CR0014114
  160. tristate "LED Support for Crane CR0014114"
  161. depends on LEDS_CLASS
  162. depends on SPI
  163. depends on OF
  164. help
  165. This option enables support for CR0014114 LED Board which
  166. is widely used in vending machines produced by
  167. Crane Merchandising Systems.
  168. To compile this driver as a module, choose M here: the module
  169. will be called leds-cr0014114.
  170. config LEDS_CROS_EC
  171. tristate "LED Support for ChromeOS EC"
  172. depends on MFD_CROS_EC_DEV
  173. depends on LEDS_CLASS_MULTICOLOR
  174. select LEDS_TRIGGERS
  175. default MFD_CROS_EC_DEV
  176. help
  177. This option enables support for LEDs managed by ChromeOS ECs.
  178. All LEDs exposed by the EC are supported in multicolor mode.
  179. A hardware trigger to switch back to the automatic behaviour is
  180. provided.
  181. To compile this driver as a module, choose M here: the module
  182. will be called leds-cros_ec.
  183. config LEDS_EL15203000
  184. tristate "LED Support for Crane EL15203000"
  185. depends on LEDS_CLASS
  186. depends on SPI
  187. depends on OF
  188. help
  189. This option enables support for EL15203000 LED Board
  190. (aka RED LED board) which is widely used in coffee vending
  191. machines produced by Crane Merchandising Systems.
  192. To compile this driver as a module, choose M here: the module
  193. will be called leds-el15203000.
  194. config LEDS_TURRIS_OMNIA
  195. tristate "LED support for CZ.NIC's Turris Omnia"
  196. depends on LEDS_CLASS_MULTICOLOR
  197. depends on I2C
  198. depends on MACH_ARMADA_38X || COMPILE_TEST
  199. depends on OF
  200. depends on TURRIS_OMNIA_MCU
  201. depends on TURRIS_OMNIA_MCU_GPIO
  202. select LEDS_TRIGGERS
  203. help
  204. This option enables basic support for the LEDs found on the front
  205. side of CZ.NIC's Turris Omnia router. There are 12 RGB LEDs on the
  206. front panel.
  207. config LEDS_LM3530
  208. tristate "LCD Backlight driver for LM3530"
  209. depends on LEDS_CLASS
  210. depends on I2C
  211. help
  212. This option enables support for the LCD backlight using
  213. LM3530 ambient light sensor chip. This ALS chip can be
  214. controlled manually or using PWM input or using ambient
  215. light automatically.
  216. config LEDS_LM3532
  217. tristate "LCD Backlight driver for LM3532"
  218. select REGMAP_I2C
  219. depends on LEDS_CLASS
  220. depends on I2C
  221. help
  222. This option enables support for the LCD backlight using
  223. LM3532 ambient light sensor chip. This ALS chip can be
  224. controlled manually or using PWM input or using ambient
  225. light automatically.
  226. config LEDS_LM3533
  227. tristate "LED support for LM3533"
  228. depends on LEDS_CLASS
  229. depends on MFD_LM3533
  230. help
  231. This option enables support for the LEDs on National Semiconductor /
  232. TI LM3533 Lighting Power chips.
  233. The LEDs can be controlled directly, through PWM input, or by the
  234. ambient-light-sensor interface. The chip supports
  235. hardware-accelerated blinking with maximum on and off periods of 9.8
  236. and 77 seconds respectively.
  237. config LEDS_LM3642
  238. tristate "LED support for LM3642 Chip"
  239. depends on LEDS_CLASS && I2C
  240. select REGMAP_I2C
  241. help
  242. This option enables support for LEDs connected to LM3642.
  243. The LM3642 is a 4MHz fixed-frequency synchronous boost
  244. converter plus 1.5A constant current driver for a high-current
  245. white LED.
  246. config LEDS_LM3692X
  247. tristate "LED support for LM3692x Chips"
  248. depends on LEDS_CLASS && I2C && OF
  249. select REGMAP_I2C
  250. help
  251. This option enables support for the TI LM3692x family
  252. of white LED string drivers used for backlighting.
  253. config LEDS_LOCOMO
  254. tristate "LED Support for Locomo device"
  255. depends on LEDS_CLASS
  256. depends on SHARP_LOCOMO
  257. help
  258. This option enables support for the LEDs on Sharp Locomo.
  259. Zaurus models SL-5500 and SL-5600.
  260. config LEDS_MIKROTIK_RB532
  261. tristate "LED Support for Mikrotik Routerboard 532"
  262. depends on LEDS_CLASS
  263. depends on MIKROTIK_RB532
  264. help
  265. This option enables support for the so called "User LED" of
  266. Mikrotik's Routerboard 532.
  267. config LEDS_MT6323
  268. tristate "LED Support for Mediatek MT6323 PMIC"
  269. depends on LEDS_CLASS
  270. depends on MFD_MT6397
  271. help
  272. This option enables support for on-chip LED drivers found on
  273. Mediatek MT6323 PMIC.
  274. config LEDS_NET48XX
  275. tristate "LED Support for Soekris net48xx series Error LED"
  276. depends on LEDS_CLASS
  277. depends on SCx200_GPIO
  278. help
  279. This option enables support for the Soekris net4801 and net4826 error
  280. LED.
  281. config LEDS_WRAP
  282. tristate "LED Support for the WRAP series LEDs"
  283. depends on LEDS_CLASS
  284. depends on SCx200_GPIO
  285. help
  286. This option enables support for the PCEngines WRAP programmable LEDs.
  287. config LEDS_COBALT_QUBE
  288. tristate "LED Support for the Cobalt Qube series front LED"
  289. depends on LEDS_CLASS
  290. depends on MIPS_COBALT || COMPILE_TEST
  291. help
  292. This option enables support for the front LED on Cobalt Qube series
  293. config LEDS_COBALT_RAQ
  294. bool "LED Support for the Cobalt Raq series"
  295. depends on LEDS_CLASS=y && (MIPS_COBALT || COMPILE_TEST)
  296. select LEDS_TRIGGERS
  297. help
  298. This option enables support for the Cobalt Raq series LEDs.
  299. config LEDS_SUN50I_A100
  300. tristate "LED support for Allwinner A100 RGB LED controller"
  301. depends on LEDS_CLASS_MULTICOLOR
  302. depends on ARCH_SUNXI || COMPILE_TEST
  303. help
  304. This option enables support for the RGB LED controller found
  305. in some Allwinner sunxi SoCs, including A100, R329, and D1.
  306. It uses a one-wire interface to control up to 1024 LEDs.
  307. config LEDS_SUNFIRE
  308. tristate "LED support for SunFire servers."
  309. depends on LEDS_CLASS
  310. depends on SPARC64
  311. select LEDS_TRIGGERS
  312. help
  313. This option enables support for the Left, Middle, and Right
  314. LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
  315. config LEDS_IPAQ_MICRO
  316. tristate "LED Support for the Compaq iPAQ h3xxx"
  317. depends on LEDS_CLASS
  318. depends on MFD_IPAQ_MICRO
  319. help
  320. Choose this option if you want to use the notification LED on
  321. Compaq/HP iPAQ h3100 and h3600.
  322. config LEDS_HP6XX
  323. tristate "LED Support for the HP Jornada 6xx"
  324. depends on LEDS_CLASS
  325. depends on SH_HP6XX
  326. help
  327. This option enables LED support for the handheld
  328. HP Jornada 620/660/680/690.
  329. config LEDS_PCA9532
  330. tristate "LED driver for PCA9532 dimmer"
  331. depends on LEDS_CLASS
  332. depends on I2C && INPUT
  333. help
  334. This option enables support for NXP pca9532
  335. LED controller. It is generally only useful
  336. as a platform driver
  337. config LEDS_PCA9532_GPIO
  338. bool "Enable GPIO support for PCA9532"
  339. depends on LEDS_PCA9532
  340. depends on GPIOLIB
  341. help
  342. Allow unused pins on PCA9532 to be used as gpio.
  343. To use a pin as gpio pca9532_type in pca9532_platform data needs to
  344. set to PCA9532_TYPE_GPIO.
  345. config LEDS_GPIO
  346. tristate "LED Support for GPIO connected LEDs"
  347. depends on LEDS_CLASS
  348. depends on GPIOLIB || COMPILE_TEST
  349. help
  350. This option enables support for the LEDs connected to GPIO
  351. outputs. To be useful the particular board must have LEDs
  352. and they must be connected to the GPIO lines. The LEDs must be
  353. defined as platform devices and/or OpenFirmware platform devices.
  354. The code to use these bindings can be selected below.
  355. config LEDS_LP3944
  356. tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
  357. depends on LEDS_CLASS
  358. depends on I2C
  359. help
  360. This option enables support for LEDs connected to the National
  361. Semiconductor LP3944 Lighting Management Unit (LMU) also known as
  362. Fun Light Chip.
  363. To compile this driver as a module, choose M here: the
  364. module will be called leds-lp3944.
  365. config LEDS_LP3952
  366. tristate "LED Support for TI LP3952 2 channel LED driver"
  367. depends on LEDS_CLASS
  368. depends on I2C
  369. depends on GPIOLIB
  370. select REGMAP_I2C
  371. help
  372. This option enables support for LEDs connected to the Texas
  373. Instruments LP3952 LED driver.
  374. To compile this driver as a module, choose M here: the
  375. module will be called leds-lp3952.
  376. config LEDS_LP50XX
  377. tristate "LED Support for TI LP5036/30/24/18/12/09 LED driver chip"
  378. depends on LEDS_CLASS && REGMAP_I2C
  379. depends on LEDS_CLASS_MULTICOLOR
  380. help
  381. If you say yes here you get support for the Texas Instruments
  382. LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 LED driver.
  383. To compile this driver as a module, choose M here: the
  384. module will be called leds-lp50xx.
  385. config LEDS_LP55XX_COMMON
  386. tristate "Common Driver for TI/National LP5521/5523/55231/5562/5569/8501"
  387. depends on LEDS_CLASS
  388. depends on LEDS_CLASS_MULTICOLOR
  389. depends on OF
  390. depends on I2C
  391. imply FW_LOADER
  392. imply FW_LOADER_USER_HELPER
  393. help
  394. This option supports common operations for LP5521/5523/55231/5562/5569/
  395. 8501 devices.
  396. config LEDS_LP5521
  397. tristate "LED Support for N.S. LP5521 LED driver chip"
  398. depends on LEDS_CLASS && I2C
  399. depends on LEDS_LP55XX_COMMON
  400. help
  401. If you say yes here you get support for the National Semiconductor
  402. LP5521 LED driver. It is 3 channel chip with programmable engines.
  403. Driver provides direct control via LED class and interface for
  404. programming the engines.
  405. config LEDS_LP5523
  406. tristate "LED Support for TI/National LP5523/55231 LED driver chip"
  407. depends on LEDS_CLASS && I2C
  408. depends on LEDS_LP55XX_COMMON
  409. help
  410. If you say yes here you get support for TI/National Semiconductor
  411. LP5523/55231 LED driver.
  412. It is 9 channel chip with programmable engines.
  413. Driver provides direct control via LED class and interface for
  414. programming the engines.
  415. config LEDS_LP5562
  416. tristate "LED Support for TI LP5562 LED driver chip"
  417. depends on LEDS_CLASS && I2C
  418. depends on LEDS_LP55XX_COMMON
  419. help
  420. If you say yes here you get support for TI LP5562 LED driver.
  421. It is 4 channels chip with programmable engines.
  422. Driver provides direct control via LED class and interface for
  423. programming the engines.
  424. config LEDS_LP5569
  425. tristate "LED Support for TI LP5569 LED driver chip"
  426. depends on LEDS_CLASS && I2C
  427. depends on LEDS_LP55XX_COMMON
  428. help
  429. If you say yes here you get support for TI LP5569 LED driver.
  430. It is 9 channels chip with programmable engines.
  431. Driver provides direct control via LED class and interface for
  432. programming the engines.
  433. config LEDS_LP8501
  434. tristate "LED Support for TI LP8501 LED driver chip"
  435. depends on LEDS_CLASS && I2C
  436. depends on LEDS_LP55XX_COMMON
  437. help
  438. If you say yes here you get support for TI LP8501 LED driver.
  439. It is 9 channel chip with programmable engines.
  440. Driver provides direct control via LED class and interface for
  441. programming the engines.
  442. It is similar as LP5523, but output power selection is available.
  443. And register layout and engine program schemes are different.
  444. config LEDS_LP8788
  445. tristate "LED support for the TI LP8788 PMIC"
  446. depends on LEDS_CLASS
  447. depends on MFD_LP8788
  448. help
  449. This option enables support for the Keyboard LEDs on the LP8788 PMIC.
  450. config LEDS_LP8860
  451. tristate "LED support for the TI LP8860 4 channel LED driver"
  452. depends on LEDS_CLASS && I2C && OF
  453. select REGMAP_I2C
  454. help
  455. If you say yes here you get support for the TI LP8860 4 channel
  456. LED driver.
  457. This option enables support for the display cluster LEDs
  458. on the LP8860 4 channel LED driver using the I2C communication
  459. bus.
  460. config LEDS_LP8864
  461. tristate "LED support for the TI LP8864/LP8866 4/6 channel LED drivers"
  462. depends on LEDS_CLASS && I2C && OF
  463. select REGMAP_I2C
  464. help
  465. If you say yes here you get support for the TI LP8864-Q1,
  466. LP8864S-Q1, LP8866-Q1, LP8866S-Q1 4/6 channel LED backlight
  467. drivers with I2C interface.
  468. To compile this driver as a module, choose M here: the
  469. module will be called leds-lp8864.
  470. config LEDS_CLEVO_MAIL
  471. tristate "Mail LED on Clevo notebook"
  472. depends on LEDS_CLASS && BROKEN
  473. depends on X86 && SERIO_I8042 && DMI
  474. help
  475. This driver makes the mail LED accessible from userspace
  476. programs through the LEDs subsystem. This LED has three
  477. known modes: off, blink at 0.5Hz and blink at 1Hz.
  478. The driver supports two kinds of interface: using ledtrig-timer
  479. or through /sys/class/leds/clevo::mail/brightness. As this LED
  480. cannot change its brightness it blinks instead. The brightness
  481. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  482. blink at 1Hz.
  483. This module can drive the mail LED for the following notebooks:
  484. Clevo D400P
  485. Clevo D410J
  486. Clevo D410V
  487. Clevo D400V/D470V (not tested, but might work)
  488. Clevo M540N
  489. Clevo M5x0N (not tested, but might work)
  490. Positivo Mobile (Clevo M5x0V)
  491. If your model is not listed here you can try the "nodetect"
  492. module parameter.
  493. To compile this driver as a module, choose M here: the
  494. module will be called leds-clevo-mail.
  495. config LEDS_PCA955X
  496. tristate "LED Support for PCA955x I2C chips"
  497. depends on LEDS_CLASS
  498. depends on I2C
  499. help
  500. This option enables support for LEDs connected to PCA955x
  501. LED driver chips accessed via the I2C bus. Supported
  502. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  503. config LEDS_PCA955X_GPIO
  504. bool "Enable GPIO support for PCA955X"
  505. depends on LEDS_PCA955X
  506. depends on GPIOLIB
  507. help
  508. Allow unused pins on PCA955X to be used as gpio.
  509. To use a pin as gpio the pin type should be set to
  510. PCA955X_TYPE_GPIO in the device tree.
  511. config LEDS_PCA963X
  512. tristate "LED support for PCA963x I2C chip"
  513. depends on LEDS_CLASS
  514. depends on I2C
  515. help
  516. This option enables support for LEDs connected to the PCA963x
  517. LED driver chip accessed via the I2C bus. Supported
  518. devices include PCA9633 and PCA9634
  519. config LEDS_PCA995X
  520. tristate "LED Support for PCA995x I2C chips"
  521. depends on LEDS_CLASS
  522. depends on I2C
  523. help
  524. This option enables support for LEDs connected to PCA995x
  525. LED driver chips accessed via the I2C bus. Supported
  526. devices include PCA9955BTW, PCA9952TW and PCA9955TW.
  527. config LEDS_QNAP_MCU
  528. tristate "LED Support for QNAP MCU controllers"
  529. depends on LEDS_CLASS
  530. depends on MFD_QNAP_MCU
  531. help
  532. This option enables support for LEDs available on embedded
  533. controllers used in QNAP NAS devices.
  534. This driver can also be built as a module. If so, the module
  535. will be called qnap-mcu-leds.
  536. config LEDS_WM831X_STATUS
  537. tristate "LED support for status LEDs on WM831x PMICs"
  538. depends on LEDS_CLASS
  539. depends on MFD_WM831X
  540. help
  541. This option enables support for the status LEDs of the WM831x
  542. series of PMICs.
  543. config LEDS_WM8350
  544. tristate "LED Support for WM8350 AudioPlus PMIC"
  545. depends on LEDS_CLASS
  546. depends on MFD_WM8350
  547. help
  548. This option enables support for LEDs driven by the Wolfson
  549. Microelectronics WM8350 AudioPlus PMIC.
  550. config LEDS_DA903X
  551. tristate "LED Support for DA9030/DA9034 PMIC"
  552. depends on LEDS_CLASS
  553. depends on PMIC_DA903X
  554. help
  555. This option enables support for on-chip LED drivers found
  556. on Dialog Semiconductor DA9030/DA9034 PMICs.
  557. config LEDS_DA9052
  558. tristate "Dialog DA9052/DA9053 LEDS"
  559. depends on LEDS_CLASS
  560. depends on PMIC_DA9052
  561. help
  562. This option enables support for on-chip LED drivers found
  563. on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
  564. config LEDS_DAC124S085
  565. tristate "LED Support for DAC124S085 SPI DAC"
  566. depends on LEDS_CLASS
  567. depends on SPI
  568. help
  569. This option enables support for DAC124S085 SPI DAC from NatSemi,
  570. which can be used to control up to four LEDs.
  571. config LEDS_PWM
  572. tristate "PWM driven LED Support"
  573. depends on LEDS_CLASS
  574. depends on PWM
  575. help
  576. This option enables support for pwm driven LEDs
  577. config LEDS_REGULATOR
  578. tristate "REGULATOR driven LED support"
  579. depends on LEDS_CLASS
  580. depends on REGULATOR
  581. help
  582. This option enables support for regulator driven LEDs.
  583. config LEDS_BD2606MVV
  584. tristate "LED driver for BD2606MVV"
  585. depends on LEDS_CLASS
  586. depends on I2C
  587. select REGMAP_I2C
  588. help
  589. This option enables support for BD2606MVV LED driver chips
  590. accessed via the I2C bus. It supports setting brightness, with
  591. the limitation that there are groups of two channels sharing
  592. a brightness setting, but not the on/off setting.
  593. To compile this driver as a module, choose M here: the module will
  594. be called leds-bd2606mvv.
  595. config LEDS_BD2802
  596. tristate "LED driver for BD2802 RGB LED"
  597. depends on LEDS_CLASS
  598. depends on I2C
  599. help
  600. This option enables support for BD2802GU RGB LED driver chips
  601. accessed via the I2C bus.
  602. config LEDS_INTEL_SS4200
  603. tristate "LED driver for Intel NAS SS4200 series"
  604. depends on LEDS_CLASS
  605. depends on PCI && DMI
  606. depends on X86
  607. help
  608. This option enables support for the Intel SS4200 series of
  609. Network Attached Storage servers. You may control the hard
  610. drive or power LEDs on the front panel. Using this driver
  611. can stop the front LED from blinking after startup.
  612. config LEDS_LT3593
  613. tristate "LED driver for LT3593 controllers"
  614. depends on LEDS_CLASS
  615. depends on GPIOLIB || COMPILE_TEST
  616. help
  617. This option enables support for LEDs driven by a Linear Technology
  618. LT3593 controller. This controller uses a special one-wire pulse
  619. coding protocol to set the brightness.
  620. config LEDS_ADP5520
  621. tristate "LED Support for ADP5520/ADP5501 PMIC"
  622. depends on LEDS_CLASS
  623. depends on PMIC_ADP5520
  624. help
  625. This option enables support for on-chip LED drivers found
  626. on Analog Devices ADP5520/ADP5501 PMICs.
  627. To compile this driver as a module, choose M here: the module will
  628. be called leds-adp5520.
  629. config LEDS_MAX5970
  630. tristate "LED Support for Maxim 5970"
  631. depends on LEDS_CLASS
  632. depends on MFD_MAX5970
  633. help
  634. This option enables support for the Maxim MAX5970 & MAX5978 smart
  635. switch indication LEDs via the I2C bus.
  636. To compile this driver as a module, choose M here: the module will
  637. be called leds-max5970.
  638. config LEDS_MC13783
  639. tristate "LED Support for MC13XXX PMIC"
  640. depends on LEDS_CLASS
  641. depends on MFD_MC13XXX
  642. help
  643. This option enables support for on-chip LED drivers found
  644. on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC.
  645. config LEDS_NS2
  646. tristate "LED support for Network Space v2 GPIO LEDs"
  647. depends on LEDS_CLASS
  648. depends on MACH_KIRKWOOD || MACH_ARMADA_370 || COMPILE_TEST
  649. default y if MACH_KIRKWOOD || MACH_ARMADA_370
  650. help
  651. This option enables support for the dual-GPIO LEDs found on the
  652. following LaCie/Seagate boards:
  653. Network Space v2 (and parents: Max, Mini)
  654. Internet Space v2
  655. d2 Network v2
  656. n090401 (Seagate NAS 4-Bay)
  657. config LEDS_NETXBIG
  658. tristate "LED support for Big Network series LEDs"
  659. depends on LEDS_CLASS
  660. depends on MACH_KIRKWOOD || COMPILE_TEST
  661. depends on OF_GPIO
  662. default MACH_KIRKWOOD
  663. help
  664. This option enables support for LEDs found on the LaCie 2Big
  665. and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
  666. controlled through a GPIO extension bus.
  667. config LEDS_TCA6507
  668. tristate "LED Support for TCA6507 I2C chip"
  669. depends on LEDS_CLASS && I2C
  670. help
  671. This option enables support for LEDs connected to TC6507
  672. LED driver chips accessed via the I2C bus.
  673. Driver support brightness control and hardware-assisted blinking.
  674. config LEDS_TLC591XX
  675. tristate "LED driver for TLC59108 and TLC59116 controllers"
  676. depends on LEDS_CLASS && I2C
  677. select REGMAP_I2C
  678. help
  679. This option enables support for Texas Instruments TLC59108
  680. and TLC59116 LED controllers.
  681. config LEDS_MAX77650
  682. tristate "LED support for Maxim MAX77650 PMIC"
  683. depends on LEDS_CLASS && MFD_MAX77650
  684. help
  685. LEDs driver for MAX77650 family of PMICs from Maxim Integrated.
  686. config LEDS_MAX77705
  687. tristate "LED support for Maxim MAX77705 PMIC"
  688. depends on MFD_MAX77705
  689. depends on LEDS_CLASS
  690. depends on LEDS_CLASS_MULTICOLOR
  691. help
  692. LED driver for MAX77705 PMIC from Maxim Integrated.
  693. config LEDS_MAX8997
  694. tristate "LED support for MAX8997 PMIC"
  695. depends on LEDS_CLASS && MFD_MAX8997
  696. help
  697. This option enables support for on-chip LED drivers on
  698. MAXIM MAX8997 PMIC.
  699. config LEDS_LM355x
  700. tristate "LED support for LM3554 and LM3556 chips"
  701. depends on LEDS_CLASS && I2C
  702. select REGMAP_I2C
  703. help
  704. This option enables support for LEDs connected to LM3554
  705. and LM3556. It includes Torch, Flash and Indicator functions.
  706. config LEDS_OT200
  707. tristate "LED support for the Bachmann OT200"
  708. depends on LEDS_CLASS && HAS_IOPORT && (X86_32 || COMPILE_TEST)
  709. help
  710. This option enables support for the LEDs on the Bachmann OT200.
  711. Say Y to enable LEDs on the Bachmann OT200.
  712. config LEDS_MENF21BMC
  713. tristate "LED support for the MEN 14F021P00 BMC"
  714. depends on LEDS_CLASS && MFD_MENF21BMC
  715. help
  716. Say Y here to include support for the MEN 14F021P00 BMC LEDs.
  717. This driver can also be built as a module. If so the module
  718. will be called leds-menf21bmc.
  719. config LEDS_IS31FL319X
  720. tristate "LED Support for ISSI IS31FL319x I2C LED controller family"
  721. depends on LEDS_CLASS && I2C
  722. select REGMAP_I2C
  723. help
  724. This option enables support for LEDs connected to ISSI IS31FL319x
  725. fancy LED driver chips accessed via the I2C bus.
  726. Driver supports individual PWM brightness control for each channel.
  727. This driver can also be built as a module. If so the module will be
  728. called leds-is31fl319x.
  729. config LEDS_IS31FL32XX
  730. tristate "LED support for ISSI IS31FL32XX I2C LED controller family"
  731. depends on LEDS_CLASS && I2C && OF
  732. help
  733. Say Y here to include support for ISSI IS31FL32XX and Si-En SN32xx
  734. LED controllers. They are I2C devices with multiple constant-current
  735. channels, each with independent 256-level PWM control.
  736. config LEDS_SC27XX_BLTC
  737. tristate "LED support for the SC27xx breathing light controller"
  738. depends on LEDS_CLASS && MFD_SC27XX_PMIC
  739. depends on OF
  740. help
  741. Say Y here to include support for the SC27xx breathing light controller
  742. LEDs.
  743. This driver can also be built as a module. If so the module will be
  744. called leds-sc27xx-bltc.
  745. config LEDS_UPBOARD
  746. tristate "LED support for the UP board"
  747. depends on LEDS_CLASS && MFD_UPBOARD_FPGA
  748. help
  749. This option enables support for the UP board LEDs.
  750. This driver can also be built as a module. If so the module will be
  751. called leds-upboard.
  752. comment "LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)"
  753. config LEDS_BLINKM
  754. tristate "LED support for the BlinkM I2C RGB LED"
  755. depends on LEDS_CLASS
  756. depends on I2C
  757. help
  758. This option enables support for the BlinkM RGB LED connected
  759. through I2C. Say Y to enable support for the BlinkM LED.
  760. config LEDS_BLINKM_MULTICOLOR
  761. bool "Enable multicolor support for BlinkM I2C RGB LED"
  762. depends on LEDS_BLINKM
  763. depends on LEDS_CLASS_MULTICOLOR=y || LEDS_CLASS_MULTICOLOR=LEDS_BLINKM
  764. help
  765. This option enables multicolor sysfs class support for BlinkM LED and
  766. disables the older, separated sysfs interface
  767. config LEDS_POWERNV
  768. tristate "LED support for PowerNV Platform"
  769. depends on LEDS_CLASS
  770. depends on PPC_POWERNV
  771. depends on OF
  772. help
  773. This option enables support for the system LEDs present on
  774. PowerNV platforms. Say 'y' to enable this support in kernel.
  775. To compile this driver as a module, choose 'm' here: the module
  776. will be called leds-powernv.
  777. config LEDS_SYSCON
  778. bool "LED support for LEDs on system controllers"
  779. depends on LEDS_CLASS=y
  780. depends on MFD_SYSCON
  781. depends on OF
  782. help
  783. This option enables support for the LEDs on syscon type
  784. devices. This will only work with device tree enabled
  785. devices.
  786. config LEDS_PM8058
  787. tristate "LED Support for the Qualcomm PM8058 PMIC"
  788. depends on MFD_PM8XXX
  789. depends on LEDS_CLASS
  790. help
  791. Choose this option if you want to use the LED drivers in
  792. the Qualcomm PM8058 PMIC.
  793. config LEDS_MLXCPLD
  794. tristate "LED support for the Mellanox boards"
  795. depends on X86 && DMI
  796. depends on LEDS_CLASS
  797. help
  798. This option enables support for the LEDs on the Mellanox
  799. boards. Say Y to enable these.
  800. config LEDS_MLXREG
  801. tristate "LED support for the Mellanox switches management control"
  802. depends on LEDS_CLASS
  803. help
  804. This option enables support for the LEDs on the Mellanox Ethernet and
  805. InfiniBand switches. The driver can be activated by the platform device
  806. device add call. Say Y to enable these. To compile this driver as a
  807. module, choose 'M' here: the module will be called leds-mlxreg.
  808. config LEDS_USER
  809. tristate "Userspace LED support"
  810. depends on LEDS_CLASS
  811. help
  812. This option enables support for userspace LEDs. Say 'y' to enable this
  813. support in kernel. To compile this driver as a module, choose 'm' here:
  814. the module will be called uleds.
  815. config LEDS_NIC78BX
  816. tristate "LED support for NI PXI NIC78bx devices"
  817. depends on LEDS_CLASS
  818. depends on HAS_IOPORT
  819. depends on X86 || COMPILE_TEST
  820. help
  821. This option enables support for the User1 and User2 LEDs on NI
  822. PXI NIC78bx devices.
  823. To compile this driver as a module, choose M here: the module
  824. will be called leds-nic78bx.
  825. config LEDS_SPI_BYTE
  826. tristate "LED support for SPI LED controller with a single byte"
  827. depends on LEDS_CLASS
  828. depends on SPI
  829. help
  830. This option enables support for LED controller which use a single byte
  831. for controlling the brightness. Currently the following controller is
  832. supported: Ubiquiti airCube ISP microcontroller based LED controller.
  833. config LEDS_TI_LMU_COMMON
  834. tristate "LED driver for TI LMU" if COMPILE_TEST
  835. select REGMAP
  836. help
  837. Say Y to enable the LED driver for TI LMU devices.
  838. This supports common features between the TI LM3532, LM3631, LM3632,
  839. LM3633, LM3695 and LM3697.
  840. config LEDS_LM3697
  841. tristate "LED driver for LM3697"
  842. depends on LEDS_CLASS && I2C && OF
  843. select LEDS_TI_LMU_COMMON
  844. help
  845. Say Y to enable the LM3697 LED driver for TI LMU devices.
  846. This supports the LED device LM3697.
  847. config LEDS_LM36274
  848. tristate "LED driver for LM36274"
  849. depends on LEDS_CLASS && MFD_TI_LMU
  850. select LEDS_TI_LMU_COMMON
  851. help
  852. Say Y to enable the LM36274 LED driver for TI LMU devices.
  853. This supports the LED device LM36274.
  854. config LEDS_ST1202
  855. tristate "LED Support for STMicroelectronics LED1202 I2C chips"
  856. depends on LEDS_CLASS
  857. depends on I2C
  858. depends on OF
  859. select LEDS_TRIGGERS
  860. select LEDS_TRIGGER_PATTERN
  861. help
  862. Say Y to enable support for LEDs connected to LED1202
  863. LED driver chips accessed via the I2C bus.
  864. config LEDS_TPS6105X
  865. tristate "LED support for TI TPS6105X"
  866. depends on LEDS_CLASS
  867. depends on TPS6105X
  868. default y if TPS6105X
  869. help
  870. This driver supports TPS61050/TPS61052 LED chips.
  871. It is a single boost converter primarily for white LEDs and
  872. audio amplifiers.
  873. config LEDS_IP30
  874. tristate "LED support for SGI Octane machines"
  875. depends on LEDS_CLASS
  876. depends on SGI_MFD_IOC3 || COMPILE_TEST
  877. help
  878. This option enables support for the Red and White LEDs of
  879. SGI Octane machines.
  880. To compile this driver as a module, choose M here: the module
  881. will be called leds-ip30.
  882. config LEDS_ACER_A500
  883. tristate "Power button LED support for Acer Iconia Tab A500"
  884. depends on LEDS_CLASS && MFD_ACER_A500_EC
  885. help
  886. This option enables support for the Power Button LED of
  887. Acer Iconia Tab A500.
  888. source "drivers/leds/blink/Kconfig"
  889. comment "Flash and Torch LED drivers"
  890. source "drivers/leds/flash/Kconfig"
  891. comment "RGB LED drivers"
  892. source "drivers/leds/rgb/Kconfig"
  893. comment "LED Triggers"
  894. source "drivers/leds/trigger/Kconfig"
  895. comment "Simatic LED drivers"
  896. source "drivers/leds/simatic/Kconfig"
  897. endif # NEW_LEDS