forked from ~ljy/RK356X_SDK_RELEASE

blame | history | patch | commit | commitdiff
hc
2024-10-22 8ac6c7a54ed1b98d142dce24b11c6de6a1e239a5 
 kernel/drivers/iio/light/Kconfig
....@@ -1,3 +1,4 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
12 
23 #
34 # Light sensors
....@@ -13,11 +14,11 @@
1314 	select IIO_TRIGGERED_BUFFER
1415 	select IIO_KFIFO_BUF
1516 	help
16
-	 Say Y here if you want to build a driver for the ACPI0008
17
-	 Ambient Light Sensor.
17
+	  Say Y here if you want to build a driver for the ACPI0008
18
+	  Ambient Light Sensor.
1819 
19
-	 To compile this driver as a module, choose M here: the module will
20
-	 be called acpi-als.
20
+	  To compile this driver as a module, choose M here: the module will
21
+	  be called acpi-als.
2122 
2223 config ADJD_S311
2324 	tristate "ADJD-S311-CR999 digital color sensor"
....@@ -25,31 +26,52 @@
2526 	select IIO_TRIGGERED_BUFFER
2627 	depends on I2C
2728 	help
28
-	 If you say yes here you get support for the Avago ADJD-S311-CR999
29
-	 digital color light sensor.
29
+	  If you say yes here you get support for the Avago ADJD-S311-CR999
30
+	  digital color light sensor.
3031 
31
-	 This driver can also be built as a module.  If so, the module
32
-	 will be called adjd_s311.
32
+	  This driver can also be built as a module.  If so, the module
33
+	  will be called adjd_s311.
34
+
35
+config 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
+
46
+config 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.
3355 
3456 config AL3320A
3557 	tristate "AL3320A ambient light sensor"
3658 	depends on I2C
3759 	help
38
-	 Say Y here if you want to build a driver for the Dyna Image AL3320A
39
-	 ambient light sensor.
60
+	  Say Y here if you want to build a driver for the Dyna Image AL3320A
61
+	  ambient light sensor.
4062 
41
-	 To compile this driver as a module, choose M here: the
42
-	 module will be called al3320a.
63
+	  To compile this driver as a module, choose M here: the
64
+	  module will be called al3320a.
4365 
4466 config APDS9300
4567 	tristate "APDS9300 ambient light sensor"
4668 	depends on I2C
4769 	help
48
-	 Say Y here if you want to build a driver for the Avago APDS9300
49
-	 ambient light sensor.
70
+	  Say Y here if you want to build a driver for the Avago APDS9300
71
+	  ambient light sensor.
5072 
51
-	 To compile this driver as a module, choose M here: the
52
-	 module will be called apds9300.
73
+	  To compile this driver as a module, choose M here: the
74
+	  module will be called apds9300.
5375 
5476 config APDS9960
5577 	tristate "Avago APDS9960 gesture/RGB/ALS/proximity sensor"
....@@ -64,78 +86,93 @@
6486 	  To compile this driver as a module, choose M here: the
6587 	  module will be called apds9960
6688 
89
+config 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
+
67104 config BH1750
68105 	tristate "ROHM BH1750 ambient light sensor"
69106 	depends on I2C
70107 	help
71
-	 Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
72
-	 BH1750, BH1751 ambient light sensors.
108
+	  Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
109
+	  BH1750, BH1751 ambient light sensors.
73110 
74
-	 To compile this driver as a module, choose M here: the module will
75
-	 be called bh1750.
111
+	  To compile this driver as a module, choose M here: the module will
112
+	  be called bh1750.
76113 
77114 config BH1780
78115 	tristate "ROHM BH1780 ambient light sensor"
79116 	depends on I2C
80117 	help
81
-	 Say Y here to build support for the ROHM BH1780GLI ambient
82
-	 light sensor.
118
+	  Say Y here to build support for the ROHM BH1780GLI ambient
119
+	  light sensor.
83120 
84
-	 To compile this driver as a module, choose M here: the module will
85
-	 be called bh1780.
121
+	  To compile this driver as a module, choose M here: the module will
122
+	  be called bh1780.
86123 
87124 config CM32181
88125 	depends on I2C
89126 	tristate "CM32181 driver"
90127 	help
91
-	 Say Y here if you use cm32181.
92
-	 This option enables ambient light sensor using
93
-	 Capella cm32181 device driver.
128
+	  Say Y here if you use cm32181.
129
+	  This option enables ambient light sensor using
130
+	  Capella cm32181 device driver.
94131 
95
-	 To compile this driver as a module, choose M here:
96
-	 the module will be called cm32181.
132
+	  To compile this driver as a module, choose M here:
133
+	  the module will be called cm32181.
97134 
98135 config CM3232
99136 	depends on I2C
100137 	tristate "CM3232 ambient light sensor"
101138 	help
102
-	 Say Y here if you use cm3232.
103
-	 This option enables ambient light sensor using
104
-	 Capella Microsystems cm3232 device driver.
139
+	  Say Y here if you use cm3232.
140
+	  This option enables ambient light sensor using
141
+	  Capella Microsystems cm3232 device driver.
105142 
106
-	 To compile this driver as a module, choose M here:
107
-	 the module will be called cm3232.
143
+	  To compile this driver as a module, choose M here:
144
+	  the module will be called cm3232.
108145 
109146 config CM3323
110147 	depends on I2C
111148 	tristate "Capella CM3323 color light sensor"
112149 	help
113
-	 Say Y here if you want to build a driver for Capella CM3323
114
-	 color sensor.
150
+	  Say Y here if you want to build a driver for Capella CM3323
151
+	  color sensor.
115152 
116
-	 To compile this driver as a module, choose M here: the module will
117
-	 be called cm3323.
153
+	  To compile this driver as a module, choose M here: the module will
154
+	  be called cm3323.
118155 
119156 config CM3605
120157 	tristate "Capella CM3605 ambient light and proximity sensor"
121158 	depends on OF
122159 	help
123
-	 Say Y here if you want to build a driver for Capella CM3605
124
-	 ambient light and short range proximity sensor.
160
+	  Say Y here if you want to build a driver for Capella CM3605
161
+	  ambient light and short range proximity sensor.
125162 
126
-	 To compile this driver as a module, choose M here: the module will
127
-	 be called cm3605.
163
+	  To compile this driver as a module, choose M here: the module will
164
+	  be called cm3605.
128165 
129166 config CM36651
130167 	depends on I2C
131168 	tristate "CM36651 driver"
132169 	help
133
-	 Say Y here if you use cm36651.
134
-	 This option enables proximity & RGB sensor using
135
-	 Capella cm36651 device driver.
170
+	  Say Y here if you use cm36651.
171
+	  This option enables proximity & RGB sensor using
172
+	  Capella cm36651 device driver.
136173 
137
-	 To compile this driver as a module, choose M here:
138
-	 the module will be called cm36651.
174
+	  To compile this driver as a module, choose M here:
175
+	  the module will be called cm36651.
139176 
140177 config IIO_CROS_EC_LIGHT_PROX
141178 	tristate "ChromeOS EC Light and Proximity Sensors"
....@@ -146,6 +183,17 @@
146183 
147184 	  To compile this driver as a module, choose M here:
148185 	  the module will be called cros_ec_light_prox.
186
+
187
+config 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.
149197 
150198 config GP2AP020A00F
151199 	tristate "Sharp GP2AP020A00F Proximity/ALS sensor"
....@@ -161,27 +209,37 @@
161209 	  To compile this driver as a module, choose M here: the
162210 	  module will be called gp2ap020a00f.
163211 
212
+config 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
+
164222 config SENSORS_ISL29018
165223 	tristate "Intersil 29018 light and proximity sensor"
166224 	depends on I2C
167225 	select REGMAP_I2C
168226 	default n
169227 	help
170
-	 If you say yes here you get support for ambient light sensing and
171
-	 proximity infrared sensing from Intersil ISL29018.
172
-	 This driver will provide the measurements of ambient light intensity
173
-	 in lux, proximity infrared sensing and normal infrared sensing.
174
-	 Data from sensor is accessible via sysfs.
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.
175233 
176234 config SENSORS_ISL29028
177235 	tristate "Intersil ISL29028 Concurrent Light and Proximity Sensor"
178236 	depends on I2C
179237 	select REGMAP_I2C
180238 	help
181
-	 Provides driver for the Intersil's ISL29028 device.
182
-	 This driver supports the sysfs interface to get the ALS, IR intensity,
183
-	 Proximity value via iio. The ISL29028 provides the concurrent sensing
184
-	 of ambient light and proximity.
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.
185243 
186244 config ISL29125
187245 	tristate "Intersil ISL29125 digital color light sensor"
....@@ -198,7 +256,6 @@
198256 config HID_SENSOR_ALS
199257 	depends on HID_SENSOR_HUB
200258 	select IIO_BUFFER
201
-	select IIO_TRIGGERED_BUFFER
202259 	select HID_SENSOR_IIO_COMMON
203260 	select HID_SENSOR_IIO_TRIGGER
204261 	tristate "HID ALS"
....@@ -212,7 +269,6 @@
212269 config HID_SENSOR_PROX
213270 	depends on HID_SENSOR_HUB
214271 	select IIO_BUFFER
215
-	select IIO_TRIGGERED_BUFFER
216272 	select HID_SENSOR_IIO_COMMON
217273 	select HID_SENSOR_IIO_TRIGGER
218274 	tristate "HID PROX"
....@@ -228,22 +284,24 @@
228284 	depends on I2C
229285 	select REGMAP_I2C
230286 	help
231
-	 Say Y here if you want to build a IIO driver for JSA1212
232
-	 proximity & ALS sensor device.
287
+	  Say Y here if you want to build a IIO driver for JSA1212
288
+	  proximity & ALS sensor device.
233289 
234
-	 To compile this driver as a module, choose M here:
235
-	 the module will be called jsa1212.
290
+	  To compile this driver as a module, choose M here:
291
+	  the module will be called jsa1212.
236292 
237293 config RPR0521
238294 	tristate "ROHM RPR0521 ALS and proximity sensor driver"
239295 	depends on I2C
240296 	select REGMAP_I2C
297
+	select IIO_BUFFER
298
+	select IIO_TRIGGERED_BUFFER
241299 	help
242
-	 Say Y here if you want to build support for ROHM's RPR0521
243
-	 ambient light and proximity sensor device.
300
+	  Say Y here if you want to build support for ROHM's RPR0521
301
+	  ambient light and proximity sensor device.
244302 
245
-	 To compile this driver as a module, choose M here:
246
-	 the module will be called rpr0521.
303
+	  To compile this driver as a module, choose M here:
304
+	  the module will be called rpr0521.
247305 
248306 config SENSORS_LM3533
249307 	tristate "LM3533 ambient light sensor"
....@@ -269,22 +327,22 @@
269327 	select IIO_BUFFER
270328 	select IIO_TRIGGERED_BUFFER
271329 	help
272
-	 If you say yes here you get support for the Lite-On LTR-501ALS-01
273
-	 ambient light and proximity sensor. This driver also supports LTR-559
274
-	 ALS/PS or LTR-301 ALS sensors.
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.
275333 
276
-	 This driver can also be built as a module.  If so, the module
277
-         will be called ltr501.
334
+	  This driver can also be built as a module.  If so, the module
335
+	  will be called ltr501.
278336 
279337 config LV0104CS
280338 	tristate "LV0104CS Ambient Light Sensor"
281339 	depends on I2C
282340 	help
283
-	 Say Y here if you want to build support for the On Semiconductor
284
-	 LV0104CS ambient light sensor.
341
+	  Say Y here if you want to build support for the On Semiconductor
342
+	  LV0104CS ambient light sensor.
285343 
286
-	 To compile this driver as a module, choose M here:
287
-	 the module will be called lv0104cs.
344
+	  To compile this driver as a module, choose M here:
345
+	  the module will be called lv0104cs.
288346 
289347 config MAX44000
290348 	tristate "MAX44000 Ambient and Infrared Proximity Sensor"
....@@ -293,11 +351,33 @@
293351 	select IIO_BUFFER
294352 	select IIO_TRIGGERED_BUFFER
295353 	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
+
360
+config MAX44009
361
+	tristate "MAX44009 Ambient Light Sensor"
362
+	depends on I2C
363
+	select REGMAP_I2C
364
+	help
296365 	 Say Y here if you want to build support for Maxim Integrated's
297
-	 MAX44000 ambient and infrared proximity sensor device.
366
+	 MAX44009 ambient light sensor device.
298367 
299368 	 To compile this driver as a module, choose M here:
300
-	 the module will be called max44000.
369
+	 the module will be called max44009.
370
+
371
+config 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.
301381 
302382 config OPT3001
303383 	tristate "Texas Instruments OPT3001 Light Sensor"
....@@ -310,15 +390,15 @@
310390 	  opt3001.
311391 
312392 config PA12203001
313
-        tristate "TXC PA12203001 light and proximity sensor"
314
-        depends on I2C
315
-        select REGMAP_I2C
316
-        help
317
-         If you say yes here you get support for the TXC PA12203001
318
-         ambient light and proximity sensor.
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.
319399 
320
-         This driver can also be built as a module.  If so, the module
321
-         will be called pa12203001.
400
+	  This driver can also be built as a module.  If so, the module
401
+	  will be called pa12203001.
322402 
323403 config SI1133
324404 	tristate "SI1133 UV Index Sensor and Ambient Light Sensor"
....@@ -349,12 +429,12 @@
349429 	depends on I2C
350430 	select REGMAP_I2C
351431 	help
352
-	 Say yes here to get support for the Sensortek STK3310 ambient light
353
-	 and proximity sensor. The STK3311 model is also supported by this
354
-	 driver.
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.
355435 
356
-	 Choosing M will build the driver as a module. If so, the module
357
-	 will be called stk3310.
436
+	  Choosing M will build the driver as a module. If so, the module
437
+	  will be called stk3310.
358438 
359439 config ST_UVIS25
360440 	tristate "STMicroelectronics UVIS25 sensor driver"
....@@ -386,11 +466,11 @@
386466 	select IIO_BUFFER
387467 	select IIO_TRIGGERED_BUFFER
388468 	help
389
-	 If you say yes here you get support for the TAOS TCS3414
390
-	 family of digital color sensors.
469
+	  If you say yes here you get support for the TAOS TCS3414
470
+	  family of digital color sensors.
391471 
392
-	 This driver can also be built as a module.  If so, the module
393
-	 will be called tcs3414.
472
+	  This driver can also be built as a module.  If so, the module
473
+	  will be called tcs3414.
394474 
395475 config TCS3472
396476 	tristate "TAOS TCS3472 color light-to-digital converter"
....@@ -398,96 +478,133 @@
398478 	select IIO_BUFFER
399479 	select IIO_TRIGGERED_BUFFER
400480 	help
401
-	 If you say yes here you get support for the TAOS TCS3472
402
-	 family of color light-to-digital converters with IR filter.
481
+	  If you say yes here you get support for the TAOS TCS3472
482
+	  family of color light-to-digital converters with IR filter.
403483 
404
-	 This driver can also be built as a module.  If so, the module
405
-	 will be called tcs3472.
484
+	  This driver can also be built as a module.  If so, the module
485
+	  will be called tcs3472.
406486 
407487 config SENSORS_TSL2563
408488 	tristate "TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ambient light sensors"
409489 	depends on I2C
410490 	help
411
-	 If you say yes here you get support for the Taos TSL2560,
412
-	 TSL2561, TSL2562 and TSL2563 ambient light sensors.
491
+	  If you say yes here you get support for the Taos TSL2560,
492
+	  TSL2561, TSL2562 and TSL2563 ambient light sensors.
413493 
414
-	 This driver can also be built as a module.  If so, the module
415
-	 will be called tsl2563.
494
+	  This driver can also be built as a module.  If so, the module
495
+	  will be called tsl2563.
416496 
417497 config TSL2583
418498 	tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters"
419499 	depends on I2C
420500 	help
421
-	 Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices.
422
-	 Access ALS data via iio, sysfs.
501
+	  Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices.
502
+	  Access ALS data via iio, sysfs.
423503 
424504 config TSL2772
425505 	tristate "TAOS TSL/TMD2x71 and TSL/TMD2x72 Family of light and proximity sensors"
426506 	depends on I2C
427507 	help
428
-	 Support for: tsl2571, tsl2671, tmd2671, tsl2771, tmd2771, tsl2572, tsl2672,
429
-	 tmd2672, tsl2772, tmd2772 devices.
430
-	 Provides iio_events and direct access via sysfs.
508
+	  Support for: tsl2571, tsl2671, tmd2671, tsl2771, tmd2771, tsl2572, tsl2672,
509
+	  tmd2672, tsl2772, tmd2772 devices.
510
+	  Provides iio_events and direct access via sysfs.
431511 
432512 config TSL4531
433513 	tristate "TAOS TSL4531 ambient light sensors"
434514 	depends on I2C
435515 	help
436
-	 Say Y here if you want to build a driver for the TAOS TSL4531 family
437
-	 of ambient light sensors with direct lux output.
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.
438518 
439
-	 To compile this driver as a module, choose M here: the
440
-	 module will be called tsl4531.
519
+	  To compile this driver as a module, choose M here: the
520
+	  module will be called tsl4531.
521
+
522
+config UCS12CM0
523
+	tristate "UCS12CM0 illuminance and correlated color temperature sensor"
524
+	depends on I2C
525
+	help
526
+	  Say Y here if you want to build a driver for the Ultra Capteur
527
+	  UCS12CM0 illuminance and correlated color temperature sensor.
528
+
529
+	  To compile this driver as a module, choose M here: the
530
+	  module will be called ucs12cm0.
441531 
442532 config US5182D
443533 	tristate "UPISEMI light and proximity sensor"
444534 	depends on I2C
445535 	help
446
-	 If you say yes here you get support for the UPISEMI US5182D
447
-	 ambient light and proximity sensor.
536
+	  If you say yes here you get support for the UPISEMI US5182D
537
+	  ambient light and proximity sensor.
448538 
449
-	 This driver can also be built as a module.  If so, the module
450
-	 will be called us5182d.
539
+	  This driver can also be built as a module.  If so, the module
540
+	  will be called us5182d.
451541 
452542 config VCNL4000
453543 	tristate "VCNL4000/4010/4020/4200 combined ALS and proximity sensor"
544
+	select IIO_BUFFER
545
+	select IIO_TRIGGERED_BUFFER
454546 	depends on I2C
455547 	help
456
-	 Say Y here if you want to build a driver for the Vishay VCNL4000,
457
-	 VCNL4010, VCNL4020, VCNL4200 combined ambient light and proximity
458
-	 sensor.
548
+	  Say Y here if you want to build a driver for the Vishay VCNL4000,
549
+	  VCNL4010, VCNL4020, VCNL4200 combined ambient light and proximity
550
+	  sensor.
459551 
460
-	 To compile this driver as a module, choose M here: the
461
-	 module will be called vcnl4000.
552
+	  To compile this driver as a module, choose M here: the
553
+	  module will be called vcnl4000.
554
+
555
+config VCNL4035
556
+	tristate "VCNL4035 combined ALS and proximity sensor"
557
+	select IIO_BUFFER
558
+	select IIO_TRIGGERED_BUFFER
559
+	select REGMAP_I2C
560
+	depends on I2C
561
+	help
562
+	  Say Y here if you want to build a driver for the Vishay VCNL4035,
563
+	  combined ambient light (ALS) and proximity sensor. Currently only ALS
564
+	  function is available.
565
+
566
+	  To compile this driver as a module, choose M here: the
567
+	  module will be called vcnl4035.
568
+
569
+config VEML6030
570
+	tristate "VEML6030 ambient light sensor"
571
+	select REGMAP_I2C
572
+	depends on I2C
573
+	help
574
+	  Say Y here if you want to build a driver for the Vishay VEML6030
575
+	  ambient light sensor (ALS).
576
+
577
+	  To compile this driver as a module, choose M here: the
578
+	  module will be called veml6030.
462579 
463580 config VEML6070
464581 	tristate "VEML6070 UV A light sensor"
465582 	depends on I2C
466583 	help
467
-	 Say Y here if you want to build a driver for the Vishay VEML6070 UV A
468
-	 light sensor.
584
+	  Say Y here if you want to build a driver for the Vishay VEML6070 UV A
585
+	  light sensor.
469586 
470
-	 To compile this driver as a module, choose M here: the
471
-	 module will be called veml6070.
587
+	  To compile this driver as a module, choose M here: the
588
+	  module will be called veml6070.
472589 
473590 config VL6180
474591 	tristate "VL6180 ALS, range and proximity sensor"
475592 	depends on I2C
476593 	help
477
-	 Say Y here if you want to build a driver for the STMicroelectronics
478
-	 VL6180 combined ambient light, range and proximity sensor.
594
+	  Say Y here if you want to build a driver for the STMicroelectronics
595
+	  VL6180 combined ambient light, range and proximity sensor.
479596 
480
-	 To compile this driver as a module, choose M here: the
481
-	 module will be called vl6180.
597
+	  To compile this driver as a module, choose M here: the
598
+	  module will be called vl6180.
482599 
483600 config ZOPT2201
484601 	tristate "ZOPT2201 ALS and UV B sensor"
485602 	depends on I2C
486603 	help
487
-	 Say Y here if you want to build a driver for the IDT
488
-	 ZOPT2201 ambient light and UV B sensor.
604
+	  Say Y here if you want to build a driver for the IDT
605
+	  ZOPT2201 ambient light and UV B sensor.
489606 
490
-	 To compile this driver as a module, choose M here: the
491
-	 module will be called zopt2201.
607
+	  To compile this driver as a module, choose M here: the
608
+	  module will be called zopt2201.
492609 
493610 endmenu