Lines Matching full:to
23 To compile this driver as a module, choose M here: the module
33 To compile this driver as a module, choose M here: the module
47 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
50 To compile this driver as a module, choose M here: the module
56 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
60 To compile this driver as a module, choose M here: the
68 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
70 To compile this driver as a module, choose M here: the
78 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
80 To compile this driver as a module, choose M here: the
88 Say Y to enable support for reporting power button status on
91 To compile this driver as a module, choose M here: the module
99 Say Y to enable support for the haptics module in Arizona CODECs.
101 To compile this driver as a module, choose M here: the
109 power button status. ONKEY can be used to wakeup from low power
112 To compile this driver as a module, choose M here: the
121 implements "captouch" protocol is connected to I2C bus. Typically
126 To compile this driver as a module, choose M here: the
137 To compile this driver as a module, choose M here; the
145 acceleration sensor hooked to an I2C bus.
147 To compile this driver as a module, choose M here: the
154 Say Y here to enable support for Cirrus Logic's CS40L50
157 To compile this driver as a module, choose M here: the
164 Say Y here to enable support for the NI Ettus Research
167 To compile this driver as a module, choose M here: the
174 Say Y here if you want the standard PC Speaker to be used for
179 To compile this driver as a module, choose M here: the
191 To compile this driver as a module, choose M here: the module
203 To compile this driver as module, choose M here: the
214 To compile this driver as a module, choose M here: the
222 to be used for bells and whistles.
226 To compile this driver as a module, choose M here: the
239 To compile this driver as a module, choose M here: the module
250 To compile this driver as module, choose M here: the
260 To compile this driver as a module, choose M here: the module
272 To compile this driver as module, choose M here: the
282 To compile this driver as a module, choose M here: the module
289 Say Y here if you want to support Freescale's MMA8450 Accelerometer
292 To compile this driver as a module, choose M here: the
301 Fujitsu Lifebook. These are attached to the mainboard through
305 To compile this driver as a module, choose M here: the module will
312 Say Y here if you have a beeper connected to a GPIO pin.
314 To compile this driver as a module, choose M here: the
321 Say Y here if you want driver to read status of multiple GPIO
322 lines and report the encoded value as an absolute integer to
325 To compile this driver as a module, choose M here: the module
333 Say Y here to get support for GPIO based vibrator devices.
337 To compile this driver as a module, choose M here: the module will be
344 Say Y here if you want to support MIPS Cobalt button interface.
346 To compile this driver as a module, choose M here: the
353 Say Y here if you want to enable power key reporting via the
356 To compile this driver as a module, choose M here. The module will
371 To compile this driver as a module, choose M here: the module will
381 To compile this driver as a module, choose M here: the module will
389 Say Y here if you want to use an ATI or Philips USB RF remote control.
394 and maps all the other remote buttons to keypress events.
396 To compile this driver as a module, choose M here: the module will be
404 Say Y here if you want to use a Keyspan DMR USB remote control.
406 on the receiver that connects to the USB port should have a P/N that
408 supported at this time. This driver maps all buttons to keypress
411 To compile this driver as a module, choose M here: the module will
418 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
421 To compile this driver as a module, choose M here: the module will
429 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
432 which can be instructed to pulse or to switch to a particular intensity.
437 To compile this driver as a module, choose M here: the
445 Say Y here if you want to enable keyboard and LCD functions of the
447 usb sound driver, so you might want to enable that as well.
449 For information about how to use these additional functions, see
452 To compile this driver as a module, choose M here: the module will be
460 Say Y here if you want to enable keyboard and buzzer functions of the
462 usb sound driver, so you might want to enable that as well.
464 To compile this driver as a module, choose M here: the module will be
476 To compile this driver as a module, choose M here: the
483 Say Y here if you want to enable power key reporting via the
486 To compile this driver as a module, choose M here. The module will
493 Say Y here if you want to enable power button reporting for
496 To compile this driver as a module, choose M here. The module will
503 Say Y here if you want to enable power button reporting for
506 To compile this driver as a module, choose M here. The module will
513 Say Y here if you want to enable power key reporting via the
516 To compile this driver as a module, choose M here. The module will
524 Say Y here if you want to enable power key reporting via the
527 To compile this driver as a module, choose M here. The module will
538 To compile this driver as a module, choose M here. The module will
548 To compile this driver as a module, choose M here. The module will
554 Say Y here if you want to support user level drivers for input
557 To compile this driver as a module, choose M here: the
564 Say Y here if you want to support SGI Indy/O2 volume button interface.
566 To compile this driver as a module, choose M here: the
574 Say Y here if you want to support the built-in real time clock
581 Say Y here if you want to enable power key reporting via the
584 To compile this driver as a module, choose M here. The module will
591 Say Y to include support for delivering PMU events via input
598 Say Y here if you want to support a keypad connected via I2C
601 To compile this driver as a module, choose M here: the
608 Say Y here to get support for PWM based beeper devices.
612 To compile this driver as a module, choose M here: the module will be
620 Say Y here to get support for PWM based vibrator devices.
624 To compile this driver as a module, choose M here: the module will be
631 Select this option to enable power key driver for RK805.
635 To compile this driver as a module, choose M here: the module will be
639 tristate "Rotary encoders connected to GPIO pins"
642 Say Y here to add support for rotary encoders connected to GPIO lines.
646 To compile this driver as a module, choose M here: the
657 To compile this driver as a module, choose M here: the
665 Say Y to enable support for the Dialog DA7280 haptics driver.
669 To compile this driver as a module, choose M here: the
679 To compile this driver as a module, choose M here: the
689 To compile this driver as a module, choose M here: the module
700 To compile this driver as a module, choose M here: the module
710 To compile this driver as a module, choose M here: the module
717 Say Y here if you want to use Power key and Headphone button
720 To compile this driver as a module, choose M here: the
731 This driver can use either I2C or SPI communication to the
735 If unsure, say N (but it's safe to say "Y").
737 To compile this driver as a module, choose M here: the
745 Say Y here if you have ADXL345/6 hooked to an I2C bus.
747 To compile this driver as a module, choose M here: the
755 Say Y here if you have ADXL345/6 hooked to a SPI bus.
757 To compile this driver as a module, choose M here: the
764 Say Y here if you have an IBM Operation Panel connected to your system
765 over I2C. The panel is typically connected only to a system's service
771 display that allows someone with physical access to the system to
773 of the controller that sends commands to the system.
775 To compile this driver as a module, choose M here: the module will be
785 To compile this driver as a module, choose M here: the module will be
793 Say Y to enable support for the Azoteq IQS269A capacitive
796 To compile this driver as a module, choose M here: the
804 Say Y to enable support for the Azoteq IQS626A capacitive
807 To compile this driver as a module, choose M here: the
814 Say Y to enable support for the Azoteq IQS7222A/B/C/D family
817 To compile this driver as a module, choose M here: the
823 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
826 This driver currently only supports I2C interface to the
831 To compile this driver as a module, choose M here: the
838 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
841 To compile this driver as a module, choose M here: the
854 To compile this driver as a module, choose M here: the
864 To compile this driver as a module, choose M here: the
874 To compile this driver as a module, choose M here: the
884 Say Y to enable support for the TI DRV260X haptics driver.
886 To compile this driver as a module, choose M here: the
895 Say Y to enable support for the TI DRV2665 haptics driver.
897 To compile this driver as a module, choose M here: the
906 Say Y to enable support for the TI DRV2667 haptics driver.
908 To compile this driver as a module, choose M here: the
915 Say Y to enable support for PMIC ONKEY.
917 To compile this driver as a module, choose M here: the
929 To compile this driver as a module, choose M here: the
936 Say Y here if you want to enable power key reporting from RAVE SP
938 To compile this driver as a module, choose M here: the
948 To compile this driver as a module, choose M here. The module will
957 To compile this driver as a module, choose M here. the module will
964 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
965 can be used to wakeup from low power modes and force a shut-down on
968 To compile this driver as a module, choose M here: the