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