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
40 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
43 To compile this driver as a module, choose M here: the module
49 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
53 To compile this driver as a module, choose M here: the
61 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
63 To compile this driver as a module, choose M here: the
71 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
73 To compile this driver as a module, choose M here: the
81 Say Y to enable support for reporting power button status on
84 To compile this driver as a module, choose M here: the module
92 Say Y to enable support for the haptics module in Arizona CODECs.
94 To compile this driver as a module, choose M here: the
102 power button status. ONKEY can be used to wakeup from low power
105 To compile this driver as a module, choose M here: the
114 implements "captouch" protocol is connected to I2C bus. Typically
119 To compile this driver as a module, choose M here: the
130 To compile this driver as a module, choose M here; the
138 acceleration sensor hooked to an I2C bus.
140 To compile this driver as a module, choose M here: the
147 Say Y here to enable support for the NI Ettus Research
150 To compile this driver as a module, choose M here: the
157 Say Y here if you want the standard PC Speaker to be used for
162 To compile this driver as a module, choose M here: the
174 To compile this driver as a module, choose M here: the module
186 To compile this driver as module, choose M here: the
197 To compile this driver as a module, choose M here: the
205 to be used for bells and whistles.
209 To compile this driver as a module, choose M here: the
222 To compile this driver as a module, choose M here: the module
233 To compile this driver as module, choose M here: the
243 To compile this driver as a module, choose M here: the module
255 To compile this driver as module, choose M here: the
265 To compile this driver as a module, choose M here: the module
272 Say Y here if you want to support Freescale's MMA8450 Accelerometer
275 To compile this driver as a module, choose M here: the
284 Fujitsu Lifebook. These are attached to the mainboard through
288 To compile this driver as a module, choose M here: the module will
295 Say Y here if you have a beeper connected to a GPIO pin.
297 To compile this driver as a module, choose M here: the
304 Say Y here if you want driver to read status of multiple GPIO
305 lines and report the encoded value as an absolute integer to
308 To compile this driver as a module, choose M here: the module
316 Say Y here to get support for GPIO based vibrator devices.
320 To compile this driver as a module, choose M here: the module will be
327 Say Y here if you want to support MIPS Cobalt button interface.
329 To compile this driver as a module, choose M here: the
336 Say Y here if you want to enable power key reporting via the
339 To compile this driver as a module, choose M here. The module will
354 To compile this driver as a module, choose M here: the module will
364 To compile this driver as a module, choose M here: the module will
372 Say Y here if you want to use an ATI or Philips USB RF remote control.
377 and maps all the other remote buttons to keypress events.
379 To compile this driver as a module, choose M here: the module will be
387 Say Y here if you want to use a Keyspan DMR USB remote control.
389 on the receiver that connects to the USB port should have a P/N that
391 supported at this time. This driver maps all buttons to keypress
394 To compile this driver as a module, choose M here: the module will
401 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
404 To compile this driver as a module, choose M here: the module will
412 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
415 which can be instructed to pulse or to switch to a particular intensity.
420 To compile this driver as a module, choose M here: the
428 Say Y here if you want to enable keyboard and LCD functions of the
430 usb sound driver, so you might want to enable that as well.
432 For information about how to use these additional functions, see
435 To compile this driver as a module, choose M here: the module will be
443 Say Y here if you want to enable keyboard and buzzer functions of the
445 usb sound driver, so you might want to enable that as well.
447 To compile this driver as a module, choose M here: the module will be
459 To compile this driver as a module, choose M here: the
466 Say Y here if you want to enable power key reporting via the
469 To compile this driver as a module, choose M here. The module will
476 Say Y here if you want to enable power button reporting for
479 To compile this driver as a module, choose M here. The module will
486 Say Y here if you want to enable power button reporting for
489 To compile this driver as a module, choose M here. The module will
496 Say Y here if you want to enable power key reporting via the
499 To compile this driver as a module, choose M here. The module will
507 Say Y here if you want to enable power key reporting via the
510 To compile this driver as a module, choose M here. The module will
521 To compile this driver as a module, choose M here. The module will
531 To compile this driver as a module, choose M here. The module will
537 Say Y here if you want to support user level drivers for input
540 To compile this driver as a module, choose M here: the
547 Say Y here if you want to support SGI Indy/O2 volume button interface.
549 To compile this driver as a module, choose M here: the
557 Say Y here if you want to support the built-in real time clock
564 Say Y here if you want to enable power key reporting via the
567 To compile this driver as a module, choose M here. The module will
574 Say Y to include support for delivering PMU events via input
581 Say Y here if you want to support a keypad connected via I2C
584 To compile this driver as a module, choose M here: the
591 Say Y here to get support for PWM based beeper devices.
595 To compile this driver as a module, choose M here: the module will be
603 Say Y here to get support for PWM based vibrator devices.
607 To compile this driver as a module, choose M here: the module will be
614 Select this option to enable power key driver for RK805.
618 To compile this driver as a module, choose M here: the module will be
622 tristate "Rotary encoders connected to GPIO pins"
625 Say Y here to add support for rotary encoders connected to GPIO lines.
629 To compile this driver as a module, choose M here: the
640 To compile this driver as a module, choose M here: the
648 Say Y to enable support for the Dialog DA7280 haptics driver.
652 To compile this driver as a module, choose M here: the
662 To compile this driver as a module, choose M here: the
672 To compile this driver as a module, choose M here: the module
683 To compile this driver as a module, choose M here: the module
693 To compile this driver as a module, choose M here: the module
700 Say Y here if you want to use Power key and Headphone button
703 To compile this driver as a module, choose M here: the
714 This driver can use either I2C or SPI communication to the
718 If unsure, say N (but it's safe to say "Y").
720 To compile this driver as a module, choose M here: the
728 Say Y here if you have ADXL345/6 hooked to an I2C bus.
730 To compile this driver as a module, choose M here: the
738 Say Y here if you have ADXL345/6 hooked to a SPI bus.
740 To compile this driver as a module, choose M here: the
747 Say Y here if you have an IBM Operation Panel connected to your system
748 over I2C. The panel is typically connected only to a system's service
754 display that allows someone with physical access to the system to
756 of the controller that sends commands to the system.
758 To compile this driver as a module, choose M here: the module will be
768 To compile this driver as a module, choose M here: the module will be
776 Say Y to enable support for the Azoteq IQS269A capacitive
779 To compile this driver as a module, choose M here: the
787 Say Y to enable support for the Azoteq IQS626A capacitive
790 To compile this driver as a module, choose M here: the
797 Say Y to enable support for the Azoteq IQS7222A/B/C/D family
800 To compile this driver as a module, choose M here: the
806 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
809 This driver currently only supports I2C interface to the
814 To compile this driver as a module, choose M here: the
821 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
824 To compile this driver as a module, choose M here: the
837 To compile this driver as a module, choose M here: the
847 To compile this driver as a module, choose M here: the
857 To compile this driver as a module, choose M here: the
867 Say Y to enable support for the TI DRV260X haptics driver.
869 To compile this driver as a module, choose M here: the
878 Say Y to enable support for the TI DRV2665 haptics driver.
880 To compile this driver as a module, choose M here: the
889 Say Y to enable support for the TI DRV2667 haptics driver.
891 To compile this driver as a module, choose M here: the
898 Say Y to enable support for PMIC ONKEY.
900 To compile this driver as a module, choose M here: the
907 Say Y here if you want to enable power key reporting from RAVE SP
909 To compile this driver as a module, choose M here: the
919 To compile this driver as a module, choose M here. The module will
928 To compile this driver as a module, choose M here. the module will
935 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
936 can be used to wakeup from low power modes and force a shut-down on
939 To compile this driver as a module, choose M here: the