Lines Matching full:be

21 	  be called acpi-als.
32 	  This driver can also be built as a module.  If so, the module
33 	  will be called adjd_s311.
44 	 module will be called adux1020.
54 	  module will be called al3010.
64 	  module will be called al3320a.
74 	  module will be called apds9300.
85 	  If built as a dynamically linked module, it will be called
99 	  module will be called apds9960
114 	 This driver can also be built as a module.  If so, the module
115 	 will be called as73211.
128 	  be called bh1745.
138 	  be called bh1750.
148 	  be called bh1780.
159 	  the module will be called cm32181.
170 	  the module will be called cm3232.
180 	  be called cm3323.
189 	  be called cm3605.
200 	  the module will be called cm36651.
210 	  the module will be called cros_ec_light_prox.
221 	  module will be called gp2ap002.
235 	  module will be called gp2ap020a00f.
245 	  will be called iqs621-als.
277 	  To compile this driver as a module, choose M here: the module will be
289 	  setting which can be configured via sysfs, the default scale is 1000
292 	  To compile this driver as a module, choose M here: the module will be
306 	  module will be called hid-sensor-als.
319 	  module will be called hid-sensor-prox.
330 	  the module will be called jsa1212.
357 	  the module will be called rpr0521.
367 	  The sensor interface can be used to control the LEDs and backlights
372 	  light zone through sysfs. A threshold event can be generated on zone
373 	  changes. The ALS-control output values can be set per zone for the
384 	  This driver can also be built as a module.  If so, the module
385 	  will be called ltr390.
398 	  This driver can also be built as a module.  If so, the module
399 	  will be called ltr501.
409 	  If built as a dynamically linked module, it will be called
420 	  the module will be called lv0104cs.
433 	  the module will be called max44000.
444 	 the module will be called max44009.
455 	 The module will be called noa1305.
464 	  If built as a dynamically linked module, it will be called
475 	  If built as a dynamically linked module, it will be called
488 	  If built as a dynamically linked module, it will be called
499 	  This driver can also be built as a module.  If so, the module
500 	  will be called pa12203001.
510 	  To compile this driver as a module, choose M here: the module will be
523 	  To compile this driver as a module, choose M here: the module will be
536 	  will be called stk3310.
550 	  will be called st_uvis25.
571 	  This driver can also be built as a module.  If so, the module
572 	  will be called tcs3414.
583 	  This driver can also be built as a module.  If so, the module
584 	  will be called tcs3472.
593 	  This driver can also be built as a module.  If so, the module
594 	  will be called tsl2563.
612           module will be called tsl2591.
630 	  module will be called tsl4531.
639 	  This driver can also be built as a module.  If so, the module
640 	  will be called us5182d.
653 	  module will be called vcnl4000.
667 	  module will be called vcnl4035.
679 	  module will be called veml3235.
693 	  module will be called veml6030.
704 	  module will be called veml6040.
714 	  module will be called veml6070.
725 	  module will be called veml6075.
735 	  module will be called vl6180.
745 	  module will be called zopt2201.