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