Kconfig 28 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Input misc drivers configuration
  4. #
  5. menuconfig INPUT_MISC
  6. bool "Miscellaneous devices"
  7. help
  8. Say Y here, and a list of miscellaneous input drivers will be displayed.
  9. Everything that didn't fit into the other categories is here. This option
  10. doesn't affect the kernel.
  11. If unsure, say Y.
  12. if INPUT_MISC
  13. config INPUT_88PM860X_ONKEY
  14. tristate "88PM860x ONKEY support"
  15. depends on MFD_88PM860X
  16. help
  17. Support the ONKEY of Marvell 88PM860x PMICs as an input device
  18. reporting power button status.
  19. To compile this driver as a module, choose M here: the module
  20. will be called 88pm860x_onkey.
  21. config INPUT_88PM80X_ONKEY
  22. tristate "88PM80x ONKEY support"
  23. depends on MFD_88PM800
  24. help
  25. Support the ONKEY of Marvell 88PM80x PMICs as an input device
  26. reporting power button status.
  27. To compile this driver as a module, choose M here: the module
  28. will be called 88pm80x_onkey.
  29. config INPUT_88PM886_ONKEY
  30. tristate "Marvell 88PM886 onkey support"
  31. depends on MFD_88PM886_PMIC
  32. help
  33. Support the onkey of Marvell 88PM886 PMIC as an input device
  34. reporting power button status.
  35. config INPUT_AB8500_PONKEY
  36. tristate "AB8500 Pon (PowerOn) Key"
  37. depends on AB8500_CORE
  38. help
  39. Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
  40. Mix-Sig PMIC.
  41. To compile this driver as a module, choose M here: the module
  42. will be called ab8500-ponkey.
  43. config INPUT_AD714X
  44. tristate "Analog Devices AD714x Capacitance Touch Sensor"
  45. help
  46. Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
  47. You should select a bus connection too.
  48. To compile this driver as a module, choose M here: the
  49. module will be called ad714x.
  50. config INPUT_AD714X_I2C
  51. tristate "support I2C bus connection"
  52. depends on INPUT_AD714X && I2C
  53. default y
  54. help
  55. Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
  56. To compile this driver as a module, choose M here: the
  57. module will be called ad714x-i2c.
  58. config INPUT_AD714X_SPI
  59. tristate "support SPI bus connection"
  60. depends on INPUT_AD714X && SPI
  61. default y
  62. help
  63. Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
  64. To compile this driver as a module, choose M here: the
  65. module will be called ad714x-spi.
  66. config INPUT_ARIEL_PWRBUTTON
  67. tristate "Dell Wyse 3020 Power Button Driver"
  68. depends on SPI
  69. depends on MACH_MMP3_DT || COMPILE_TEST
  70. help
  71. Say Y to enable support for reporting power button status on
  72. on Dell Wyse 3020 ("Ariel") thin client.
  73. To compile this driver as a module, choose M here: the module
  74. will be called ariel-pwrbutton.
  75. config INPUT_ARIZONA_HAPTICS
  76. tristate "Arizona haptics support"
  77. depends on MFD_ARIZONA && SND_SOC
  78. select INPUT_FF_MEMLESS
  79. help
  80. Say Y to enable support for the haptics module in Arizona CODECs.
  81. To compile this driver as a module, choose M here: the
  82. module will be called arizona-haptics.
  83. config INPUT_ATC260X_ONKEY
  84. tristate "Actions Semi ATC260x PMIC ONKEY"
  85. depends on MFD_ATC260X
  86. help
  87. Support the ONKEY of ATC260x PMICs as an input device reporting
  88. power button status. ONKEY can be used to wakeup from low power
  89. modes and force a reset on long press.
  90. To compile this driver as a module, choose M here: the
  91. module will be called atc260x-onkey.
  92. config INPUT_ATMEL_CAPTOUCH
  93. tristate "Atmel Capacitive Touch Button Driver"
  94. depends on OF
  95. depends on I2C
  96. help
  97. Say Y here if an Atmel Capacitive Touch Button device which
  98. implements "captouch" protocol is connected to I2C bus. Typically
  99. this device consists of Atmel Touch sensor controlled by AtMegaXX
  100. MCU running firmware based on Qtouch library.
  101. One should find "atmel,captouch" node in the board specific DTS.
  102. To compile this driver as a module, choose M here: the
  103. module will be called atmel_captouch.
  104. config INPUT_BBNSM_PWRKEY
  105. tristate "NXP BBNSM Power Key Driver"
  106. depends on ARCH_MXC || COMPILE_TEST
  107. depends on OF
  108. help
  109. This is the bbnsm powerkey driver for the NXP i.MX application
  110. processors.
  111. To compile this driver as a module, choose M here; the
  112. module will be called bbnsm_pwrkey.
  113. config INPUT_BMA150
  114. tristate "BMA150/SMB380 acceleration sensor support"
  115. depends on I2C
  116. help
  117. Say Y here if you have Bosch Sensortec's BMA150 or SMB380
  118. acceleration sensor hooked to an I2C bus.
  119. To compile this driver as a module, choose M here: the
  120. module will be called bma150.
  121. config INPUT_CS40L50_VIBRA
  122. tristate "CS40L50 Haptic Driver support"
  123. depends on MFD_CS40L50_CORE
  124. help
  125. Say Y here to enable support for Cirrus Logic's CS40L50
  126. haptic driver.
  127. To compile this driver as a module, choose M here: the
  128. module will be called cs40l50-vibra.
  129. config INPUT_E3X0_BUTTON
  130. tristate "NI Ettus Research USRP E3xx Button support."
  131. default n
  132. help
  133. Say Y here to enable support for the NI Ettus Research
  134. USRP E3xx Button.
  135. To compile this driver as a module, choose M here: the
  136. module will be called e3x0_button.
  137. config INPUT_PCSPKR
  138. tristate "PC Speaker support"
  139. depends on PCSPKR_PLATFORM
  140. help
  141. Say Y here if you want the standard PC Speaker to be used for
  142. bells and whistles.
  143. If unsure, say Y.
  144. To compile this driver as a module, choose M here: the
  145. module will be called pcspkr.
  146. config INPUT_PM8941_PWRKEY
  147. tristate "Qualcomm PM8941 power key support"
  148. depends on MFD_SPMI_PMIC
  149. help
  150. Say Y here if you want support for the power key usually found
  151. on boards using a Qualcomm PM8941 compatible PMIC.
  152. If unsure, say Y.
  153. To compile this driver as a module, choose M here: the module
  154. will be called pm8941-pwrkey.
  155. config INPUT_PM8XXX_VIBRATOR
  156. tristate "Qualcomm PM8XXX vibrator support"
  157. depends on MFD_PM8XXX || MFD_SPMI_PMIC
  158. select INPUT_FF_MEMLESS
  159. help
  160. This option enables device driver support for the vibrator
  161. on Qualcomm PM8xxx chip. This driver supports ff-memless interface
  162. from input framework.
  163. To compile this driver as module, choose M here: the
  164. module will be called pm8xxx-vibrator.
  165. config INPUT_PMIC8XXX_PWRKEY
  166. tristate "PMIC8XXX power key support"
  167. depends on MFD_PM8XXX
  168. help
  169. Say Y here if you want support for the PMIC8XXX power key.
  170. If unsure, say N.
  171. To compile this driver as a module, choose M here: the
  172. module will be called pmic8xxx-pwrkey.
  173. config INPUT_SPARCSPKR
  174. tristate "SPARC Speaker support"
  175. depends on PCI && SPARC64
  176. help
  177. Say Y here if you want the standard Speaker on Sparc PCI systems
  178. to be used for bells and whistles.
  179. If unsure, say Y.
  180. To compile this driver as a module, choose M here: the
  181. module will be called sparcspkr.
  182. config INPUT_M68K_BEEP
  183. tristate "M68k Beeper support"
  184. depends on M68K
  185. config INPUT_MAX77650_ONKEY
  186. tristate "Maxim MAX77650 ONKEY support"
  187. depends on MFD_MAX77650
  188. help
  189. Support the ONKEY of the MAX77650 PMIC as an input device.
  190. To compile this driver as a module, choose M here: the module
  191. will be called max77650-onkey.
  192. config INPUT_MAX77693_HAPTIC
  193. tristate "MAXIM MAX77693/MAX77843 haptic controller support"
  194. depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
  195. select INPUT_FF_MEMLESS
  196. help
  197. This option enables support for the haptic controller on
  198. MAXIM MAX77693 and MAX77843 chips.
  199. To compile this driver as module, choose M here: the
  200. module will be called max77693-haptic.
  201. config INPUT_MAX8925_ONKEY
  202. tristate "MAX8925 ONKEY support"
  203. depends on MFD_MAX8925
  204. help
  205. Support the ONKEY of MAX8925 PMICs as an input device
  206. reporting power button status.
  207. To compile this driver as a module, choose M here: the module
  208. will be called max8925_onkey.
  209. config INPUT_MAX8997_HAPTIC
  210. tristate "MAXIM MAX8997 haptic controller support"
  211. depends on PWM && MFD_MAX8997
  212. select INPUT_FF_MEMLESS
  213. help
  214. This option enables device driver support for the haptic controller
  215. on MAXIM MAX8997 chip. This driver supports ff-memless interface
  216. from input framework.
  217. To compile this driver as module, choose M here: the
  218. module will be called max8997-haptic.
  219. config INPUT_MC13783_PWRBUTTON
  220. tristate "MC13783 ON buttons"
  221. depends on MFD_MC13XXX
  222. help
  223. Support the ON buttons of MC13783 PMIC as an input device
  224. reporting power button status.
  225. To compile this driver as a module, choose M here: the module
  226. will be called mc13783-pwrbutton.
  227. config INPUT_MMA8450
  228. tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
  229. depends on I2C
  230. help
  231. Say Y here if you want to support Freescale's MMA8450 Accelerometer
  232. through I2C interface.
  233. To compile this driver as a module, choose M here: the
  234. module will be called mma8450.
  235. config INPUT_APANEL
  236. tristate "Fujitsu Lifebook Application Panel buttons"
  237. depends on X86 && I2C && LEDS_CLASS
  238. select CHECK_SIGNATURE
  239. help
  240. Say Y here for support of the Application Panel buttons, used on
  241. Fujitsu Lifebook. These are attached to the mainboard through
  242. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  243. which you should also build for this kernel.
  244. To compile this driver as a module, choose M here: the module will
  245. be called apanel.
  246. config INPUT_GPIO_BEEPER
  247. tristate "Generic GPIO Beeper support"
  248. depends on GPIOLIB || COMPILE_TEST
  249. help
  250. Say Y here if you have a beeper connected to a GPIO pin.
  251. To compile this driver as a module, choose M here: the
  252. module will be called gpio-beeper.
  253. config INPUT_GPIO_DECODER
  254. tristate "Polled GPIO Decoder Input driver"
  255. depends on GPIOLIB || COMPILE_TEST
  256. help
  257. Say Y here if you want driver to read status of multiple GPIO
  258. lines and report the encoded value as an absolute integer to
  259. input subsystem.
  260. To compile this driver as a module, choose M here: the module
  261. will be called gpio_decoder.
  262. config INPUT_GPIO_VIBRA
  263. tristate "GPIO vibrator support"
  264. depends on GPIOLIB || COMPILE_TEST
  265. select INPUT_FF_MEMLESS
  266. help
  267. Say Y here to get support for GPIO based vibrator devices.
  268. If unsure, say N.
  269. To compile this driver as a module, choose M here: the module will be
  270. called gpio-vibra.
  271. config INPUT_COBALT_BTNS
  272. tristate "Cobalt button interface"
  273. depends on MIPS_COBALT
  274. help
  275. Say Y here if you want to support MIPS Cobalt button interface.
  276. To compile this driver as a module, choose M here: the
  277. module will be called cobalt_btns.
  278. config INPUT_CPCAP_PWRBUTTON
  279. tristate "CPCAP OnKey"
  280. depends on MFD_CPCAP
  281. help
  282. Say Y here if you want to enable power key reporting via the
  283. Motorola CPCAP chip.
  284. To compile this driver as a module, choose M here. The module will
  285. be called cpcap-pwrbutton.
  286. config INPUT_WISTRON_BTNS
  287. tristate "x86 Wistron laptop button interface"
  288. depends on X86_32 && !UML
  289. select INPUT_SPARSEKMAP
  290. select NEW_LEDS
  291. select LEDS_CLASS
  292. select CHECK_SIGNATURE
  293. help
  294. Say Y here for support of Wistron laptop button interfaces, used on
  295. laptops of various brands, including Acer and Fujitsu-Siemens. If
  296. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  297. To compile this driver as a module, choose M here: the module will
  298. be called wistron_btns.
  299. config INPUT_ATLAS_BTNS
  300. tristate "x86 Atlas button interface"
  301. depends on X86 && ACPI
  302. help
  303. Say Y here for support of Atlas wallmount touchscreen buttons.
  304. The events will show up as scancodes F1 through F9 via evdev.
  305. To compile this driver as a module, choose M here: the module will
  306. be called atlas_btns.
  307. config INPUT_ATI_REMOTE2
  308. tristate "ATI / Philips USB RF remote control"
  309. depends on USB_ARCH_HAS_HCD
  310. select USB
  311. help
  312. Say Y here if you want to use an ATI or Philips USB RF remote control.
  313. These are RF remotes with USB receivers.
  314. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  315. and is also available as a separate product.
  316. This driver provides mouse pointer, left and right mouse buttons,
  317. and maps all the other remote buttons to keypress events.
  318. To compile this driver as a module, choose M here: the module will be
  319. called ati_remote2.
  320. config INPUT_KEYSPAN_REMOTE
  321. tristate "Keyspan DMR USB remote control"
  322. depends on USB_ARCH_HAS_HCD
  323. select USB
  324. help
  325. Say Y here if you want to use a Keyspan DMR USB remote control.
  326. Currently only the UIA-11 type of receiver has been tested. The tag
  327. on the receiver that connects to the USB port should have a P/N that
  328. will tell you what type of DMR you have. The UIA-10 type is not
  329. supported at this time. This driver maps all buttons to keypress
  330. events.
  331. To compile this driver as a module, choose M here: the module will
  332. be called keyspan_remote.
  333. config INPUT_KXTJ9
  334. tristate "Kionix KXTJ9 tri-axis digital accelerometer"
  335. depends on I2C
  336. help
  337. Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
  338. accelerometer.
  339. To compile this driver as a module, choose M here: the module will
  340. be called kxtj9.
  341. config INPUT_POWERMATE
  342. tristate "Griffin PowerMate and Contour Jog support"
  343. depends on USB_ARCH_HAS_HCD
  344. select USB
  345. help
  346. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  347. These are aluminum dials which can measure clockwise and anticlockwise
  348. rotation. The dial also acts as a pushbutton. The base contains an LED
  349. which can be instructed to pulse or to switch to a particular intensity.
  350. You can download userspace tools from
  351. <http://sowerbutts.com/powermate/>.
  352. To compile this driver as a module, choose M here: the
  353. module will be called powermate.
  354. config INPUT_YEALINK
  355. tristate "Yealink usb-p1k voip phone"
  356. depends on USB_ARCH_HAS_HCD
  357. select USB
  358. help
  359. Say Y here if you want to enable keyboard and LCD functions of the
  360. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  361. usb sound driver, so you might want to enable that as well.
  362. For information about how to use these additional functions, see
  363. <file:Documentation/input/devices/yealink.rst>.
  364. To compile this driver as a module, choose M here: the module will be
  365. called yealink.
  366. config INPUT_CM109
  367. tristate "C-Media CM109 USB I/O Controller"
  368. depends on USB_ARCH_HAS_HCD
  369. select USB
  370. help
  371. Say Y here if you want to enable keyboard and buzzer functions of the
  372. C-Media CM109 usb phones. The audio part is enabled by the generic
  373. usb sound driver, so you might want to enable that as well.
  374. To compile this driver as a module, choose M here: the module will be
  375. called cm109.
  376. config INPUT_REGULATOR_HAPTIC
  377. tristate "Regulator haptics support"
  378. depends on REGULATOR
  379. select INPUT_FF_MEMLESS
  380. help
  381. This option enables device driver support for the haptic controlled
  382. by a regulator. This driver supports ff-memless interface
  383. from input framework.
  384. To compile this driver as a module, choose M here: the
  385. module will be called regulator-haptic.
  386. config INPUT_RETU_PWRBUTTON
  387. tristate "Retu Power button Driver"
  388. depends on MFD_RETU
  389. help
  390. Say Y here if you want to enable power key reporting via the
  391. Retu chips found in Nokia Internet Tablets (770, N800, N810).
  392. To compile this driver as a module, choose M here. The module will
  393. be called retu-pwrbutton.
  394. config INPUT_TPS65218_PWRBUTTON
  395. tristate "TPS65218 Power button driver"
  396. depends on (MFD_TPS65217 || MFD_TPS65218)
  397. help
  398. Say Y here if you want to enable power button reporting for
  399. TPS65217 and TPS65218 Power Management IC devices.
  400. To compile this driver as a module, choose M here. The module will
  401. be called tps65218-pwrbutton.
  402. config INPUT_TPS65219_PWRBUTTON
  403. tristate "TPS65219 Power button driver"
  404. depends on MFD_TPS65219
  405. help
  406. Say Y here if you want to enable power button reporting for
  407. TPS65219 Power Management IC devices.
  408. To compile this driver as a module, choose M here. The module will
  409. be called tps65219-pwrbutton.
  410. config INPUT_AXP20X_PEK
  411. tristate "X-Powers AXP20X power button driver"
  412. depends on MFD_AXP20X
  413. help
  414. Say Y here if you want to enable power key reporting via the
  415. AXP20X PMIC.
  416. To compile this driver as a module, choose M here. The module will
  417. be called axp20x-pek.
  418. config INPUT_TWL4030_PWRBUTTON
  419. tristate "TWL4030 Power button Driver"
  420. depends on TWL4030_CORE
  421. help
  422. Say Y here if you want to enable power key reporting via the
  423. TWL4030 family of chips.
  424. To compile this driver as a module, choose M here. The module will
  425. be called twl4030_pwrbutton.
  426. config INPUT_TWL4030_VIBRA
  427. tristate "Support for TWL4030 Vibrator"
  428. depends on TWL4030_CORE
  429. select MFD_TWL4030_AUDIO
  430. select INPUT_FF_MEMLESS
  431. help
  432. This option enables support for TWL4030 Vibrator Driver.
  433. To compile this driver as a module, choose M here. The module will
  434. be called twl4030_vibra.
  435. config INPUT_TWL6040_VIBRA
  436. tristate "Support for TWL6040 Vibrator"
  437. depends on TWL6040_CORE
  438. select INPUT_FF_MEMLESS
  439. help
  440. This option enables support for TWL6040 Vibrator Driver.
  441. To compile this driver as a module, choose M here. The module will
  442. be called twl6040_vibra.
  443. config INPUT_UINPUT
  444. tristate "User level driver support"
  445. help
  446. Say Y here if you want to support user level drivers for input
  447. subsystem accessible under char device 10:223 - /dev/input/uinput.
  448. To compile this driver as a module, choose M here: the
  449. module will be called uinput.
  450. config INPUT_SGI_BTNS
  451. tristate "SGI Indy/O2 volume button interface"
  452. depends on SGI_IP22 || SGI_IP32
  453. help
  454. Say Y here if you want to support SGI Indy/O2 volume button interface.
  455. To compile this driver as a module, choose M here: the
  456. module will be called sgi_btns.
  457. config HP_SDC_RTC
  458. tristate "HP SDC Real Time Clock"
  459. depends on (GSC || HP300) && SERIO
  460. select HP_SDC
  461. help
  462. Say Y here if you want to support the built-in real time clock
  463. of the HP SDC controller.
  464. config INPUT_PALMAS_PWRBUTTON
  465. tristate "Palmas Power button Driver"
  466. depends on MFD_PALMAS
  467. help
  468. Say Y here if you want to enable power key reporting via the
  469. Palmas family of PMICs.
  470. To compile this driver as a module, choose M here. The module will
  471. be called palmas_pwrbutton.
  472. config INPUT_PCF50633_PMU
  473. tristate "PCF50633 PMU events"
  474. depends on MFD_PCF50633
  475. help
  476. Say Y to include support for delivering PMU events via input
  477. layer on NXP PCF50633.
  478. config INPUT_PCF8574
  479. tristate "PCF8574 Keypad input device"
  480. depends on I2C
  481. help
  482. Say Y here if you want to support a keypad connected via I2C
  483. with a PCF8574.
  484. To compile this driver as a module, choose M here: the
  485. module will be called pcf8574_keypad.
  486. config INPUT_PWM_BEEPER
  487. tristate "PWM beeper support"
  488. depends on PWM
  489. help
  490. Say Y here to get support for PWM based beeper devices.
  491. If unsure, say N.
  492. To compile this driver as a module, choose M here: the module will be
  493. called pwm-beeper.
  494. config INPUT_PWM_VIBRA
  495. tristate "PWM vibrator support"
  496. depends on PWM
  497. select INPUT_FF_MEMLESS
  498. help
  499. Say Y here to get support for PWM based vibrator devices.
  500. If unsure, say N.
  501. To compile this driver as a module, choose M here: the module will be
  502. called pwm-vibra.
  503. config INPUT_RK805_PWRKEY
  504. tristate "Rockchip RK805 PMIC power key support"
  505. depends on MFD_RK8XX
  506. help
  507. Select this option to enable power key driver for RK805.
  508. If unsure, say N.
  509. To compile this driver as a module, choose M here: the module will be
  510. called rk805_pwrkey.
  511. config INPUT_GPIO_ROTARY_ENCODER
  512. tristate "Rotary encoders connected to GPIO pins"
  513. depends on GPIOLIB || COMPILE_TEST
  514. help
  515. Say Y here to add support for rotary encoders connected to GPIO lines.
  516. Check file:Documentation/input/devices/rotary-encoder.rst for more
  517. information.
  518. To compile this driver as a module, choose M here: the
  519. module will be called rotary_encoder.
  520. config INPUT_RB532_BUTTON
  521. tristate "Mikrotik Routerboard 532 button interface"
  522. depends on MIKROTIK_RB532
  523. depends on GPIOLIB
  524. help
  525. Say Y here if you want support for the S1 button built into
  526. Mikrotik's Routerboard 532.
  527. To compile this driver as a module, choose M here: the
  528. module will be called rb532_button.
  529. config INPUT_DA7280_HAPTICS
  530. tristate "Dialog Semiconductor DA7280 haptics support"
  531. depends on INPUT && I2C
  532. select REGMAP_I2C
  533. help
  534. Say Y to enable support for the Dialog DA7280 haptics driver.
  535. The haptics can be controlled by PWM or GPIO
  536. with I2C communication.
  537. To compile this driver as a module, choose M here: the
  538. module will be called da7280.
  539. config INPUT_DA9052_ONKEY
  540. tristate "Dialog DA9052/DA9053 Onkey"
  541. depends on PMIC_DA9052
  542. help
  543. Support the ONKEY of Dialog DA9052 PMICs as an input device
  544. reporting power button status.
  545. To compile this driver as a module, choose M here: the
  546. module will be called da9052_onkey.
  547. config INPUT_DA9055_ONKEY
  548. tristate "Dialog Semiconductor DA9055 ONKEY"
  549. depends on MFD_DA9055
  550. help
  551. Support the ONKEY of DA9055 PMICs as an input device
  552. reporting power button status.
  553. To compile this driver as a module, choose M here: the module
  554. will be called da9055_onkey.
  555. config INPUT_DA9063_ONKEY
  556. tristate "Dialog DA9063/62/61 OnKey"
  557. depends on MFD_DA9063 || MFD_DA9062
  558. help
  559. Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
  560. Management ICs as an input device capable of reporting the
  561. power button status.
  562. To compile this driver as a module, choose M here: the module
  563. will be called da9063_onkey.
  564. config INPUT_WM831X_ON
  565. tristate "WM831X ON pin"
  566. depends on MFD_WM831X
  567. help
  568. Support the ON pin of WM831X PMICs as an input device
  569. reporting power button status.
  570. To compile this driver as a module, choose M here: the module
  571. will be called wm831x_on.
  572. config INPUT_PCAP
  573. tristate "Motorola EZX PCAP misc input events"
  574. depends on EZX_PCAP
  575. help
  576. Say Y here if you want to use Power key and Headphone button
  577. on Motorola EZX phones.
  578. To compile this driver as a module, choose M here: the
  579. module will be called pcap_keys.
  580. config INPUT_ADXL34X
  581. tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
  582. default n
  583. help
  584. Say Y here if you have a Accelerometer interface using the
  585. ADXL345/6 controller, and your board-specific initialization
  586. code includes that in its table of devices.
  587. This driver can use either I2C or SPI communication to the
  588. ADXL345/6 controller. Select the appropriate method for
  589. your system.
  590. If unsure, say N (but it's safe to say "Y").
  591. To compile this driver as a module, choose M here: the
  592. module will be called adxl34x.
  593. config INPUT_ADXL34X_I2C
  594. tristate "support I2C bus connection"
  595. depends on INPUT_ADXL34X && I2C
  596. default y
  597. help
  598. Say Y here if you have ADXL345/6 hooked to an I2C bus.
  599. To compile this driver as a module, choose M here: the
  600. module will be called adxl34x-i2c.
  601. config INPUT_ADXL34X_SPI
  602. tristate "support SPI bus connection"
  603. depends on INPUT_ADXL34X && SPI
  604. default y
  605. help
  606. Say Y here if you have ADXL345/6 hooked to a SPI bus.
  607. To compile this driver as a module, choose M here: the
  608. module will be called adxl34x-spi.
  609. config INPUT_IBM_PANEL
  610. tristate "IBM Operation Panel driver"
  611. depends on I2C && I2C_SLAVE
  612. help
  613. Say Y here if you have an IBM Operation Panel connected to your system
  614. over I2C. The panel is typically connected only to a system's service
  615. processor (BMC).
  616. If unsure, say N.
  617. The Operation Panel is a controller with some buttons and an LCD
  618. display that allows someone with physical access to the system to
  619. perform various administrative tasks. This driver only supports the part
  620. of the controller that sends commands to the system.
  621. To compile this driver as a module, choose M here: the module will be
  622. called ibm-panel.
  623. config INPUT_IMS_PCU
  624. tristate "IMS Passenger Control Unit driver"
  625. depends on USB
  626. depends on LEDS_CLASS
  627. help
  628. Say Y here if you have system with IMS Rave Passenger Control Unit.
  629. To compile this driver as a module, choose M here: the module will be
  630. called ims_pcu.
  631. config INPUT_IQS269A
  632. tristate "Azoteq IQS269A capacitive touch controller"
  633. depends on I2C
  634. select REGMAP_I2C
  635. help
  636. Say Y to enable support for the Azoteq IQS269A capacitive
  637. touch controller.
  638. To compile this driver as a module, choose M here: the
  639. module will be called iqs269a.
  640. config INPUT_IQS626A
  641. tristate "Azoteq IQS626A capacitive touch controller"
  642. depends on I2C
  643. select REGMAP_I2C
  644. help
  645. Say Y to enable support for the Azoteq IQS626A capacitive
  646. touch controller.
  647. To compile this driver as a module, choose M here: the
  648. module will be called iqs626a.
  649. config INPUT_IQS7222
  650. tristate "Azoteq IQS7222A/B/C/D capacitive touch controller"
  651. depends on I2C
  652. help
  653. Say Y to enable support for the Azoteq IQS7222A/B/C/D family
  654. of capacitive touch controllers.
  655. To compile this driver as a module, choose M here: the
  656. module will be called iqs7222.
  657. config INPUT_CMA3000
  658. tristate "VTI CMA3000 Tri-axis accelerometer"
  659. help
  660. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  661. driver
  662. This driver currently only supports I2C interface to the
  663. controller. Also select the I2C method.
  664. If unsure, say N
  665. To compile this driver as a module, choose M here: the
  666. module will be called cma3000_d0x.
  667. config INPUT_CMA3000_I2C
  668. tristate "Support I2C bus connection"
  669. depends on INPUT_CMA3000 && I2C
  670. help
  671. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  672. through I2C interface.
  673. To compile this driver as a module, choose M here: the
  674. module will be called cma3000_d0x_i2c.
  675. config INPUT_XEN_KBDDEV_FRONTEND
  676. tristate "Xen virtual keyboard and mouse support"
  677. depends on XEN
  678. default y
  679. select XEN_XENBUS_FRONTEND
  680. help
  681. This driver implements the front-end of the Xen virtual
  682. keyboard and mouse device driver. It communicates with a back-end
  683. in another domain.
  684. To compile this driver as a module, choose M here: the
  685. module will be called xen-kbdfront.
  686. config INPUT_IDEAPAD_SLIDEBAR
  687. tristate "IdeaPad Laptop Slidebar"
  688. depends on INPUT
  689. depends on SERIO_I8042
  690. help
  691. Say Y here if you have an IdeaPad laptop with a slidebar.
  692. To compile this driver as a module, choose M here: the
  693. module will be called ideapad_slidebar.
  694. config INPUT_SOC_BUTTON_ARRAY
  695. tristate "Windows-compatible SoC Button Array"
  696. depends on KEYBOARD_GPIO && ACPI
  697. help
  698. Say Y here if you have a SoC-based tablet that originally runs
  699. Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later.
  700. To compile this driver as a module, choose M here: the
  701. module will be called soc_button_array.
  702. config INPUT_DRV260X_HAPTICS
  703. tristate "TI DRV260X haptics support"
  704. depends on INPUT && I2C
  705. depends on GPIOLIB || COMPILE_TEST
  706. select INPUT_FF_MEMLESS
  707. select REGMAP_I2C
  708. help
  709. Say Y to enable support for the TI DRV260X haptics driver.
  710. To compile this driver as a module, choose M here: the
  711. module will be called drv260x-haptics.
  712. config INPUT_DRV2665_HAPTICS
  713. tristate "TI DRV2665 haptics support"
  714. depends on INPUT && I2C
  715. select INPUT_FF_MEMLESS
  716. select REGMAP_I2C
  717. help
  718. Say Y to enable support for the TI DRV2665 haptics driver.
  719. To compile this driver as a module, choose M here: the
  720. module will be called drv2665-haptics.
  721. config INPUT_DRV2667_HAPTICS
  722. tristate "TI DRV2667 haptics support"
  723. depends on INPUT && I2C
  724. select INPUT_FF_MEMLESS
  725. select REGMAP_I2C
  726. help
  727. Say Y to enable support for the TI DRV2667 haptics driver.
  728. To compile this driver as a module, choose M here: the
  729. module will be called drv2667-haptics.
  730. config INPUT_HISI_POWERKEY
  731. tristate "Hisilicon PMIC ONKEY support"
  732. depends on ARCH_HISI || COMPILE_TEST
  733. help
  734. Say Y to enable support for PMIC ONKEY.
  735. To compile this driver as a module, choose M here: the
  736. module will be called hisi_powerkey.
  737. config INPUT_RAVE_SP_PWRBUTTON
  738. tristate "RAVE SP Power button Driver"
  739. depends on RAVE_SP_CORE
  740. help
  741. Say Y here if you want to enable power key reporting from RAVE SP
  742. To compile this driver as a module, choose M here: the
  743. module will be called rave-sp-pwrbutton.
  744. config INPUT_SC27XX_VIBRA
  745. tristate "Spreadtrum sc27xx vibrator support"
  746. depends on MFD_SC27XX_PMIC || COMPILE_TEST
  747. select INPUT_FF_MEMLESS
  748. help
  749. This option enables support for Spreadtrum sc27xx vibrator driver.
  750. To compile this driver as a module, choose M here. The module will
  751. be called sc27xx_vibra.
  752. config INPUT_RT5120_PWRKEY
  753. tristate "RT5120 PMIC power key support"
  754. depends on MFD_RT5120 || COMPILE_TEST
  755. help
  756. This enables support for RT5120 PMIC power key driver.
  757. To compile this driver as a module, choose M here. the module will
  758. be called rt5120-pwrkey.
  759. config INPUT_STPMIC1_ONKEY
  760. tristate "STPMIC1 PMIC Onkey support"
  761. depends on MFD_STPMIC1
  762. help
  763. Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
  764. can be used to wakeup from low power modes and force a shut-down on
  765. long press.
  766. To compile this driver as a module, choose M here: the
  767. module will be called stpmic1_onkey.
  768. endif