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