xref: /openbmc/linux/drivers/iio/light/Kconfig (revision 92b19ff5)
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 BH1750
54	tristate "ROHM BH1750 ambient light sensor"
55	depends on I2C
56	help
57	 Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
58	 BH1750, BH1751 ambient light sensors.
59
60	 To compile this driver as a module, choose M here: the module will
61	 be called bh1750.
62
63config CM32181
64	depends on I2C
65	tristate "CM32181 driver"
66	help
67	 Say Y here if you use cm32181.
68	 This option enables ambient light sensor using
69	 Capella cm32181 device driver.
70
71	 To compile this driver as a module, choose M here:
72	 the module will be called cm32181.
73
74config CM3232
75	depends on I2C
76	tristate "CM3232 ambient light sensor"
77	help
78	 Say Y here if you use cm3232.
79	 This option enables ambient light sensor using
80	 Capella Microsystems cm3232 device driver.
81
82	 To compile this driver as a module, choose M here:
83	 the module will be called cm3232.
84
85config CM3323
86	depends on I2C
87	tristate "Capella CM3323 color light sensor"
88	help
89	 Say Y here if you want to build a driver for Capela CM3323
90	 color sensor.
91
92	 To compile this driver as a module, choose M here: the module will
93	 be called cm3323.
94
95config CM36651
96	depends on I2C
97	tristate "CM36651 driver"
98	help
99	 Say Y here if you use cm36651.
100	 This option enables proximity & RGB sensor using
101	 Capella cm36651 device driver.
102
103	 To compile this driver as a module, choose M here:
104	 the module will be called cm36651.
105
106config GP2AP020A00F
107	tristate "Sharp GP2AP020A00F Proximity/ALS sensor"
108	depends on I2C
109	select REGMAP_I2C
110	select IIO_BUFFER
111	select IIO_TRIGGERED_BUFFER
112	select IRQ_WORK
113	help
114	  Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip
115	  hooked to an I2C bus.
116
117	  To compile this driver as a module, choose M here: the
118	  module will be called gp2ap020a00f.
119
120config ISL29125
121	tristate "Intersil ISL29125 digital color light sensor"
122	depends on I2C
123	select IIO_BUFFER
124	select IIO_TRIGGERED_BUFFER
125	help
126	  Say Y here if you want to build a driver for the Intersil ISL29125
127	  RGB light sensor for I2C.
128
129	  To compile this driver as a module, choose M here: the module will be
130	  called isl29125.
131
132config HID_SENSOR_ALS
133	depends on HID_SENSOR_HUB
134	select IIO_BUFFER
135	select IIO_TRIGGERED_BUFFER
136	select HID_SENSOR_IIO_COMMON
137	select HID_SENSOR_IIO_TRIGGER
138	tristate "HID ALS"
139	help
140	  Say yes here to build support for the HID SENSOR
141	  Ambient light sensor.
142
143	  To compile this driver as a module, choose M here: the
144	  module will be called hid-sensor-als.
145
146config HID_SENSOR_PROX
147	depends on HID_SENSOR_HUB
148	select IIO_BUFFER
149	select IIO_TRIGGERED_BUFFER
150	select HID_SENSOR_IIO_COMMON
151	select HID_SENSOR_IIO_TRIGGER
152	tristate "HID PROX"
153	help
154	  Say yes here to build support for the HID SENSOR
155	  Proximity sensor.
156
157	  To compile this driver as a module, choose M here: the
158	  module will be called hid-sensor-prox.
159
160config JSA1212
161	tristate "JSA1212 ALS and proximity sensor driver"
162	depends on I2C
163	select REGMAP_I2C
164	help
165	 Say Y here if you want to build a IIO driver for JSA1212
166	 proximity & ALS sensor device.
167
168	 To compile this driver as a module, choose M here:
169	 the module will be called jsa1212.
170
171config SENSORS_LM3533
172	tristate "LM3533 ambient light sensor"
173	depends on MFD_LM3533
174	help
175	  If you say yes here you get support for the ambient light sensor
176	  interface on National Semiconductor / TI LM3533 Lighting Power
177	  chips.
178
179	  The sensor interface can be used to control the LEDs and backlights
180	  of the chip through defining five light zones and three sets of
181	  corresponding output-current values.
182
183	  The driver provides raw and mean adc readings along with the current
184	  light zone through sysfs. A threshold event can be generated on zone
185	  changes. The ALS-control output values can be set per zone for the
186	  three current output channels.
187
188config LTR501
189	tristate "LTR-501ALS-01 light sensor"
190	depends on I2C
191	select REGMAP_I2C
192	select IIO_BUFFER
193	select IIO_TRIGGERED_BUFFER
194	help
195	 If you say yes here you get support for the Lite-On LTR-501ALS-01
196	 ambient light and proximity sensor. This driver also supports LTR-559
197	 ALS/PS or LTR-301 ALS sensors.
198
199	 This driver can also be built as a module.  If so, the module
200         will be called ltr501.
201
202config STK3310
203	tristate "STK3310 ALS and proximity sensor"
204	depends on I2C
205	select REGMAP_I2C
206	help
207	 Say yes here to get support for the Sensortek STK3310 ambient light
208	 and proximity sensor. The STK3311 model is also supported by this
209	 driver.
210
211	 Choosing M will build the driver as a module. If so, the module
212	 will be called stk3310.
213
214config TCS3414
215	tristate "TAOS TCS3414 digital color sensor"
216	depends on I2C
217	select IIO_BUFFER
218	select IIO_TRIGGERED_BUFFER
219	help
220	 If you say yes here you get support for the TAOS TCS3414
221	 family of digital color sensors.
222
223	 This driver can also be built as a module.  If so, the module
224	 will be called tcs3414.
225
226config TCS3472
227	tristate "TAOS TCS3472 color light-to-digital converter"
228	depends on I2C
229	select IIO_BUFFER
230	select IIO_TRIGGERED_BUFFER
231	help
232	 If you say yes here you get support for the TAOS TCS3472
233	 family of color light-to-digital converters with IR filter.
234
235	 This driver can also be built as a module.  If so, the module
236	 will be called tcs3472.
237
238config SENSORS_TSL2563
239	tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors"
240	depends on I2C
241	help
242	 If you say yes here you get support for the Taos TSL2560,
243	 TSL2561, TSL2562 and TSL2563 ambient light sensors.
244
245	 This driver can also be built as a module.  If so, the module
246	 will be called tsl2563.
247
248config TSL4531
249	tristate "TAOS TSL4531 ambient light sensors"
250	depends on I2C
251	help
252	 Say Y here if you want to build a driver for the TAOS TSL4531 family
253	 of ambient light sensors with direct lux output.
254
255	 To compile this driver as a module, choose M here: the
256	 module will be called tsl4531.
257
258config VCNL4000
259	tristate "VCNL4000 combined ALS and proximity sensor"
260	depends on I2C
261	help
262	 Say Y here if you want to build a driver for the Vishay VCNL4000
263	 combined ambient light and proximity sensor.
264
265	 To compile this driver as a module, choose M here: the
266	 module will be called vcnl4000.
267
268endmenu
269