Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679
  1. #
  2. # Input misc drivers configuration
  3. #
  4. menuconfig INPUT_MISC
  5. bool "Miscellaneous devices"
  6. help
  7. Say Y here, and a list of miscellaneous input drivers will be displayed.
  8. Everything that didn't fit into the other categories is here. This option
  9. doesn't affect the kernel.
  10. If unsure, say Y.
  11. if INPUT_MISC
  12. config INPUT_88PM860X_ONKEY
  13. tristate "88PM860x ONKEY support"
  14. depends on MFD_88PM860X
  15. help
  16. Support the ONKEY of Marvell 88PM860x PMICs as an input device
  17. reporting power button status.
  18. To compile this driver as a module, choose M here: the module
  19. will be called 88pm860x_onkey.
  20. config INPUT_88PM80X_ONKEY
  21. tristate "88PM80x ONKEY support"
  22. depends on MFD_88PM800
  23. help
  24. Support the ONKEY of Marvell 88PM80x PMICs as an input device
  25. reporting power button status.
  26. To compile this driver as a module, choose M here: the module
  27. will be called 88pm80x_onkey.
  28. config INPUT_AB8500_PONKEY
  29. tristate "AB8500 Pon (PowerOn) Key"
  30. depends on AB8500_CORE
  31. help
  32. Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
  33. Mix-Sig PMIC.
  34. To compile this driver as a module, choose M here: the module
  35. will be called ab8500-ponkey.
  36. config INPUT_AD714X
  37. tristate "Analog Devices AD714x Capacitance Touch Sensor"
  38. help
  39. Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
  40. You should select a bus connection too.
  41. To compile this driver as a module, choose M here: the
  42. module will be called ad714x.
  43. config INPUT_AD714X_I2C
  44. tristate "support I2C bus connection"
  45. depends on INPUT_AD714X && I2C
  46. default y
  47. help
  48. Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
  49. To compile this driver as a module, choose M here: the
  50. module will be called ad714x-i2c.
  51. config INPUT_AD714X_SPI
  52. tristate "support SPI bus connection"
  53. depends on INPUT_AD714X && SPI
  54. default y
  55. help
  56. Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
  57. To compile this driver as a module, choose M here: the
  58. module will be called ad714x-spi.
  59. config INPUT_ARIZONA_HAPTICS
  60. tristate "Arizona haptics support"
  61. depends on MFD_ARIZONA && SND_SOC
  62. select INPUT_FF_MEMLESS
  63. help
  64. Say Y to enable support for the haptics module in Arizona CODECs.
  65. To compile this driver as a module, choose M here: the
  66. module will be called arizona-haptics.
  67. config INPUT_BMA150
  68. tristate "BMA150/SMB380 acceleration sensor support"
  69. depends on I2C
  70. select INPUT_POLLDEV
  71. help
  72. Say Y here if you have Bosch Sensortec's BMA150 or SMB380
  73. acceleration sensor hooked to an I2C bus.
  74. To compile this driver as a module, choose M here: the
  75. module will be called bma150.
  76. config INPUT_PCSPKR
  77. tristate "PC Speaker support"
  78. depends on PCSPKR_PLATFORM
  79. help
  80. Say Y here if you want the standard PC Speaker to be used for
  81. bells and whistles.
  82. If unsure, say Y.
  83. To compile this driver as a module, choose M here: the
  84. module will be called pcspkr.
  85. config INPUT_PM8XXX_VIBRATOR
  86. tristate "Qualcomm PM8XXX vibrator support"
  87. depends on MFD_PM8XXX
  88. select INPUT_FF_MEMLESS
  89. help
  90. This option enables device driver support for the vibrator
  91. on Qualcomm PM8xxx chip. This driver supports ff-memless interface
  92. from input framework.
  93. To compile this driver as module, choose M here: the
  94. module will be called pm8xxx-vibrator.
  95. config INPUT_PMIC8XXX_PWRKEY
  96. tristate "PMIC8XXX power key support"
  97. depends on MFD_PM8XXX
  98. help
  99. Say Y here if you want support for the PMIC8XXX power key.
  100. If unsure, say N.
  101. To compile this driver as a module, choose M here: the
  102. module will be called pmic8xxx-pwrkey.
  103. config INPUT_SPARCSPKR
  104. tristate "SPARC Speaker support"
  105. depends on PCI && SPARC64
  106. help
  107. Say Y here if you want the standard Speaker on Sparc PCI systems
  108. to be used for bells and whistles.
  109. If unsure, say Y.
  110. To compile this driver as a module, choose M here: the
  111. module will be called sparcspkr.
  112. config INPUT_M68K_BEEP
  113. tristate "M68k Beeper support"
  114. depends on M68K
  115. config INPUT_MAX8925_ONKEY
  116. tristate "MAX8925 ONKEY support"
  117. depends on MFD_MAX8925
  118. help
  119. Support the ONKEY of MAX8925 PMICs as an input device
  120. reporting power button status.
  121. To compile this driver as a module, choose M here: the module
  122. will be called max8925_onkey.
  123. config INPUT_MAX8997_HAPTIC
  124. tristate "MAXIM MAX8997 haptic controller support"
  125. depends on PWM && MFD_MAX8997
  126. select INPUT_FF_MEMLESS
  127. help
  128. This option enables device driver support for the haptic controller
  129. on MAXIM MAX8997 chip. This driver supports ff-memless interface
  130. from input framework.
  131. To compile this driver as module, choose M here: the
  132. module will be called max8997-haptic.
  133. config INPUT_MC13783_PWRBUTTON
  134. tristate "MC13783 ON buttons"
  135. depends on MFD_MC13XXX
  136. help
  137. Support the ON buttons of MC13783 PMIC as an input device
  138. reporting power button status.
  139. To compile this driver as a module, choose M here: the module
  140. will be called mc13783-pwrbutton.
  141. config INPUT_MMA8450
  142. tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
  143. depends on I2C
  144. select INPUT_POLLDEV
  145. help
  146. Say Y here if you want to support Freescale's MMA8450 Accelerometer
  147. through I2C interface.
  148. To compile this driver as a module, choose M here: the
  149. module will be called mma8450.
  150. config INPUT_MPU3050
  151. tristate "MPU3050 Triaxial gyroscope sensor"
  152. depends on I2C
  153. help
  154. Say Y here if you want to support InvenSense MPU3050
  155. connected via an I2C bus.
  156. To compile this driver as a module, choose M here: the
  157. module will be called mpu3050.
  158. config INPUT_APANEL
  159. tristate "Fujitsu Lifebook Application Panel buttons"
  160. depends on X86 && I2C && LEDS_CLASS
  161. select INPUT_POLLDEV
  162. select CHECK_SIGNATURE
  163. help
  164. Say Y here for support of the Application Panel buttons, used on
  165. Fujitsu Lifebook. These are attached to the mainboard through
  166. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  167. which you should also build for this kernel.
  168. To compile this driver as a module, choose M here: the module will
  169. be called apanel.
  170. config INPUT_GP2A
  171. tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
  172. depends on I2C
  173. depends on GPIOLIB
  174. help
  175. Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
  176. hooked to an I2C bus.
  177. To compile this driver as a module, choose M here: the
  178. module will be called gp2ap002a00f.
  179. config INPUT_GPIO_BEEPER
  180. tristate "Generic GPIO Beeper support"
  181. depends on GPIOLIB
  182. help
  183. Say Y here if you have a beeper connected to a GPIO pin.
  184. To compile this driver as a module, choose M here: the
  185. module will be called gpio-beeper.
  186. config INPUT_GPIO_TILT_POLLED
  187. tristate "Polled GPIO tilt switch"
  188. depends on GPIOLIB
  189. select INPUT_POLLDEV
  190. help
  191. This driver implements support for tilt switches connected
  192. to GPIO pins that are not capable of generating interrupts.
  193. The list of gpios to use and the mapping of their states
  194. to specific angles is done via platform data.
  195. To compile this driver as a module, choose M here: the
  196. module will be called gpio_tilt_polled.
  197. config INPUT_IXP4XX_BEEPER
  198. tristate "IXP4XX Beeper support"
  199. depends on ARCH_IXP4XX
  200. help
  201. If you say yes here, you can connect a beeper to the
  202. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  203. If unsure, say Y.
  204. To compile this driver as a module, choose M here: the
  205. module will be called ixp4xx-beeper.
  206. config INPUT_COBALT_BTNS
  207. tristate "Cobalt button interface"
  208. depends on MIPS_COBALT
  209. select INPUT_POLLDEV
  210. help
  211. Say Y here if you want to support MIPS Cobalt button interface.
  212. To compile this driver as a module, choose M here: the
  213. module will be called cobalt_btns.
  214. config INPUT_WISTRON_BTNS
  215. tristate "x86 Wistron laptop button interface"
  216. depends on X86_32
  217. select INPUT_POLLDEV
  218. select INPUT_SPARSEKMAP
  219. select NEW_LEDS
  220. select LEDS_CLASS
  221. select CHECK_SIGNATURE
  222. help
  223. Say Y here for support of Wistron laptop button interfaces, used on
  224. laptops of various brands, including Acer and Fujitsu-Siemens. If
  225. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  226. To compile this driver as a module, choose M here: the module will
  227. be called wistron_btns.
  228. config INPUT_ATLAS_BTNS
  229. tristate "x86 Atlas button interface"
  230. depends on X86 && ACPI
  231. help
  232. Say Y here for support of Atlas wallmount touchscreen buttons.
  233. The events will show up as scancodes F1 through F9 via evdev.
  234. To compile this driver as a module, choose M here: the module will
  235. be called atlas_btns.
  236. config INPUT_ATI_REMOTE2
  237. tristate "ATI / Philips USB RF remote control"
  238. depends on USB_ARCH_HAS_HCD
  239. select USB
  240. help
  241. Say Y here if you want to use an ATI or Philips USB RF remote control.
  242. These are RF remotes with USB receivers.
  243. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  244. and is also available as a separate product.
  245. This driver provides mouse pointer, left and right mouse buttons,
  246. and maps all the other remote buttons to keypress events.
  247. To compile this driver as a module, choose M here: the module will be
  248. called ati_remote2.
  249. config INPUT_KEYSPAN_REMOTE
  250. tristate "Keyspan DMR USB remote control"
  251. depends on USB_ARCH_HAS_HCD
  252. select USB
  253. help
  254. Say Y here if you want to use a Keyspan DMR USB remote control.
  255. Currently only the UIA-11 type of receiver has been tested. The tag
  256. on the receiver that connects to the USB port should have a P/N that
  257. will tell you what type of DMR you have. The UIA-10 type is not
  258. supported at this time. This driver maps all buttons to keypress
  259. events.
  260. To compile this driver as a module, choose M here: the module will
  261. be called keyspan_remote.
  262. config INPUT_KXTJ9
  263. tristate "Kionix KXTJ9 tri-axis digital accelerometer"
  264. depends on I2C
  265. help
  266. Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
  267. accelerometer.
  268. To compile this driver as a module, choose M here: the module will
  269. be called kxtj9.
  270. config INPUT_KXTJ9_POLLED_MODE
  271. bool "Enable polling mode support"
  272. depends on INPUT_KXTJ9
  273. select INPUT_POLLDEV
  274. help
  275. Say Y here if you need accelerometer to work in polling mode.
  276. config INPUT_POWERMATE
  277. tristate "Griffin PowerMate and Contour Jog support"
  278. depends on USB_ARCH_HAS_HCD
  279. select USB
  280. help
  281. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  282. These are aluminum dials which can measure clockwise and anticlockwise
  283. rotation. The dial also acts as a pushbutton. The base contains an LED
  284. which can be instructed to pulse or to switch to a particular intensity.
  285. You can download userspace tools from
  286. <http://sowerbutts.com/powermate/>.
  287. To compile this driver as a module, choose M here: the
  288. module will be called powermate.
  289. config INPUT_YEALINK
  290. tristate "Yealink usb-p1k voip phone"
  291. depends on USB_ARCH_HAS_HCD
  292. select USB
  293. help
  294. Say Y here if you want to enable keyboard and LCD functions of the
  295. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  296. usb sound driver, so you might want to enable that as well.
  297. For information about how to use these additional functions, see
  298. <file:Documentation/input/yealink.txt>.
  299. To compile this driver as a module, choose M here: the module will be
  300. called yealink.
  301. config INPUT_CM109
  302. tristate "C-Media CM109 USB I/O Controller"
  303. depends on USB_ARCH_HAS_HCD
  304. select USB
  305. help
  306. Say Y here if you want to enable keyboard and buzzer functions of the
  307. C-Media CM109 usb phones. The audio part is enabled by the generic
  308. usb sound driver, so you might want to enable that as well.
  309. To compile this driver as a module, choose M here: the module will be
  310. called cm109.
  311. config INPUT_RETU_PWRBUTTON
  312. tristate "Retu Power button Driver"
  313. depends on MFD_RETU
  314. help
  315. Say Y here if you want to enable power key reporting via the
  316. Retu chips found in Nokia Internet Tablets (770, N800, N810).
  317. To compile this driver as a module, choose M here. The module will
  318. be called retu-pwrbutton.
  319. config INPUT_TWL4030_PWRBUTTON
  320. tristate "TWL4030 Power button Driver"
  321. depends on TWL4030_CORE
  322. help
  323. Say Y here if you want to enable power key reporting via the
  324. TWL4030 family of chips.
  325. To compile this driver as a module, choose M here. The module will
  326. be called twl4030_pwrbutton.
  327. config INPUT_TWL4030_VIBRA
  328. tristate "Support for TWL4030 Vibrator"
  329. depends on TWL4030_CORE
  330. select MFD_TWL4030_AUDIO
  331. select INPUT_FF_MEMLESS
  332. help
  333. This option enables support for TWL4030 Vibrator Driver.
  334. To compile this driver as a module, choose M here. The module will
  335. be called twl4030_vibra.
  336. config INPUT_TWL6040_VIBRA
  337. tristate "Support for TWL6040 Vibrator"
  338. depends on TWL6040_CORE
  339. select INPUT_FF_MEMLESS
  340. help
  341. This option enables support for TWL6040 Vibrator Driver.
  342. To compile this driver as a module, choose M here. The module will
  343. be called twl6040_vibra.
  344. config INPUT_UINPUT
  345. tristate "User level driver support"
  346. help
  347. Say Y here if you want to support user level drivers for input
  348. subsystem accessible under char device 10:223 - /dev/input/uinput.
  349. To compile this driver as a module, choose M here: the
  350. module will be called uinput.
  351. config INPUT_SGI_BTNS
  352. tristate "SGI Indy/O2 volume button interface"
  353. depends on SGI_IP22 || SGI_IP32
  354. select INPUT_POLLDEV
  355. help
  356. Say Y here if you want to support SGI Indy/O2 volume button interface.
  357. To compile this driver as a module, choose M here: the
  358. module will be called sgi_btns.
  359. config HP_SDC_RTC
  360. tristate "HP SDC Real Time Clock"
  361. depends on (GSC || HP300) && SERIO
  362. select HP_SDC
  363. help
  364. Say Y here if you want to support the built-in real time clock
  365. of the HP SDC controller.
  366. config INPUT_PCF50633_PMU
  367. tristate "PCF50633 PMU events"
  368. depends on MFD_PCF50633
  369. help
  370. Say Y to include support for delivering PMU events via input
  371. layer on NXP PCF50633.
  372. config INPUT_PCF8574
  373. tristate "PCF8574 Keypad input device"
  374. depends on I2C
  375. help
  376. Say Y here if you want to support a keypad connected via I2C
  377. with a PCF8574.
  378. To compile this driver as a module, choose M here: the
  379. module will be called pcf8574_keypad.
  380. config INPUT_PWM_BEEPER
  381. tristate "PWM beeper support"
  382. depends on PWM
  383. help
  384. Say Y here to get support for PWM based beeper devices.
  385. If unsure, say N.
  386. To compile this driver as a module, choose M here: the module will be
  387. called pwm-beeper.
  388. config INPUT_GPIO_ROTARY_ENCODER
  389. tristate "Rotary encoders connected to GPIO pins"
  390. depends on GPIOLIB
  391. help
  392. Say Y here to add support for rotary encoders connected to GPIO lines.
  393. Check file:Documentation/input/rotary-encoder.txt for more
  394. information.
  395. To compile this driver as a module, choose M here: the
  396. module will be called rotary_encoder.
  397. config INPUT_RB532_BUTTON
  398. tristate "Mikrotik Routerboard 532 button interface"
  399. depends on MIKROTIK_RB532
  400. depends on GPIOLIB
  401. select INPUT_POLLDEV
  402. help
  403. Say Y here if you want support for the S1 button built into
  404. Mikrotik's Routerboard 532.
  405. To compile this driver as a module, choose M here: the
  406. module will be called rb532_button.
  407. config INPUT_DA9052_ONKEY
  408. tristate "Dialog DA9052/DA9053 Onkey"
  409. depends on PMIC_DA9052
  410. help
  411. Support the ONKEY of Dialog DA9052 PMICs as an input device
  412. reporting power button status.
  413. To compile this driver as a module, choose M here: the
  414. module will be called da9052_onkey.
  415. config INPUT_DA9055_ONKEY
  416. tristate "Dialog Semiconductor DA9055 ONKEY"
  417. depends on MFD_DA9055
  418. help
  419. Support the ONKEY of DA9055 PMICs as an input device
  420. reporting power button status.
  421. To compile this driver as a module, choose M here: the module
  422. will be called da9055_onkey.
  423. config INPUT_DM355EVM
  424. tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
  425. depends on MFD_DM355EVM_MSP
  426. select INPUT_SPARSEKMAP
  427. help
  428. Supports the pushbuttons and IR remote used with
  429. the DM355 EVM board.
  430. To compile this driver as a module, choose M here: the
  431. module will be called dm355evm_keys.
  432. config INPUT_BFIN_ROTARY
  433. tristate "Blackfin Rotary support"
  434. depends on BF54x || BF52x
  435. help
  436. Say Y here if you want to use the Blackfin Rotary.
  437. To compile this driver as a module, choose M here: the
  438. module will be called bfin-rotary.
  439. config INPUT_WM831X_ON
  440. tristate "WM831X ON pin"
  441. depends on MFD_WM831X
  442. help
  443. Support the ON pin of WM831X PMICs as an input device
  444. reporting power button status.
  445. To compile this driver as a module, choose M here: the module
  446. will be called wm831x_on.
  447. config INPUT_PCAP
  448. tristate "Motorola EZX PCAP misc input events"
  449. depends on EZX_PCAP
  450. help
  451. Say Y here if you want to use Power key and Headphone button
  452. on Motorola EZX phones.
  453. To compile this driver as a module, choose M here: the
  454. module will be called pcap_keys.
  455. config INPUT_ADXL34X
  456. tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
  457. default n
  458. help
  459. Say Y here if you have a Accelerometer interface using the
  460. ADXL345/6 controller, and your board-specific initialization
  461. code includes that in its table of devices.
  462. This driver can use either I2C or SPI communication to the
  463. ADXL345/6 controller. Select the appropriate method for
  464. your system.
  465. If unsure, say N (but it's safe to say "Y").
  466. To compile this driver as a module, choose M here: the
  467. module will be called adxl34x.
  468. config INPUT_ADXL34X_I2C
  469. tristate "support I2C bus connection"
  470. depends on INPUT_ADXL34X && I2C
  471. default y
  472. help
  473. Say Y here if you have ADXL345/6 hooked to an I2C bus.
  474. To compile this driver as a module, choose M here: the
  475. module will be called adxl34x-i2c.
  476. config INPUT_ADXL34X_SPI
  477. tristate "support SPI bus connection"
  478. depends on INPUT_ADXL34X && SPI
  479. default y
  480. help
  481. Say Y here if you have ADXL345/6 hooked to a SPI bus.
  482. To compile this driver as a module, choose M here: the
  483. module will be called adxl34x-spi.
  484. config INPUT_IMS_PCU
  485. tristate "IMS Passenger Control Unit driver"
  486. depends on USB
  487. depends on LEDS_CLASS
  488. help
  489. Say Y here if you have system with IMS Rave Passenger Control Unit.
  490. To compile this driver as a module, choose M here: the module will be
  491. called ims_pcu.
  492. config INPUT_CMA3000
  493. tristate "VTI CMA3000 Tri-axis accelerometer"
  494. help
  495. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  496. driver
  497. This driver currently only supports I2C interface to the
  498. controller. Also select the I2C method.
  499. If unsure, say N
  500. To compile this driver as a module, choose M here: the
  501. module will be called cma3000_d0x.
  502. config INPUT_CMA3000_I2C
  503. tristate "Support I2C bus connection"
  504. depends on INPUT_CMA3000 && I2C
  505. help
  506. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  507. through I2C interface.
  508. To compile this driver as a module, choose M here: the
  509. module will be called cma3000_d0x_i2c.
  510. config INPUT_XEN_KBDDEV_FRONTEND
  511. tristate "Xen virtual keyboard and mouse support"
  512. depends on XEN
  513. default y
  514. select XEN_XENBUS_FRONTEND
  515. help
  516. This driver implements the front-end of the Xen virtual
  517. keyboard and mouse device driver. It communicates with a back-end
  518. in another domain.
  519. To compile this driver as a module, choose M here: the
  520. module will be called xen-kbdfront.
  521. config INPUT_SIRFSOC_ONKEY
  522. bool "CSR SiRFSoC power on/off/suspend key support"
  523. depends on ARCH_SIRF && OF
  524. default y
  525. help
  526. Say Y here if you want to support for the SiRFSoC power on/off/suspend key
  527. in Linux, after you press the onkey, system will suspend.
  528. If unsure, say N.
  529. config INPUT_IDEAPAD_SLIDEBAR
  530. tristate "IdeaPad Laptop Slidebar"
  531. depends on INPUT
  532. depends on SERIO_I8042
  533. help
  534. Say Y here if you have an IdeaPad laptop with a slidebar.
  535. To compile this driver as a module, choose M here: the
  536. module will be called ideapad_slidebar.
  537. config INPUT_SOC_BUTTON_ARRAY
  538. tristate "Windows-compatible SoC Button Array"
  539. depends on KEYBOARD_GPIO
  540. help
  541. Say Y here if you have a SoC-based tablet that originally
  542. runs Windows 8.
  543. To compile this driver as a module, choose M here: the
  544. module will be called soc_button_array.
  545. endif