1 # SPDX-License-Identifier: GPL-2.0-only
6 # When adding new entries keep the list in alphabetical order
11 tristate "ACPI Ambient Light Sensor"
14 select IIO_TRIGGERED_BUFFER
17 Say Y here if you want to build a driver for the ACPI0008
20 To compile this driver as a module, choose M here: the module will
24 tristate "ADJD-S311-CR999 digital color sensor"
26 select IIO_TRIGGERED_BUFFER
29 If you say yes here you get support for the Avago ADJD-S311-CR999
30 digital color light sensor.
32 This driver can also be built as a module. If so, the module
33 will be called adjd_s311.
36 tristate "ADUX1020 photometric sensor"
40 Say Y here if you want to build a driver for the Analog Devices
41 ADUX1020 photometric sensor.
43 To compile this driver as a module, choose M here: the
44 module will be called adux1020.
47 tristate "AL3010 ambient light sensor"
50 Say Y here if you want to build a driver for the Dyna Image AL3010
53 To compile this driver as a module, choose M here: the
54 module will be called al3010.
57 tristate "AL3320A ambient light sensor"
60 Say Y here if you want to build a driver for the Dyna Image AL3320A
63 To compile this driver as a module, choose M here: the
64 module will be called al3320a.
67 tristate "APDS9300 ambient light sensor"
70 Say Y here if you want to build a driver for the Avago APDS9300
73 To compile this driver as a module, choose M here: the
74 module will be called apds9300.
77 tristate "Avago APDS9960 gesture/RGB/ALS/proximity sensor"
83 Say Y here to build I2C interface support for the Avago
84 APDS9960 gesture/RGB/ALS/proximity sensor.
86 To compile this driver as a module, choose M here: the
87 module will be called apds9960
90 tristate "AMS AS73211 XYZ color sensor"
93 select IIO_TRIGGERED_BUFFER
95 If you say yes here you get support for the AMS AS73211
96 JENCOLOR(R) Digital XYZ Sensor.
98 For triggered measurements, you will need an additional trigger driver
99 like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER.
101 This driver can also be built as a module. If so, the module
102 will be called as73211.
105 tristate "ROHM BH1750 ambient light sensor"
108 Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
109 BH1750, BH1751 ambient light sensors.
111 To compile this driver as a module, choose M here: the module will
115 tristate "ROHM BH1780 ambient light sensor"
118 Say Y here to build support for the ROHM BH1780GLI ambient
121 To compile this driver as a module, choose M here: the module will
126 tristate "CM32181 driver"
128 Say Y here if you use cm32181.
129 This option enables ambient light sensor using
130 Capella cm32181 device driver.
132 To compile this driver as a module, choose M here:
133 the module will be called cm32181.
137 tristate "CM3232 ambient light sensor"
139 Say Y here if you use cm3232.
140 This option enables ambient light sensor using
141 Capella Microsystems cm3232 device driver.
143 To compile this driver as a module, choose M here:
144 the module will be called cm3232.
148 tristate "Capella CM3323 color light sensor"
150 Say Y here if you want to build a driver for Capella CM3323
153 To compile this driver as a module, choose M here: the module will
157 tristate "Capella CM3605 ambient light and proximity sensor"
159 Say Y here if you want to build a driver for Capella CM3605
160 ambient light and short range proximity sensor.
162 To compile this driver as a module, choose M here: the module will
167 tristate "CM36651 driver"
169 Say Y here if you use cm36651.
170 This option enables proximity & RGB sensor using
171 Capella cm36651 device driver.
173 To compile this driver as a module, choose M here:
174 the module will be called cm36651.
176 config IIO_CROS_EC_LIGHT_PROX
177 tristate "ChromeOS EC Light and Proximity Sensors"
178 depends on IIO_CROS_EC_SENSORS_CORE
180 Say Y here if you use the light and proximity sensors
181 presented by the ChromeOS EC Sensor hub.
183 To compile this driver as a module, choose M here:
184 the module will be called cros_ec_light_prox.
187 tristate "Sharp GP2AP002 Proximity/ALS sensor"
191 Say Y here if you have a Sharp GP2AP002 proximity/ALS combo-chip
192 hooked to an I2C bus.
194 To compile this driver as a module, choose M here: the
195 module will be called gp2ap002.
198 tristate "Sharp GP2AP020A00F Proximity/ALS sensor"
202 select IIO_TRIGGERED_BUFFER
205 Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip
206 hooked to an I2C bus.
208 To compile this driver as a module, choose M here: the
209 module will be called gp2ap020a00f.
212 tristate "Azoteq IQS621/622 ambient light sensors"
213 depends on MFD_IQS62X || COMPILE_TEST
215 Say Y here if you want to build support for the Azoteq IQS621
216 and IQS622 ambient light sensors.
218 To compile this driver as a module, choose M here: the module
219 will be called iqs621-als.
221 config SENSORS_ISL29018
222 tristate "Intersil 29018 light and proximity sensor"
227 If you say yes here you get support for ambient light sensing and
228 proximity infrared sensing from Intersil ISL29018.
229 This driver will provide the measurements of ambient light intensity
230 in lux, proximity infrared sensing and normal infrared sensing.
231 Data from sensor is accessible via sysfs.
233 config SENSORS_ISL29028
234 tristate "Intersil ISL29028 Concurrent Light and Proximity Sensor"
238 Provides driver for the Intersil's ISL29028 device.
239 This driver supports the sysfs interface to get the ALS, IR intensity,
240 Proximity value via iio. The ISL29028 provides the concurrent sensing
241 of ambient light and proximity.
244 tristate "Intersil ISL29125 digital color light sensor"
247 select IIO_TRIGGERED_BUFFER
249 Say Y here if you want to build a driver for the Intersil ISL29125
250 RGB light sensor for I2C.
252 To compile this driver as a module, choose M here: the module will be
255 config HID_SENSOR_ALS
256 depends on HID_SENSOR_HUB
258 select HID_SENSOR_IIO_COMMON
259 select HID_SENSOR_IIO_TRIGGER
262 Say yes here to build support for the HID SENSOR
263 Ambient light sensor.
265 To compile this driver as a module, choose M here: the
266 module will be called hid-sensor-als.
268 config HID_SENSOR_PROX
269 depends on HID_SENSOR_HUB
271 select HID_SENSOR_IIO_COMMON
272 select HID_SENSOR_IIO_TRIGGER
275 Say yes here to build support for the HID SENSOR
278 To compile this driver as a module, choose M here: the
279 module will be called hid-sensor-prox.
282 tristate "JSA1212 ALS and proximity sensor driver"
286 Say Y here if you want to build a IIO driver for JSA1212
287 proximity & ALS sensor device.
289 To compile this driver as a module, choose M here:
290 the module will be called jsa1212.
293 tristate "ROHM BU27008 color (RGB+C/IR) sensor"
296 select IIO_GTS_HELPER
298 Enable support for the ROHM BU27008 color sensor.
299 The ROHM BU27008 is a sensor with 5 photodiodes (red, green,
300 blue, clear and IR) with four configurable channels. Red and
301 green being always available and two out of the rest three
302 (blue, clear, IR) can be selected to be simultaneously measured.
303 Typical application is adjusting LCD backlight of TVs,
304 mobile phones and tablet PCs.
307 tristate "ROHM BU27034 ambient light sensor"
310 select IIO_GTS_HELPER
314 Enable support for the ROHM BU27034 ambient light sensor. ROHM BU27034
315 is an ambient light sesnor with 3 channels and 3 photo diodes capable
316 of detecting a very wide range of illuminance.
317 Typical application is adjusting LCD and backlight power of TVs and
321 tristate "ROHM RPR0521 ALS and proximity sensor driver"
325 select IIO_TRIGGERED_BUFFER
327 Say Y here if you want to build support for ROHM's RPR0521
328 ambient light and proximity sensor device.
330 To compile this driver as a module, choose M here:
331 the module will be called rpr0521.
333 config SENSORS_LM3533
334 tristate "LM3533 ambient light sensor"
335 depends on MFD_LM3533
337 If you say yes here you get support for the ambient light sensor
338 interface on National Semiconductor / TI LM3533 Lighting Power
341 The sensor interface can be used to control the LEDs and backlights
342 of the chip through defining five light zones and three sets of
343 corresponding output-current values.
345 The driver provides raw and mean adc readings along with the current
346 light zone through sysfs. A threshold event can be generated on zone
347 changes. The ALS-control output values can be set per zone for the
348 three current output channels.
351 tristate "LTR-501ALS-01 light sensor"
355 select IIO_TRIGGERED_BUFFER
357 If you say yes here you get support for the Lite-On LTR-501ALS-01
358 ambient light and proximity sensor. This driver also supports LTR-559
359 ALS/PS or LTR-301 ALS sensors.
361 This driver can also be built as a module. If so, the module
362 will be called ltr501.
365 tristate "Liteon LTRF216A Light Sensor"
369 If you say Y or M here, you get support for Liteon LTRF216A
370 Ambient Light Sensor.
372 If built as a dynamically linked module, it will be called
376 tristate "LV0104CS Ambient Light Sensor"
379 Say Y here if you want to build support for the On Semiconductor
380 LV0104CS ambient light sensor.
382 To compile this driver as a module, choose M here:
383 the module will be called lv0104cs.
386 tristate "MAX44000 Ambient and Infrared Proximity Sensor"
390 select IIO_TRIGGERED_BUFFER
392 Say Y here if you want to build support for Maxim Integrated's
393 MAX44000 ambient and infrared proximity sensor device.
395 To compile this driver as a module, choose M here:
396 the module will be called max44000.
399 tristate "MAX44009 Ambient Light Sensor"
403 Say Y here if you want to build support for Maxim Integrated's
404 MAX44009 ambient light sensor device.
406 To compile this driver as a module, choose M here:
407 the module will be called max44009.
410 tristate "ON Semiconductor NOA1305 ambient light sensor"
414 Say Y here if you want to build support for the ON Semiconductor
415 NOA1305 ambient light sensor.
417 To compile this driver as a module, choose M here:
418 The module will be called noa1305.
421 tristate "Texas Instruments OPT3001 Light Sensor"
424 If you say Y or M here, you get support for Texas Instruments
425 OPT3001 Ambient Light Sensor.
427 If built as a dynamically linked module, it will be called
431 tristate "Texas Instruments OPT4001 Light Sensor"
435 If you say Y or M here, you get support for Texas Instruments
436 OPT4001 Ambient Light Sensor.
438 If built as a dynamically linked module, it will be called
442 tristate "TXC PA12203001 light and proximity sensor"
446 If you say yes here you get support for the TXC PA12203001
447 ambient light and proximity sensor.
449 This driver can also be built as a module. If so, the module
450 will be called pa12203001.
453 tristate "SI1133 UV Index Sensor and Ambient Light Sensor"
457 Say Y here if you want to build a driver for the Silicon Labs SI1133
458 UV Index Sensor and Ambient Light Sensor chip.
460 To compile this driver as a module, choose M here: the module will be
464 tristate "SI1132 and SI1141/2/3/5/6/7 combined ALS, UV index and proximity sensor"
467 select IIO_TRIGGERED_BUFFER
469 Say Y here if you want to build a driver for the Silicon Labs SI1132 or
470 SI1141/2/3/5/6/7 combined ambient light, UV index and proximity sensor
473 To compile this driver as a module, choose M here: the module will be
477 tristate "STK3310 ALS and proximity sensor"
481 Say yes here to get support for the Sensortek STK3310 ambient light
482 and proximity sensor. The STK3311 model is also supported by this
485 Choosing M will build the driver as a module. If so, the module
486 will be called stk3310.
489 tristate "STMicroelectronics UVIS25 sensor driver"
490 depends on (I2C || SPI)
492 select IIO_TRIGGERED_BUFFER
493 select ST_UVIS25_I2C if (I2C)
494 select ST_UVIS25_SPI if (SPI_MASTER)
496 Say yes here to build support for STMicroelectronics UVIS25
499 To compile this driver as a module, choose M here: the module
500 will be called st_uvis25.
513 tristate "TAOS TCS3414 digital color sensor"
516 select IIO_TRIGGERED_BUFFER
518 If you say yes here you get support for the TAOS TCS3414
519 family of digital color sensors.
521 This driver can also be built as a module. If so, the module
522 will be called tcs3414.
525 tristate "TAOS TCS3472 color light-to-digital converter"
528 select IIO_TRIGGERED_BUFFER
530 If you say yes here you get support for the TAOS TCS3472
531 family of color light-to-digital converters with IR filter.
533 This driver can also be built as a module. If so, the module
534 will be called tcs3472.
536 config SENSORS_TSL2563
537 tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors"
540 If you say yes here you get support for the Taos TSL2560,
541 TSL2561, TSL2562 and TSL2563 ambient light sensors.
543 This driver can also be built as a module. If so, the module
544 will be called tsl2563.
547 tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters"
550 Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices.
551 Access ALS data via iio, sysfs.
554 tristate "TAOS TSL2591 ambient light sensor"
557 Select Y here for support of the AMS/TAOS TSL2591 ambient light sensor,
558 featuring channels for combined visible + IR intensity and lux illuminance.
559 Access data via iio and sysfs. Supports iio_events.
561 To compile this driver as a module, select M: the
562 module will be called tsl2591.
565 tristate "TAOS TSL/TMD2x71 and TSL/TMD2x72 Family of light and proximity sensors"
568 Support for: tsl2571, tsl2671, tmd2671, tsl2771, tmd2771, tsl2572, tsl2672,
569 tmd2672, tsl2772, tmd2772 devices.
570 Provides iio_events and direct access via sysfs.
573 tristate "TAOS TSL4531 ambient light sensors"
576 Say Y here if you want to build a driver for the TAOS TSL4531 family
577 of ambient light sensors with direct lux output.
579 To compile this driver as a module, choose M here: the
580 module will be called tsl4531.
583 tristate "UPISEMI light and proximity sensor"
586 If you say yes here you get support for the UPISEMI US5182D
587 ambient light and proximity sensor.
589 This driver can also be built as a module. If so, the module
590 will be called us5182d.
593 tristate "VCNL4000/4010/4020/4200 combined ALS and proximity sensor"
595 select IIO_TRIGGERED_BUFFER
598 Say Y here if you want to build a driver for the Vishay VCNL4000,
599 VCNL4010, VCNL4020, VCNL4200 combined ambient light and proximity
602 To compile this driver as a module, choose M here: the
603 module will be called vcnl4000.
606 tristate "VCNL4035 combined ALS and proximity sensor"
608 select IIO_TRIGGERED_BUFFER
612 Say Y here if you want to build a driver for the Vishay VCNL4035,
613 combined ambient light (ALS) and proximity sensor. Currently only ALS
614 function is available.
616 To compile this driver as a module, choose M here: the
617 module will be called vcnl4035.
620 tristate "VEML6030 ambient light sensor"
624 Say Y here if you want to build a driver for the Vishay VEML6030
625 ambient light sensor (ALS).
627 To compile this driver as a module, choose M here: the
628 module will be called veml6030.
631 tristate "VEML6070 UV A light sensor"
634 Say Y here if you want to build a driver for the Vishay VEML6070 UV A
637 To compile this driver as a module, choose M here: the
638 module will be called veml6070.
641 tristate "VL6180 ALS, range and proximity sensor"
644 Say Y here if you want to build a driver for the STMicroelectronics
645 VL6180 combined ambient light, range and proximity sensor.
647 To compile this driver as a module, choose M here: the
648 module will be called vl6180.
651 tristate "ZOPT2201 ALS and UV B sensor"
654 Say Y here if you want to build a driver for the IDT
655 ZOPT2201 ambient light and UV B sensor.
657 To compile this driver as a module, choose M here: the
658 module will be called zopt2201.