Lines Matching +full:on +full:- +full:module
1 # SPDX-License-Identifier: GPL-2.0-only
12 depends on ACPI
20 To compile this driver as a module, choose M here: the module will
21 be called acpi-als.
24 tristate "ADJD-S311-CR999 digital color sensor"
27 depends on I2C
29 If you say yes here you get support for the Avago ADJD-S311-CR999
32 This driver can also be built as a module. If so, the module
38 depends on I2C
43 To compile this driver as a module, choose M here: the
44 module will be called adux1020.
48 depends on I2C
53 To compile this driver as a module, choose M here: the
54 module will be called al3010.
58 depends on I2C
63 To compile this driver as a module, choose M here: the
64 module will be called al3320a.
68 depends on I2C
73 To compile this driver as a module, choose M here: the
74 module will be called apds9300.
78 depends on I2C
85 If built as a dynamically linked module, it will be called
93 depends on I2C
98 To compile this driver as a module, choose M here: the
99 module will be called apds9960
103 depends on I2C
114 This driver can also be built as a module. If so, the module
119 depends on I2C
127 To compile this driver as a module, choose M here: the module will
132 depends on I2C
137 To compile this driver as a module, choose M here: the module will
142 depends on I2C
147 To compile this driver as a module, choose M here: the module will
151 depends on I2C
158 To compile this driver as a module, choose M here:
159 the module will be called cm32181.
162 depends on I2C
169 To compile this driver as a module, choose M here:
170 the module will be called cm3232.
173 depends on I2C
179 To compile this driver as a module, choose M here: the module will
188 To compile this driver as a module, choose M here: the module will
192 depends on I2C
199 To compile this driver as a module, choose M here:
200 the module will be called cm36651.
204 depends on IIO_CROS_EC_SENSORS_CORE
209 To compile this driver as a module, choose M here:
210 the module will be called cros_ec_light_prox.
214 depends on I2C
217 Say Y here if you have a Sharp GP2AP002 proximity/ALS combo-chip
220 To compile this driver as a module, choose M here: the
221 module will be called gp2ap002.
225 depends on I2C
231 Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip
234 To compile this driver as a module, choose M here: the
235 module will be called gp2ap020a00f.
239 depends on MFD_IQS62X || COMPILE_TEST
244 To compile this driver as a module, choose M here: the module
245 will be called iqs621-als.
249 depends on I2C
260 depends on I2C
270 depends on I2C
277 To compile this driver as a module, choose M here: the module will be
282 depends on I2C
292 To compile this driver as a module, choose M here: the module will be
296 depends on HID_SENSOR_HUB
305 To compile this driver as a module, choose M here: the
306 module will be called hid-sensor-als.
309 depends on HID_SENSOR_HUB
318 To compile this driver as a module, choose M here: the
319 module will be called hid-sensor-prox.
323 depends on I2C
329 To compile this driver as a module, choose M here:
330 the module will be called jsa1212.
334 depends on I2C
350 depends on I2C
364 depends on I2C
372 To compile this driver as a module, choose M here:
373 the module will be called rpr0521.
377 depends on MFD_LM3533
380 interface on National Semiconductor / TI LM3533 Lighting Power
385 corresponding output-current values.
388 light zone through sysfs. A threshold event can be generated on zone
389 changes. The ALS-control output values can be set per zone for the
393 tristate "LTR-390UV-01 ambient light and UV sensor"
394 depends on I2C
397 If you say yes here you get support for the Lite-On LTR-390UV-01
400 This driver can also be built as a module. If so, the module
404 tristate "LTR-501ALS-01 light sensor"
405 depends on I2C
410 If you say yes here you get support for the Lite-On LTR-501ALS-01
411 ambient light and proximity sensor. This driver also supports LTR-559
412 ALS/PS or LTR-301 ALS sensors.
414 This driver can also be built as a module. If so, the module
419 depends on I2C
425 If built as a dynamically linked module, it will be called
430 depends on I2C
432 Say Y here if you want to build support for the On Semiconductor
435 To compile this driver as a module, choose M here:
436 the module will be called lv0104cs.
440 depends on I2C
448 To compile this driver as a module, choose M here:
449 the module will be called max44000.
453 depends on I2C
459 To compile this driver as a module, choose M here:
460 the module will be called max44009.
463 tristate "ON Semiconductor NOA1305 ambient light sensor"
464 depends on I2C
467 Say Y here if you want to build support for the ON Semiconductor
470 To compile this driver as a module, choose M here:
471 The module will be called noa1305.
475 depends on I2C
478 OPT3001 Ambient Light Sensor, OPT3002 Light-to-Digital Sensor.
480 If built as a dynamically linked module, it will be called
485 depends on I2C
491 If built as a dynamically linked module, it will be called
496 depends on I2C
502 This driver can also be built as a module. If so, the module
507 depends on I2C
513 To compile this driver as a module, choose M here: the module will be
518 depends on I2C
526 To compile this driver as a module, choose M here: the module will be
531 depends on I2C
538 Choosing M will build the driver as a module. If so, the module
543 depends on (I2C || SPI)
552 To compile this driver as a module, choose M here: the module
557 depends on ST_UVIS25
562 depends on ST_UVIS25
567 depends on I2C
574 This driver can also be built as a module. If so, the module
578 tristate "TAOS TCS3472 color light-to-digital converter"
579 depends on I2C
584 family of color light-to-digital converters with IR filter.
586 This driver can also be built as a module. If so, the module
591 depends on I2C
596 This driver can also be built as a module. If so, the module
600 tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters"
601 depends on I2C
608 depends on I2C
614 To compile this driver as a module, select M: the
615 module will be called tsl2591.
619 depends on I2C
627 depends on I2C
632 To compile this driver as a module, choose M here: the
633 module will be called tsl4531.
637 depends on I2C
642 This driver can also be built as a module. If so, the module
649 depends on I2C
655 To compile this driver as a module, choose M here: the
656 module will be called vcnl4000.
663 depends on I2C
669 To compile this driver as a module, choose M here: the
670 module will be called vcnl4035.
675 depends on I2C
680 To compile this driver as a module, choose M here: the
681 module will be called veml3235.
686 depends on I2C
691 To compile this driver as a module, choose M here: the
692 module will be called veml6030.
697 depends on I2C
702 To compile this driver as a module, choose M here: the
703 module will be called veml6040.
707 depends on I2C
712 To compile this driver as a module, choose M here: the
713 module will be called veml6070.
718 depends on I2C
723 To compile this driver as a module, choose M here: the
724 module will be called veml6075.
728 depends on I2C
733 To compile this driver as a module, choose M here: the
734 module will be called vl6180.
738 depends on I2C
743 To compile this driver as a module, choose M here: the
744 module will be called zopt2201.