1# SPDX-License-Identifier: GPL-2.0-only 2 3# 4# Light sensors 5# 6# When adding new entries keep the list in alphabetical order 7 8menu "Light sensors" 9 10config ACPI_ALS 11 tristate "ACPI Ambient Light Sensor" 12 depends on ACPI 13 select IIO_BUFFER 14 select IIO_TRIGGERED_BUFFER 15 select IIO_KFIFO_BUF 16 help 17 Say Y here if you want to build a driver for the ACPI0008 18 Ambient Light Sensor. 19 20 To compile this driver as a module, choose M here: the module will 21 be called acpi-als. 22 23config ADJD_S311 24 tristate "ADJD-S311-CR999 digital color sensor" 25 select IIO_BUFFER 26 select IIO_TRIGGERED_BUFFER 27 depends on I2C 28 help 29 If you say yes here you get support for the Avago ADJD-S311-CR999 30 digital color light sensor. 31 32 This driver can also be built as a module. If so, the module 33 will be called adjd_s311. 34 35config AL3320A 36 tristate "AL3320A ambient light sensor" 37 depends on I2C 38 help 39 Say Y here if you want to build a driver for the Dyna Image AL3320A 40 ambient light sensor. 41 42 To compile this driver as a module, choose M here: the 43 module will be called al3320a. 44 45config APDS9300 46 tristate "APDS9300 ambient light sensor" 47 depends on I2C 48 help 49 Say Y here if you want to build a driver for the Avago APDS9300 50 ambient light sensor. 51 52 To compile this driver as a module, choose M here: the 53 module will be called apds9300. 54 55config APDS9960 56 tristate "Avago APDS9960 gesture/RGB/ALS/proximity sensor" 57 select REGMAP_I2C 58 select IIO_BUFFER 59 select IIO_KFIFO_BUF 60 depends on I2C 61 help 62 Say Y here to build I2C interface support for the Avago 63 APDS9960 gesture/RGB/ALS/proximity sensor. 64 65 To compile this driver as a module, choose M here: the 66 module will be called apds9960 67 68config BH1750 69 tristate "ROHM BH1750 ambient light sensor" 70 depends on I2C 71 help 72 Say Y here to build support for the ROHM BH1710, BH1715, BH1721, 73 BH1750, BH1751 ambient light sensors. 74 75 To compile this driver as a module, choose M here: the module will 76 be called bh1750. 77 78config BH1780 79 tristate "ROHM BH1780 ambient light sensor" 80 depends on I2C 81 help 82 Say Y here to build support for the ROHM BH1780GLI ambient 83 light sensor. 84 85 To compile this driver as a module, choose M here: the module will 86 be called bh1780. 87 88config CM32181 89 depends on I2C 90 tristate "CM32181 driver" 91 help 92 Say Y here if you use cm32181. 93 This option enables ambient light sensor using 94 Capella cm32181 device driver. 95 96 To compile this driver as a module, choose M here: 97 the module will be called cm32181. 98 99config CM3232 100 depends on I2C 101 tristate "CM3232 ambient light sensor" 102 help 103 Say Y here if you use cm3232. 104 This option enables ambient light sensor using 105 Capella Microsystems cm3232 device driver. 106 107 To compile this driver as a module, choose M here: 108 the module will be called cm3232. 109 110config CM3323 111 depends on I2C 112 tristate "Capella CM3323 color light sensor" 113 help 114 Say Y here if you want to build a driver for Capella CM3323 115 color sensor. 116 117 To compile this driver as a module, choose M here: the module will 118 be called cm3323. 119 120config CM3605 121 tristate "Capella CM3605 ambient light and proximity sensor" 122 depends on OF 123 help 124 Say Y here if you want to build a driver for Capella CM3605 125 ambient light and short range proximity sensor. 126 127 To compile this driver as a module, choose M here: the module will 128 be called cm3605. 129 130config CM36651 131 depends on I2C 132 tristate "CM36651 driver" 133 help 134 Say Y here if you use cm36651. 135 This option enables proximity & RGB sensor using 136 Capella cm36651 device driver. 137 138 To compile this driver as a module, choose M here: 139 the module will be called cm36651. 140 141config IIO_CROS_EC_LIGHT_PROX 142 tristate "ChromeOS EC Light and Proximity Sensors" 143 depends on IIO_CROS_EC_SENSORS_CORE 144 help 145 Say Y here if you use the light and proximity sensors 146 presented by the ChromeOS EC Sensor hub. 147 148 To compile this driver as a module, choose M here: 149 the module will be called cros_ec_light_prox. 150 151config GP2AP020A00F 152 tristate "Sharp GP2AP020A00F Proximity/ALS sensor" 153 depends on I2C 154 select REGMAP_I2C 155 select IIO_BUFFER 156 select IIO_TRIGGERED_BUFFER 157 select IRQ_WORK 158 help 159 Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip 160 hooked to an I2C bus. 161 162 To compile this driver as a module, choose M here: the 163 module will be called gp2ap020a00f. 164 165config SENSORS_ISL29018 166 tristate "Intersil 29018 light and proximity sensor" 167 depends on I2C 168 select REGMAP_I2C 169 default n 170 help 171 If you say yes here you get support for ambient light sensing and 172 proximity infrared sensing from Intersil ISL29018. 173 This driver will provide the measurements of ambient light intensity 174 in lux, proximity infrared sensing and normal infrared sensing. 175 Data from sensor is accessible via sysfs. 176 177config SENSORS_ISL29028 178 tristate "Intersil ISL29028 Concurrent Light and Proximity Sensor" 179 depends on I2C 180 select REGMAP_I2C 181 help 182 Provides driver for the Intersil's ISL29028 device. 183 This driver supports the sysfs interface to get the ALS, IR intensity, 184 Proximity value via iio. The ISL29028 provides the concurrent sensing 185 of ambient light and proximity. 186 187config ISL29125 188 tristate "Intersil ISL29125 digital color light sensor" 189 depends on I2C 190 select IIO_BUFFER 191 select IIO_TRIGGERED_BUFFER 192 help 193 Say Y here if you want to build a driver for the Intersil ISL29125 194 RGB light sensor for I2C. 195 196 To compile this driver as a module, choose M here: the module will be 197 called isl29125. 198 199config HID_SENSOR_ALS 200 depends on HID_SENSOR_HUB 201 select IIO_BUFFER 202 select IIO_TRIGGERED_BUFFER 203 select HID_SENSOR_IIO_COMMON 204 select HID_SENSOR_IIO_TRIGGER 205 tristate "HID ALS" 206 help 207 Say yes here to build support for the HID SENSOR 208 Ambient light sensor. 209 210 To compile this driver as a module, choose M here: the 211 module will be called hid-sensor-als. 212 213config HID_SENSOR_PROX 214 depends on HID_SENSOR_HUB 215 select IIO_BUFFER 216 select IIO_TRIGGERED_BUFFER 217 select HID_SENSOR_IIO_COMMON 218 select HID_SENSOR_IIO_TRIGGER 219 tristate "HID PROX" 220 help 221 Say yes here to build support for the HID SENSOR 222 Proximity sensor. 223 224 To compile this driver as a module, choose M here: the 225 module will be called hid-sensor-prox. 226 227config JSA1212 228 tristate "JSA1212 ALS and proximity sensor driver" 229 depends on I2C 230 select REGMAP_I2C 231 help 232 Say Y here if you want to build a IIO driver for JSA1212 233 proximity & ALS sensor device. 234 235 To compile this driver as a module, choose M here: 236 the module will be called jsa1212. 237 238config RPR0521 239 tristate "ROHM RPR0521 ALS and proximity sensor driver" 240 depends on I2C 241 select REGMAP_I2C 242 select IIO_BUFFER 243 select IIO_TRIGGERED_BUFFER 244 help 245 Say Y here if you want to build support for ROHM's RPR0521 246 ambient light and proximity sensor device. 247 248 To compile this driver as a module, choose M here: 249 the module will be called rpr0521. 250 251config SENSORS_LM3533 252 tristate "LM3533 ambient light sensor" 253 depends on MFD_LM3533 254 help 255 If you say yes here you get support for the ambient light sensor 256 interface on National Semiconductor / TI LM3533 Lighting Power 257 chips. 258 259 The sensor interface can be used to control the LEDs and backlights 260 of the chip through defining five light zones and three sets of 261 corresponding output-current values. 262 263 The driver provides raw and mean adc readings along with the current 264 light zone through sysfs. A threshold event can be generated on zone 265 changes. The ALS-control output values can be set per zone for the 266 three current output channels. 267 268config LTR501 269 tristate "LTR-501ALS-01 light sensor" 270 depends on I2C 271 select REGMAP_I2C 272 select IIO_BUFFER 273 select IIO_TRIGGERED_BUFFER 274 help 275 If you say yes here you get support for the Lite-On LTR-501ALS-01 276 ambient light and proximity sensor. This driver also supports LTR-559 277 ALS/PS or LTR-301 ALS sensors. 278 279 This driver can also be built as a module. If so, the module 280 will be called ltr501. 281 282config LV0104CS 283 tristate "LV0104CS Ambient Light Sensor" 284 depends on I2C 285 help 286 Say Y here if you want to build support for the On Semiconductor 287 LV0104CS ambient light sensor. 288 289 To compile this driver as a module, choose M here: 290 the module will be called lv0104cs. 291 292config MAX44000 293 tristate "MAX44000 Ambient and Infrared Proximity Sensor" 294 depends on I2C 295 select REGMAP_I2C 296 select IIO_BUFFER 297 select IIO_TRIGGERED_BUFFER 298 help 299 Say Y here if you want to build support for Maxim Integrated's 300 MAX44000 ambient and infrared proximity sensor device. 301 302 To compile this driver as a module, choose M here: 303 the module will be called max44000. 304 305config MAX44009 306 tristate "MAX44009 Ambient Light Sensor" 307 depends on I2C 308 select REGMAP_I2C 309 help 310 Say Y here if you want to build support for Maxim Integrated's 311 MAX44009 ambient light sensor device. 312 313 To compile this driver as a module, choose M here: 314 the module will be called max44009. 315 316config NOA1305 317 tristate "ON Semiconductor NOA1305 ambient light sensor" 318 depends on I2C 319 select REGMAP_I2C 320 help 321 Say Y here if you want to build support for the ON Semiconductor 322 NOA1305 ambient light sensor. 323 324 To compile this driver as a module, choose M here: 325 The module will be called noa1305. 326 327config OPT3001 328 tristate "Texas Instruments OPT3001 Light Sensor" 329 depends on I2C 330 help 331 If you say Y or M here, you get support for Texas Instruments 332 OPT3001 Ambient Light Sensor. 333 334 If built as a dynamically linked module, it will be called 335 opt3001. 336 337config PA12203001 338 tristate "TXC PA12203001 light and proximity sensor" 339 depends on I2C 340 select REGMAP_I2C 341 help 342 If you say yes here you get support for the TXC PA12203001 343 ambient light and proximity sensor. 344 345 This driver can also be built as a module. If so, the module 346 will be called pa12203001. 347 348config SI1133 349 tristate "SI1133 UV Index Sensor and Ambient Light Sensor" 350 depends on I2C 351 select REGMAP_I2C 352 help 353 Say Y here if you want to build a driver for the Silicon Labs SI1133 354 UV Index Sensor and Ambient Light Sensor chip. 355 356 To compile this driver as a module, choose M here: the module will be 357 called si1133. 358 359config SI1145 360 tristate "SI1132 and SI1141/2/3/5/6/7 combined ALS, UV index and proximity sensor" 361 depends on I2C 362 select IIO_BUFFER 363 select IIO_TRIGGERED_BUFFER 364 help 365 Say Y here if you want to build a driver for the Silicon Labs SI1132 or 366 SI1141/2/3/5/6/7 combined ambient light, UV index and proximity sensor 367 chips. 368 369 To compile this driver as a module, choose M here: the module will be 370 called si1145. 371 372config STK3310 373 tristate "STK3310 ALS and proximity sensor" 374 depends on I2C 375 select REGMAP_I2C 376 help 377 Say yes here to get support for the Sensortek STK3310 ambient light 378 and proximity sensor. The STK3311 model is also supported by this 379 driver. 380 381 Choosing M will build the driver as a module. If so, the module 382 will be called stk3310. 383 384config ST_UVIS25 385 tristate "STMicroelectronics UVIS25 sensor driver" 386 depends on (I2C || SPI) 387 select IIO_BUFFER 388 select IIO_TRIGGERED_BUFFER 389 select ST_UVIS25_I2C if (I2C) 390 select ST_UVIS25_SPI if (SPI_MASTER) 391 help 392 Say yes here to build support for STMicroelectronics UVIS25 393 uv sensor 394 395 To compile this driver as a module, choose M here: the module 396 will be called st_uvis25. 397 398config ST_UVIS25_I2C 399 tristate 400 depends on ST_UVIS25 401 select REGMAP_I2C 402 403config ST_UVIS25_SPI 404 tristate 405 depends on ST_UVIS25 406 select REGMAP_SPI 407 408config TCS3414 409 tristate "TAOS TCS3414 digital color sensor" 410 depends on I2C 411 select IIO_BUFFER 412 select IIO_TRIGGERED_BUFFER 413 help 414 If you say yes here you get support for the TAOS TCS3414 415 family of digital color sensors. 416 417 This driver can also be built as a module. If so, the module 418 will be called tcs3414. 419 420config TCS3472 421 tristate "TAOS TCS3472 color light-to-digital converter" 422 depends on I2C 423 select IIO_BUFFER 424 select IIO_TRIGGERED_BUFFER 425 help 426 If you say yes here you get support for the TAOS TCS3472 427 family of color light-to-digital converters with IR filter. 428 429 This driver can also be built as a module. If so, the module 430 will be called tcs3472. 431 432config SENSORS_TSL2563 433 tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors" 434 depends on I2C 435 help 436 If you say yes here you get support for the Taos TSL2560, 437 TSL2561, TSL2562 and TSL2563 ambient light sensors. 438 439 This driver can also be built as a module. If so, the module 440 will be called tsl2563. 441 442config TSL2583 443 tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters" 444 depends on I2C 445 help 446 Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices. 447 Access ALS data via iio, sysfs. 448 449config TSL2772 450 tristate "TAOS TSL/TMD2x71 and TSL/TMD2x72 Family of light and proximity sensors" 451 depends on I2C 452 help 453 Support for: tsl2571, tsl2671, tmd2671, tsl2771, tmd2771, tsl2572, tsl2672, 454 tmd2672, tsl2772, tmd2772 devices. 455 Provides iio_events and direct access via sysfs. 456 457config TSL4531 458 tristate "TAOS TSL4531 ambient light sensors" 459 depends on I2C 460 help 461 Say Y here if you want to build a driver for the TAOS TSL4531 family 462 of ambient light sensors with direct lux output. 463 464 To compile this driver as a module, choose M here: the 465 module will be called tsl4531. 466 467config US5182D 468 tristate "UPISEMI light and proximity sensor" 469 depends on I2C 470 help 471 If you say yes here you get support for the UPISEMI US5182D 472 ambient light and proximity sensor. 473 474 This driver can also be built as a module. If so, the module 475 will be called us5182d. 476 477config VCNL4000 478 tristate "VCNL4000/4010/4020/4200 combined ALS and proximity sensor" 479 depends on I2C 480 help 481 Say Y here if you want to build a driver for the Vishay VCNL4000, 482 VCNL4010, VCNL4020, VCNL4200 combined ambient light and proximity 483 sensor. 484 485 To compile this driver as a module, choose M here: the 486 module will be called vcnl4000. 487 488config VCNL4035 489 tristate "VCNL4035 combined ALS and proximity sensor" 490 select IIO_BUFFER 491 select IIO_TRIGGERED_BUFFER 492 select REGMAP_I2C 493 depends on I2C 494 help 495 Say Y here if you want to build a driver for the Vishay VCNL4035, 496 combined ambient light (ALS) and proximity sensor. Currently only ALS 497 function is available. 498 499 To compile this driver as a module, choose M here: the 500 module will be called vcnl4035. 501 502config VEML6070 503 tristate "VEML6070 UV A light sensor" 504 depends on I2C 505 help 506 Say Y here if you want to build a driver for the Vishay VEML6070 UV A 507 light sensor. 508 509 To compile this driver as a module, choose M here: the 510 module will be called veml6070. 511 512config VL6180 513 tristate "VL6180 ALS, range and proximity sensor" 514 depends on I2C 515 help 516 Say Y here if you want to build a driver for the STMicroelectronics 517 VL6180 combined ambient light, range and proximity sensor. 518 519 To compile this driver as a module, choose M here: the 520 module will be called vl6180. 521 522config ZOPT2201 523 tristate "ZOPT2201 ALS and UV B sensor" 524 depends on I2C 525 help 526 Say Y here if you want to build a driver for the IDT 527 ZOPT2201 ambient light and UV B sensor. 528 529 To compile this driver as a module, choose M here: the 530 module will be called zopt2201. 531 532endmenu 533