xref: /linux/drivers/iio/light/Kconfig (revision fcc8487d477a3452a1d0ccbdd4c5e0e1e3cb8bed)
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 ISL29125
176	tristate "Intersil ISL29125 digital color light sensor"
177	depends on I2C
178	select IIO_BUFFER
179	select IIO_TRIGGERED_BUFFER
180	help
181	  Say Y here if you want to build a driver for the Intersil ISL29125
182	  RGB light sensor for I2C.
183
184	  To compile this driver as a module, choose M here: the module will be
185	  called isl29125.
186
187config HID_SENSOR_ALS
188	depends on HID_SENSOR_HUB
189	select IIO_BUFFER
190	select IIO_TRIGGERED_BUFFER
191	select HID_SENSOR_IIO_COMMON
192	select HID_SENSOR_IIO_TRIGGER
193	tristate "HID ALS"
194	help
195	  Say yes here to build support for the HID SENSOR
196	  Ambient light sensor.
197
198	  To compile this driver as a module, choose M here: the
199	  module will be called hid-sensor-als.
200
201config HID_SENSOR_PROX
202	depends on HID_SENSOR_HUB
203	select IIO_BUFFER
204	select IIO_TRIGGERED_BUFFER
205	select HID_SENSOR_IIO_COMMON
206	select HID_SENSOR_IIO_TRIGGER
207	tristate "HID PROX"
208	help
209	  Say yes here to build support for the HID SENSOR
210	  Proximity sensor.
211
212	  To compile this driver as a module, choose M here: the
213	  module will be called hid-sensor-prox.
214
215config JSA1212
216	tristate "JSA1212 ALS and proximity sensor driver"
217	depends on I2C
218	select REGMAP_I2C
219	help
220	 Say Y here if you want to build a IIO driver for JSA1212
221	 proximity & ALS sensor device.
222
223	 To compile this driver as a module, choose M here:
224	 the module will be called jsa1212.
225
226config RPR0521
227	tristate "ROHM RPR0521 ALS and proximity sensor driver"
228	depends on I2C
229	select REGMAP_I2C
230	help
231	 Say Y here if you want to build support for ROHM's RPR0521
232	 ambient light and proximity sensor device.
233
234	 To compile this driver as a module, choose M here:
235	 the module will be called rpr0521.
236
237config SENSORS_LM3533
238	tristate "LM3533 ambient light sensor"
239	depends on MFD_LM3533
240	help
241	  If you say yes here you get support for the ambient light sensor
242	  interface on National Semiconductor / TI LM3533 Lighting Power
243	  chips.
244
245	  The sensor interface can be used to control the LEDs and backlights
246	  of the chip through defining five light zones and three sets of
247	  corresponding output-current values.
248
249	  The driver provides raw and mean adc readings along with the current
250	  light zone through sysfs. A threshold event can be generated on zone
251	  changes. The ALS-control output values can be set per zone for the
252	  three current output channels.
253
254config LTR501
255	tristate "LTR-501ALS-01 light sensor"
256	depends on I2C
257	select REGMAP_I2C
258	select IIO_BUFFER
259	select IIO_TRIGGERED_BUFFER
260	help
261	 If you say yes here you get support for the Lite-On LTR-501ALS-01
262	 ambient light and proximity sensor. This driver also supports LTR-559
263	 ALS/PS or LTR-301 ALS sensors.
264
265	 This driver can also be built as a module.  If so, the module
266         will be called ltr501.
267
268config MAX44000
269	tristate "MAX44000 Ambient and Infrared Proximity Sensor"
270	depends on I2C
271	select REGMAP_I2C
272	select IIO_BUFFER
273	select IIO_TRIGGERED_BUFFER
274	help
275	 Say Y here if you want to build support for Maxim Integrated's
276	 MAX44000 ambient and infrared proximity sensor device.
277
278	 To compile this driver as a module, choose M here:
279	 the module will be called max44000.
280
281config OPT3001
282	tristate "Texas Instruments OPT3001 Light Sensor"
283	depends on I2C
284	help
285	  If you say Y or M here, you get support for Texas Instruments
286	  OPT3001 Ambient Light Sensor.
287
288	  If built as a dynamically linked module, it will be called
289	  opt3001.
290
291config PA12203001
292        tristate "TXC PA12203001 light and proximity sensor"
293        depends on I2C
294        select REGMAP_I2C
295        help
296         If you say yes here you get support for the TXC PA12203001
297         ambient light and proximity sensor.
298
299         This driver can also be built as a module.  If so, the module
300         will be called pa12203001.
301
302config SI1145
303	tristate "SI1132 and SI1141/2/3/5/6/7 combined ALS, UV index and proximity sensor"
304	depends on I2C
305	select IIO_BUFFER
306	select IIO_TRIGGERED_BUFFER
307	help
308	  Say Y here if you want to build a driver for the Silicon Labs SI1132 or
309	  SI1141/2/3/5/6/7 combined ambient light, UV index and proximity sensor
310	  chips.
311
312	  To compile this driver as a module, choose M here: the module will be
313	  called si1145.
314
315config STK3310
316	tristate "STK3310 ALS and proximity sensor"
317	depends on I2C
318	select REGMAP_I2C
319	help
320	 Say yes here to get support for the Sensortek STK3310 ambient light
321	 and proximity sensor. The STK3311 model is also supported by this
322	 driver.
323
324	 Choosing M will build the driver as a module. If so, the module
325	 will be called stk3310.
326
327config TCS3414
328	tristate "TAOS TCS3414 digital color sensor"
329	depends on I2C
330	select IIO_BUFFER
331	select IIO_TRIGGERED_BUFFER
332	help
333	 If you say yes here you get support for the TAOS TCS3414
334	 family of digital color sensors.
335
336	 This driver can also be built as a module.  If so, the module
337	 will be called tcs3414.
338
339config TCS3472
340	tristate "TAOS TCS3472 color light-to-digital converter"
341	depends on I2C
342	select IIO_BUFFER
343	select IIO_TRIGGERED_BUFFER
344	help
345	 If you say yes here you get support for the TAOS TCS3472
346	 family of color light-to-digital converters with IR filter.
347
348	 This driver can also be built as a module.  If so, the module
349	 will be called tcs3472.
350
351config SENSORS_TSL2563
352	tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors"
353	depends on I2C
354	help
355	 If you say yes here you get support for the Taos TSL2560,
356	 TSL2561, TSL2562 and TSL2563 ambient light sensors.
357
358	 This driver can also be built as a module.  If so, the module
359	 will be called tsl2563.
360
361config TSL2583
362	tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters"
363	depends on I2C
364	help
365	 Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices.
366	 Access ALS data via iio, sysfs.
367
368config TSL4531
369	tristate "TAOS TSL4531 ambient light sensors"
370	depends on I2C
371	help
372	 Say Y here if you want to build a driver for the TAOS TSL4531 family
373	 of ambient light sensors with direct lux output.
374
375	 To compile this driver as a module, choose M here: the
376	 module will be called tsl4531.
377
378config US5182D
379	tristate "UPISEMI light and proximity sensor"
380	depends on I2C
381	help
382	 If you say yes here you get support for the UPISEMI US5182D
383	 ambient light and proximity sensor.
384
385	 This driver can also be built as a module.  If so, the module
386	 will be called us5182d.
387
388config VCNL4000
389	tristate "VCNL4000/4010/4020 combined ALS and proximity sensor"
390	depends on I2C
391	help
392	 Say Y here if you want to build a driver for the Vishay VCNL4000,
393	 VCNL4010, VCNL4020 combined ambient light and proximity sensor.
394
395	 To compile this driver as a module, choose M here: the
396	 module will be called vcnl4000.
397
398config VEML6070
399	tristate "VEML6070 UV A light sensor"
400	depends on I2C
401	help
402	 Say Y here if you want to build a driver for the Vishay VEML6070 UV A
403	 light sensor.
404
405	 To compile this driver as a module, choose M here: the
406	 module will be called veml6070.
407
408config VL6180
409	tristate "VL6180 ALS, range and proximity sensor"
410	depends on I2C
411	help
412	 Say Y here if you want to build a driver for the STMicroelectronics
413	 VL6180 combined ambient light, range and proximity sensor.
414
415	 To compile this driver as a module, choose M here: the
416	 module will be called vl6180.
417
418endmenu
419