xref: /linux/drivers/iio/light/Kconfig (revision 1260ed77798502de9c98020040d2995008de10cc)
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 AL3000A
47	tristate "AL3000a ambient light sensor"
48	depends on I2C
49	help
50	  Say Y here if you want to build a driver for the Dyna Image AL3000a
51	  ambient light sensor.
52
53	  To compile this driver as a module, choose M here: the
54	  module will be called al3000a.
55
56config AL3010
57	tristate "AL3010 ambient light sensor"
58	depends on I2C
59	help
60	  Say Y here if you want to build a driver for the Dyna Image AL3010
61	  ambient light sensor.
62
63	  To compile this driver as a module, choose M here: the
64	  module will be called al3010.
65
66config AL3320A
67	tristate "AL3320A ambient light sensor"
68	depends on I2C
69	help
70	  Say Y here if you want to build a driver for the Dyna Image AL3320A
71	  ambient light sensor.
72
73	  To compile this driver as a module, choose M here: the
74	  module will be called al3320a.
75
76config APDS9160
77	tristate "APDS9160 combined als and proximity sensor"
78	depends on I2C
79	select REGMAP_I2C
80	help
81	   Say Y here if you want to build support for a Broadcom APDS9160
82	   combined ambient light and proximity sensor.
83
84	   To compile this driver as a module, choose M here: the
85	   module will be called apds9160.
86
87config APDS9300
88	tristate "APDS9300 ambient light sensor"
89	depends on I2C
90	help
91	  Say Y here if you want to build a driver for the Avago APDS9300
92	  ambient light sensor.
93
94	  To compile this driver as a module, choose M here: the
95	  module will be called apds9300.
96
97config APDS9306
98	tristate "Avago APDS9306 Ambient Light Sensor"
99	depends on I2C
100	select REGMAP_I2C
101	select IIO_GTS_HELPER
102	help
103	  If you say Y or M here, you get support for Avago APDS9306
104	  Ambient Light Sensor.
105
106	  If built as a dynamically linked module, it will be called
107	  apds9306.
108
109config APDS9960
110	tristate "Avago APDS9960 gesture/RGB/ALS/proximity sensor"
111	select REGMAP_I2C
112	select IIO_BUFFER
113	select IIO_KFIFO_BUF
114	depends on I2C
115	help
116	  Say Y here to build I2C interface support for the Avago
117	  APDS9960 gesture/RGB/ALS/proximity sensor.
118
119	  To compile this driver as a module, choose M here: the
120	  module will be called apds9960
121
122config AS73211
123	tristate "AMS AS73211 XYZ color sensor and AMS AS7331 UV sensor"
124	depends on I2C
125	select IIO_BUFFER
126	select IIO_TRIGGERED_BUFFER
127	help
128	 If you say yes here you get support for the AMS AS73211
129	 JENCOLOR(R) Digital XYZ and the AMS AS7331 UVA, UVB and UVC
130	 ultraviolet sensors.
131
132	 For triggered measurements, you will need an additional trigger driver
133	 like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER.
134
135	 This driver can also be built as a module.  If so, the module
136	 will be called as73211.
137
138config BH1745
139	tristate "ROHM BH1745 colour sensor"
140	depends on I2C
141	select REGMAP_I2C
142	select IIO_BUFFER
143	select IIO_TRIGGERED_BUFFER
144	select IIO_GTS_HELPER
145	help
146	  Say Y here to build support for the ROHM bh1745 colour sensor.
147
148	  To compile this driver as a module, choose M here: the module will
149	  be called bh1745.
150
151config BH1750
152	tristate "ROHM BH1750 ambient light sensor"
153	depends on I2C
154	help
155	  Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
156	  BH1750, BH1751 ambient light sensors.
157
158	  To compile this driver as a module, choose M here: the module will
159	  be called bh1750.
160
161config BH1780
162	tristate "ROHM BH1780 ambient light sensor"
163	depends on I2C
164	help
165	  Say Y here to build support for the ROHM BH1780GLI ambient
166	  light sensor.
167
168	  To compile this driver as a module, choose M here: the module will
169	  be called bh1780.
170
171config CM32181
172	depends on I2C
173	tristate "CM32181 driver"
174	help
175	  Say Y here if you use cm32181.
176	  This option enables ambient light sensor using
177	  Capella cm32181 device driver.
178
179	  To compile this driver as a module, choose M here:
180	  the module will be called cm32181.
181
182config CM3232
183	depends on I2C
184	tristate "CM3232 ambient light sensor"
185	help
186	  Say Y here if you use cm3232.
187	  This option enables ambient light sensor using
188	  Capella Microsystems cm3232 device driver.
189
190	  To compile this driver as a module, choose M here:
191	  the module will be called cm3232.
192
193config CM3323
194	depends on I2C
195	tristate "Capella CM3323 color light sensor"
196	help
197	  Say Y here if you want to build a driver for Capella CM3323
198	  color sensor.
199
200	  To compile this driver as a module, choose M here: the module will
201	  be called cm3323.
202
203config CM3605
204	tristate "Capella CM3605 ambient light and proximity sensor"
205	help
206	  Say Y here if you want to build a driver for Capella CM3605
207	  ambient light and short range proximity sensor.
208
209	  To compile this driver as a module, choose M here: the module will
210	  be called cm3605.
211
212config CM36651
213	depends on I2C
214	tristate "CM36651 driver"
215	help
216	  Say Y here if you use cm36651.
217	  This option enables proximity & RGB sensor using
218	  Capella cm36651 device driver.
219
220	  To compile this driver as a module, choose M here:
221	  the module will be called cm36651.
222
223config IIO_CROS_EC_LIGHT_PROX
224	tristate "ChromeOS EC Light and Proximity Sensors"
225	depends on IIO_CROS_EC_SENSORS_CORE
226	help
227	  Say Y here if you use the light and proximity sensors
228	  presented by the ChromeOS EC Sensor hub.
229
230	  To compile this driver as a module, choose M here:
231	  the module will be called cros_ec_light_prox.
232
233config GP2AP002
234	tristate "Sharp GP2AP002 Proximity/ALS sensor"
235	depends on I2C
236	select REGMAP
237	help
238	  Say Y here if you have a Sharp GP2AP002 proximity/ALS combo-chip
239	  hooked to an I2C bus.
240
241	  To compile this driver as a module, choose M here: the
242	  module will be called gp2ap002.
243
244config GP2AP020A00F
245	tristate "Sharp GP2AP020A00F Proximity/ALS sensor"
246	depends on I2C
247	select REGMAP_I2C
248	select IIO_BUFFER
249	select IIO_TRIGGERED_BUFFER
250	select IRQ_WORK
251	help
252	  Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip
253	  hooked to an I2C bus.
254
255	  To compile this driver as a module, choose M here: the
256	  module will be called gp2ap020a00f.
257
258config IQS621_ALS
259	tristate "Azoteq IQS621/622 ambient light sensors"
260	depends on MFD_IQS62X || COMPILE_TEST
261	help
262	  Say Y here if you want to build support for the Azoteq IQS621
263	  and IQS622 ambient light sensors.
264
265	  To compile this driver as a module, choose M here: the module
266	  will be called iqs621-als.
267
268config SENSORS_ISL29018
269	tristate "Intersil 29018 light and proximity sensor"
270	depends on I2C
271	select REGMAP_I2C
272	help
273	  If you say yes here you get support for ambient light sensing and
274	  proximity infrared sensing from Intersil ISL29018.
275	  This driver will provide the measurements of ambient light intensity
276	  in lux, proximity infrared sensing and normal infrared sensing.
277	  Data from sensor is accessible via sysfs.
278
279config SENSORS_ISL29028
280	tristate "Intersil ISL29028 Concurrent Light and Proximity Sensor"
281	depends on I2C
282	select REGMAP_I2C
283	help
284	  Provides driver for the Intersil's ISL29028 device.
285	  This driver supports the sysfs interface to get the ALS, IR intensity,
286	  Proximity value via iio. The ISL29028 provides the concurrent sensing
287	  of ambient light and proximity.
288
289config ISL29125
290	tristate "Intersil ISL29125 digital color light sensor"
291	depends on I2C
292	select IIO_BUFFER
293	select IIO_TRIGGERED_BUFFER
294	help
295	  Say Y here if you want to build a driver for the Intersil ISL29125
296	  RGB light sensor for I2C.
297
298	  To compile this driver as a module, choose M here: the module will be
299	  called isl29125.
300
301config ISL76682
302	tristate "Intersil ISL76682 Light Sensor"
303	depends on I2C
304	select REGMAP_I2C
305	help
306	  Say Y here if you want to build a driver for the Intersil ISL76682
307	  Ambient Light Sensor and IR Intensity sensor. This driver provides
308	  the readouts via standard IIO sysfs and device interface. Both ALS
309	  illuminance and IR illuminance are provided raw with separate scale
310	  setting which can be configured via sysfs, the default scale is 1000
311	  lux, other options are 4000/16000/64000 lux.
312
313	  To compile this driver as a module, choose M here: the module will be
314	  called isl76682.
315
316config HID_SENSOR_ALS
317	depends on HID_SENSOR_HUB
318	select IIO_BUFFER
319	select HID_SENSOR_IIO_COMMON
320	select HID_SENSOR_IIO_TRIGGER
321	tristate "HID ALS"
322	help
323	  Say yes here to build support for the HID SENSOR
324	  Ambient light sensor.
325
326	  To compile this driver as a module, choose M here: the
327	  module will be called hid-sensor-als.
328
329config HID_SENSOR_PROX
330	depends on HID_SENSOR_HUB
331	select IIO_BUFFER
332	select HID_SENSOR_IIO_COMMON
333	select HID_SENSOR_IIO_TRIGGER
334	tristate "HID PROX"
335	help
336	  Say yes here to build support for the HID SENSOR
337	  Proximity sensor.
338
339	  To compile this driver as a module, choose M here: the
340	  module will be called hid-sensor-prox.
341
342config JSA1212
343	tristate "JSA1212 ALS and proximity sensor driver"
344	depends on I2C
345	select REGMAP_I2C
346	help
347	  Say Y here if you want to build a IIO driver for JSA1212
348	  proximity & ALS sensor device.
349
350	  To compile this driver as a module, choose M here:
351	  the module will be called jsa1212.
352
353config ROHM_BU27034
354	tristate "ROHM BU27034 ambient light sensor"
355	depends on I2C
356	select REGMAP_I2C
357	select IIO_GTS_HELPER
358	select IIO_BUFFER
359	select IIO_KFIFO_BUF
360	help
361	  Enable support for the ROHM BU27034 ambient light sensor. ROHM BU27034
362	  is an ambient light sesnor with 3 channels and 3 photo diodes capable
363	  of detecting a very wide range of illuminance.
364	  Typical application is adjusting LCD and backlight power of TVs and
365	  mobile phones.
366
367config RPR0521
368	tristate "ROHM RPR0521 ALS and proximity sensor driver"
369	depends on I2C
370	select REGMAP_I2C
371	select IIO_BUFFER
372	select IIO_TRIGGERED_BUFFER
373	help
374	  Say Y here if you want to build support for ROHM's RPR0521
375	  ambient light and proximity sensor device.
376
377	  To compile this driver as a module, choose M here:
378	  the module will be called rpr0521.
379
380config SENSORS_LM3533
381	tristate "LM3533 ambient light sensor"
382	depends on MFD_LM3533
383	help
384	  If you say yes here you get support for the ambient light sensor
385	  interface on National Semiconductor / TI LM3533 Lighting Power
386	  chips.
387
388	  The sensor interface can be used to control the LEDs and backlights
389	  of the chip through defining five light zones and three sets of
390	  corresponding output-current values.
391
392	  The driver provides raw and mean adc readings along with the current
393	  light zone through sysfs. A threshold event can be generated on zone
394	  changes. The ALS-control output values can be set per zone for the
395	  three current output channels.
396
397config LTR390
398	tristate "LTR-390UV-01 ambient light and UV sensor"
399	depends on I2C
400	select REGMAP_I2C
401	help
402	  If you say yes here you get support for the Lite-On LTR-390UV-01
403	  ambient light and UV sensor.
404
405	  This driver can also be built as a module.  If so, the module
406	  will be called ltr390.
407
408config LTR501
409	tristate "LTR-501ALS-01 light sensor"
410	depends on I2C
411	select REGMAP_I2C
412	select IIO_BUFFER
413	select IIO_TRIGGERED_BUFFER
414	help
415	  If you say yes here you get support for the Lite-On LTR-501ALS-01
416	  ambient light and proximity sensor. This driver also supports LTR-559
417	  ALS/PS or LTR-301 ALS sensors.
418
419	  This driver can also be built as a module.  If so, the module
420	  will be called ltr501.
421
422config LTRF216A
423	tristate "Liteon LTRF216A Light Sensor"
424	depends on I2C
425	select REGMAP_I2C
426	help
427	  If you say Y or M here, you get support for Liteon LTRF216A
428	  Ambient Light Sensor.
429
430	  If built as a dynamically linked module, it will be called
431	  ltrf216a.
432
433config LV0104CS
434	tristate "LV0104CS Ambient Light Sensor"
435	depends on I2C
436	help
437	  Say Y here if you want to build support for the On Semiconductor
438	  LV0104CS ambient light sensor.
439
440	  To compile this driver as a module, choose M here:
441	  the module will be called lv0104cs.
442
443config MAX44000
444	tristate "MAX44000 Ambient and Infrared Proximity Sensor"
445	depends on I2C
446	select REGMAP_I2C
447	select IIO_BUFFER
448	select IIO_TRIGGERED_BUFFER
449	help
450	  Say Y here if you want to build support for Maxim Integrated's
451	  MAX44000 ambient and infrared proximity sensor device.
452
453	  To compile this driver as a module, choose M here:
454	  the module will be called max44000.
455
456config MAX44009
457	tristate "MAX44009 Ambient Light Sensor"
458	depends on I2C
459	select REGMAP_I2C
460	help
461	 Say Y here if you want to build support for Maxim Integrated's
462	 MAX44009 ambient light sensor device.
463
464	 To compile this driver as a module, choose M here:
465	 the module will be called max44009.
466
467config NOA1305
468	tristate "ON Semiconductor NOA1305 ambient light sensor"
469	depends on I2C
470	select REGMAP_I2C
471	help
472	 Say Y here if you want to build support for the ON Semiconductor
473	 NOA1305 ambient light sensor.
474
475	 To compile this driver as a module, choose M here:
476	 The module will be called noa1305.
477
478config OPT3001
479	tristate "Texas Instruments OPT3001 Light Sensor"
480	depends on I2C
481	help
482	  If you say Y or M here, you get support for Texas Instruments
483	  OPT3001 Ambient Light Sensor, OPT3002 Light-to-Digital Sensor.
484
485	  If built as a dynamically linked module, it will be called
486	  opt3001.
487
488config OPT4001
489	tristate "Texas Instruments OPT4001 Light Sensor"
490	depends on I2C
491	select REGMAP_I2C
492	help
493	  If you say Y or M here, you get support for Texas Instruments
494	  OPT4001 Ambient Light Sensor.
495
496	  If built as a dynamically linked module, it will be called
497	  opt4001.
498
499config OPT4060
500	tristate "Texas Instruments OPT4060 RGBW Color Sensor"
501	depends on I2C
502	select REGMAP_I2C
503	select IIO_BUFFER
504	select IIO_TRIGGERED_BUFFER
505	help
506	  If you say Y or M here, you get support for Texas Instruments
507	  OPT4060 RGBW Color Sensor.
508
509	  If built as a dynamically linked module, it will be called
510	  opt4060.
511
512config PA12203001
513	tristate "TXC PA12203001 light and proximity sensor"
514	depends on I2C
515	select REGMAP_I2C
516	help
517	  If you say yes here you get support for the TXC PA12203001
518	  ambient light and proximity sensor.
519
520	  This driver can also be built as a module.  If so, the module
521	  will be called pa12203001.
522
523config SI1133
524	tristate "SI1133 UV Index Sensor and Ambient Light Sensor"
525	depends on I2C
526	select REGMAP_I2C
527	  help
528	  Say Y here if you want to build a driver for the Silicon Labs SI1133
529	  UV Index Sensor and Ambient Light Sensor chip.
530
531	  To compile this driver as a module, choose M here: the module will be
532	  called si1133.
533
534config SI1145
535	tristate "SI1132 and SI1141/2/3/5/6/7 combined ALS, UV index and proximity sensor"
536	depends on I2C
537	select IIO_BUFFER
538	select IIO_TRIGGERED_BUFFER
539	help
540	  Say Y here if you want to build a driver for the Silicon Labs SI1132 or
541	  SI1141/2/3/5/6/7 combined ambient light, UV index and proximity sensor
542	  chips.
543
544	  To compile this driver as a module, choose M here: the module will be
545	  called si1145.
546
547config STK3310
548	tristate "STK3310 ALS and proximity sensor"
549	depends on I2C
550	select REGMAP_I2C
551	help
552	  Say yes here to get support for the Sensortek STK3310 ambient light
553	  and proximity sensor. The STK3311 model is also supported by this
554	  driver.
555
556	  Choosing M will build the driver as a module. If so, the module
557	  will be called stk3310.
558
559config ST_UVIS25
560	tristate "STMicroelectronics UVIS25 sensor driver"
561	depends on (I2C || SPI)
562	select IIO_BUFFER
563	select IIO_TRIGGERED_BUFFER
564	select ST_UVIS25_I2C if (I2C)
565	select ST_UVIS25_SPI if (SPI_MASTER)
566	help
567	  Say yes here to build support for STMicroelectronics UVIS25
568	  uv sensor
569
570	  To compile this driver as a module, choose M here: the module
571	  will be called st_uvis25.
572
573config ST_UVIS25_I2C
574	tristate
575	depends on ST_UVIS25
576	select REGMAP_I2C
577
578config ST_UVIS25_SPI
579	tristate
580	depends on ST_UVIS25
581	select REGMAP_SPI
582
583config TCS3414
584	tristate "TAOS TCS3414 digital color sensor"
585	depends on I2C
586	select IIO_BUFFER
587	select IIO_TRIGGERED_BUFFER
588	help
589	  If you say yes here you get support for the TAOS TCS3414
590	  family of digital color sensors.
591
592	  This driver can also be built as a module.  If so, the module
593	  will be called tcs3414.
594
595config TCS3472
596	tristate "TAOS TCS3472 color light-to-digital converter"
597	depends on I2C
598	select IIO_BUFFER
599	select IIO_TRIGGERED_BUFFER
600	help
601	  If you say yes here you get support for the TAOS TCS3472
602	  family of color light-to-digital converters with IR filter.
603
604	  This driver can also be built as a module.  If so, the module
605	  will be called tcs3472.
606
607config SENSORS_TSL2563
608	tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors"
609	depends on I2C
610	help
611	  If you say yes here you get support for the Taos TSL2560,
612	  TSL2561, TSL2562 and TSL2563 ambient light sensors.
613
614	  This driver can also be built as a module.  If so, the module
615	  will be called tsl2563.
616
617config TSL2583
618	tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters"
619	depends on I2C
620	help
621	  Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices.
622	  Access ALS data via iio, sysfs.
623
624config TSL2591
625        tristate "TAOS TSL2591 ambient light sensor"
626        depends on I2C
627        help
628          Select Y here for support of the AMS/TAOS TSL2591 ambient light sensor,
629          featuring channels for combined visible + IR intensity and lux illuminance.
630          Access data via iio and sysfs. Supports iio_events.
631
632          To compile this driver as a module, select M: the
633          module will be called tsl2591.
634
635config TSL2772
636	tristate "TAOS TSL/TMD2x71 and TSL/TMD2x72 Family of light and proximity sensors"
637	depends on I2C
638	help
639	  Support for: tsl2571, tsl2671, tmd2671, tsl2771, tmd2771, tsl2572, tsl2672,
640	  tmd2672, tsl2772, tmd2772 devices.
641	  Provides iio_events and direct access via sysfs.
642
643config TSL4531
644	tristate "TAOS TSL4531 ambient light sensors"
645	depends on I2C
646	help
647	  Say Y here if you want to build a driver for the TAOS TSL4531 family
648	  of ambient light sensors with direct lux output.
649
650	  To compile this driver as a module, choose M here: the
651	  module will be called tsl4531.
652
653config US5182D
654	tristate "UPISEMI light and proximity sensor"
655	depends on I2C
656	help
657	  If you say yes here you get support for the UPISEMI US5182D
658	  ambient light and proximity sensor.
659
660	  This driver can also be built as a module.  If so, the module
661	  will be called us5182d.
662
663config VCNL4000
664	tristate "VCNL4000/4010/4020/4200 combined ALS and proximity sensor"
665	select IIO_BUFFER
666	select IIO_TRIGGERED_BUFFER
667	depends on I2C
668	help
669	  Say Y here if you want to build a driver for the Vishay VCNL4000,
670	  VCNL4010, VCNL4020, VCNL4200 combined ambient light and proximity
671	  sensor.
672
673	  To compile this driver as a module, choose M here: the
674	  module will be called vcnl4000.
675
676config VCNL4035
677	tristate "VCNL4035 combined ALS and proximity sensor"
678	select IIO_BUFFER
679	select IIO_TRIGGERED_BUFFER
680	select REGMAP_I2C
681	depends on I2C
682	help
683	  Say Y here if you want to build a driver for the Vishay VCNL4035,
684	  combined ambient light (ALS) and proximity sensor. Currently only ALS
685	  function is available.
686
687	  To compile this driver as a module, choose M here: the
688	  module will be called vcnl4035.
689
690config VEML3235
691	tristate "VEML3235 ambient light sensor"
692	select REGMAP_I2C
693	select IIO_GTS_HELPER
694	depends on I2C
695	help
696	  Say Y here if you want to build a driver for the Vishay VEML3235
697	  ambient light sensor.
698
699	  To compile this driver as a module, choose M here: the
700	  module will be called veml3235.
701
702config VEML6030
703	tristate "VEML6030 and VEML6035 ambient light sensors"
704	select REGMAP_I2C
705	select IIO_BUFFER
706	select IIO_TRIGGERED_BUFFER
707	select IIO_GTS_HELPER
708	depends on I2C
709	help
710	  Say Y here if you want to build a driver for the Vishay VEML6030
711	  and VEML6035 ambient light sensors (ALS).
712
713	  To compile this driver as a module, choose M here: the
714	  module will be called veml6030.
715
716config VEML6040
717	tristate "VEML6040 RGBW light sensor"
718	select REGMAP_I2C
719	depends on I2C
720	help
721	  Say Y here if you want to build a driver for the Vishay VEML6040
722	  RGBW light sensor.
723
724	  To compile this driver as a module, choose M here: the
725	  module will be called veml6040.
726
727config VEML6070
728	tristate "VEML6070 UV A light sensor"
729	depends on I2C
730	help
731	  Say Y here if you want to build a driver for the Vishay VEML6070 UV A
732	  light sensor.
733
734	  To compile this driver as a module, choose M here: the
735	  module will be called veml6070.
736
737config VEML6075
738	tristate "VEML6075 UVA and UVB light sensor"
739	select REGMAP_I2C
740	depends on I2C
741	help
742	  Say Y here if you want to build a driver for the Vishay VEML6075 UVA
743	  and UVB light sensor.
744
745	  To compile this driver as a module, choose M here: the
746	  module will be called veml6075.
747
748config VL6180
749	tristate "VL6180 ALS, range and proximity sensor"
750	depends on I2C
751	help
752	  Say Y here if you want to build a driver for the STMicroelectronics
753	  VL6180 combined ambient light, range and proximity sensor.
754
755	  To compile this driver as a module, choose M here: the
756	  module will be called vl6180.
757
758config ZOPT2201
759	tristate "ZOPT2201 ALS and UV B sensor"
760	depends on I2C
761	help
762	  Say Y here if you want to build a driver for the IDT
763	  ZOPT2201 ambient light and UV B sensor.
764
765	  To compile this driver as a module, choose M here: the
766	  module will be called zopt2201.
767
768endmenu
769