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