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