Lines Matching refs:module

22 	  To compile this driver as a module, choose M here: the module
32 To compile this driver as a module, choose M here: the module
42 To compile this driver as a module, choose M here: the module
52 To compile this driver as a module, choose M here: the
53 module will be called ad714x.
62 To compile this driver as a module, choose M here: the
63 module will be called ad714x-i2c.
72 To compile this driver as a module, choose M here: the
73 module will be called ad714x-spi.
80 Say Y to enable support for the haptics module in Arizona CODECs.
82 To compile this driver as a module, choose M here: the
83 module will be called arizona-haptics.
93 To compile this driver as a module, choose M here: the
94 module will be called bma150.
103 To compile this driver as a module, choose M here: the
104 module will be called e3x0_button.
115 To compile this driver as a module, choose M here: the
116 module will be called pcspkr.
127 To compile this driver as a module, choose M here: the module
139 To compile this driver as module, choose M here: the
140 module will be called pm8xxx-vibrator.
150 To compile this driver as a module, choose M here: the
151 module will be called pmic8xxx-pwrkey.
162 To compile this driver as a module, choose M here: the
163 module will be called sparcspkr.
177 To compile this driver as module, choose M here: the
178 module will be called max77693-haptic.
189 To compile this driver as module, choose M here: the
190 module will be called max77843-haptic.
199 To compile this driver as a module, choose M here: the module
211 To compile this driver as module, choose M here: the
212 module will be called max8997-haptic.
221 To compile this driver as a module, choose M here: the module
232 To compile this driver as a module, choose M here: the
233 module will be called mma8450.
242 To compile this driver as a module, choose M here: the
243 module will be called mpu3050.
256 To compile this driver as a module, choose M here: the module will
267 To compile this driver as a module, choose M here: the
268 module will be called gp2ap002a00f.
276 To compile this driver as a module, choose M here: the
277 module will be called gpio-beeper.
290 To compile this driver as a module, choose M here: the
291 module will be called gpio_tilt_polled.
302 To compile this driver as a module, choose M here: the
303 module will be called ixp4xx-beeper.
312 To compile this driver as a module, choose M here: the
313 module will be called cobalt_btns.
328 To compile this driver as a module, choose M here: the module will
338 To compile this driver as a module, choose M here: the module will
353 To compile this driver as a module, choose M here: the module will be
368 To compile this driver as a module, choose M here: the module will
378 To compile this driver as a module, choose M here: the module will
401 To compile this driver as a module, choose M here: the
402 module will be called powermate.
416 To compile this driver as a module, choose M here: the module will be
428 To compile this driver as a module, choose M here: the module will be
440 To compile this driver as a module, choose M here: the
441 module will be called regulator-haptic.
450 To compile this driver as a module, choose M here. The module will
460 To compile this driver as a module, choose M here. The module will
470 To compile this driver as a module, choose M here. The module will
481 To compile this driver as a module, choose M here. The module will
492 To compile this driver as a module, choose M here. The module will
502 To compile this driver as a module, choose M here. The module will
511 To compile this driver as a module, choose M here: the
512 module will be called uinput.
521 To compile this driver as a module, choose M here: the
522 module will be called sgi_btns.
539 To compile this driver as a module, choose M here. The module will
556 To compile this driver as a module, choose M here: the
557 module will be called pcf8574_keypad.
567 To compile this driver as a module, choose M here: the module will be
578 To compile this driver as a module, choose M here: the
579 module will be called rotary_encoder.
590 To compile this driver as a module, choose M here: the
591 module will be called rb532_button.
600 To compile this driver as a module, choose M here: the
601 module will be called da9052_onkey.
610 To compile this driver as a module, choose M here: the module
621 To compile this driver as a module, choose M here: the
622 module will be called dm355evm_keys.
630 To compile this driver as a module, choose M here: the
631 module will be called bfin-rotary.
640 To compile this driver as a module, choose M here: the module
650 To compile this driver as a module, choose M here: the
651 module will be called pcap_keys.
667 To compile this driver as a module, choose M here: the
668 module will be called adxl34x.
677 To compile this driver as a module, choose M here: the
678 module will be called adxl34x-i2c.
687 To compile this driver as a module, choose M here: the
688 module will be called adxl34x-spi.
697 To compile this driver as a module, choose M here: the module will be
711 To compile this driver as a module, choose M here: the
712 module will be called cma3000_d0x.
721 To compile this driver as a module, choose M here: the
722 module will be called cma3000_d0x_i2c.
734 To compile this driver as a module, choose M here: the
735 module will be called xen-kbdfront.
754 To compile this driver as a module, choose M here: the
755 module will be called ideapad_slidebar.
764 To compile this driver as a module, choose M here: the
765 module will be called soc_button_array.
775 To compile this driver as a module, choose M here: the
776 module will be called drv260x-haptics.
786 To compile this driver as a module, choose M here: the
787 module will be called drv260x-haptics.