Kconfig 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464
  1. #
  2. # GPIO infrastructure and drivers
  3. #
  4. config ARCH_WANT_OPTIONAL_GPIOLIB
  5. bool
  6. help
  7. Select this config option from the architecture Kconfig, if
  8. it is possible to use gpiolib on the architecture, but let the
  9. user decide whether to actually build it or not.
  10. Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
  11. not depend on GPIOs being available, but rather let the user
  12. decide whether he needs it or not.
  13. config ARCH_REQUIRE_GPIOLIB
  14. bool
  15. select GPIOLIB
  16. help
  17. Platforms select gpiolib if they use this infrastructure
  18. for all their GPIOs, usually starting with ones integrated
  19. into SOC processors.
  20. Selecting this from the architecture code will cause the gpiolib
  21. code to always get built in.
  22. menuconfig GPIOLIB
  23. bool "GPIO Support"
  24. depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
  25. select GENERIC_GPIO
  26. help
  27. This enables GPIO support through the generic GPIO library.
  28. You only need to enable this, if you also want to enable
  29. one or more of the GPIO drivers below.
  30. If unsure, say N.
  31. if GPIOLIB
  32. config DEBUG_GPIO
  33. bool "Debug GPIO calls"
  34. depends on DEBUG_KERNEL
  35. help
  36. Say Y here to add some extra checks and diagnostics to GPIO calls.
  37. These checks help ensure that GPIOs have been properly initialized
  38. before they are used, and that sleeping calls are not made from
  39. non-sleeping contexts. They can make bitbanged serial protocols
  40. slower. The diagnostics help catch the type of setup errors
  41. that are most common when setting up new platforms or boards.
  42. config GPIO_SYSFS
  43. bool "/sys/class/gpio/... (sysfs interface)"
  44. depends on SYSFS && EXPERIMENTAL
  45. help
  46. Say Y here to add a sysfs interface for GPIOs.
  47. This is mostly useful to work around omissions in a system's
  48. kernel support. Those are common in custom and semicustom
  49. hardware assembled using standard kernels with a minimum of
  50. custom patches. In those cases, userspace code may import
  51. a given GPIO from the kernel, if no kernel driver requested it.
  52. Kernel drivers may also request that a particular GPIO be
  53. exported to userspace; this can be useful when debugging.
  54. # put drivers in the right section, in alphabetical order
  55. config GPIO_MAX730X
  56. tristate
  57. comment "Memory mapped GPIO drivers:"
  58. config GPIO_BASIC_MMIO_CORE
  59. tristate
  60. help
  61. Provides core functionality for basic memory-mapped GPIO controllers.
  62. config GPIO_BASIC_MMIO
  63. tristate "Basic memory-mapped GPIO controllers support"
  64. select GPIO_BASIC_MMIO_CORE
  65. help
  66. Say yes here to support basic memory-mapped GPIO controllers.
  67. config GPIO_IT8761E
  68. tristate "IT8761E GPIO support"
  69. help
  70. Say yes here to support GPIO functionality of IT8761E super I/O chip.
  71. config GPIO_EXYNOS4
  72. def_bool y
  73. depends on CPU_EXYNOS4210
  74. config GPIO_MSM_V1
  75. tristate "Qualcomm MSM GPIO v1"
  76. depends on GPIOLIB && ARCH_MSM
  77. help
  78. Say yes here to support the GPIO interface on ARM v6 based
  79. Qualcomm MSM chips. Most of the pins on the MSM can be
  80. selected for GPIO, and are controlled by this driver.
  81. config GPIO_PLAT_SAMSUNG
  82. def_bool y
  83. depends on SAMSUNG_GPIOLIB_4BIT
  84. config GPIO_S5PC100
  85. def_bool y
  86. depends on CPU_S5PC100
  87. config GPIO_S5PV210
  88. def_bool y
  89. depends on CPU_S5PV210
  90. config GPIO_PL061
  91. bool "PrimeCell PL061 GPIO support"
  92. depends on ARM_AMBA
  93. help
  94. Say yes here to support the PrimeCell PL061 GPIO device
  95. config GPIO_XILINX
  96. bool "Xilinx GPIO support"
  97. depends on PPC_OF || MICROBLAZE
  98. help
  99. Say yes here to support the Xilinx FPGA GPIO device
  100. config GPIO_VR41XX
  101. tristate "NEC VR4100 series General-purpose I/O Uint support"
  102. depends on CPU_VR41XX
  103. help
  104. Say yes here to support the NEC VR4100 series General-purpose I/O Uint
  105. config GPIO_SCH
  106. tristate "Intel SCH/TunnelCreek GPIO"
  107. depends on PCI && X86
  108. select MFD_CORE
  109. select LPC_SCH
  110. help
  111. Say yes here to support GPIO interface on Intel Poulsbo SCH
  112. or Intel Tunnel Creek processor.
  113. The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
  114. powered by the core power rail and are turned off during sleep
  115. modes (S3 and higher). The remaining four GPIOs are powered by
  116. the Intel SCH suspend power supply. These GPIOs remain
  117. active during S3. The suspend powered GPIOs can be used to wake the
  118. system from the Suspend-to-RAM state.
  119. The Intel Tunnel Creek processor has 5 GPIOs powered by the
  120. core power rail and 9 from suspend power supply.
  121. This driver can also be built as a module. If so, the module
  122. will be called sch-gpio.
  123. config GPIO_VX855
  124. tristate "VIA VX855/VX875 GPIO"
  125. depends on MFD_SUPPORT && PCI
  126. select MFD_CORE
  127. select MFD_VX855
  128. help
  129. Support access to the VX855/VX875 GPIO lines through the gpio library.
  130. This driver provides common support for accessing the device,
  131. additional drivers must be enabled in order to use the
  132. functionality of the device.
  133. comment "I2C GPIO expanders:"
  134. config GPIO_MAX7300
  135. tristate "Maxim MAX7300 GPIO expander"
  136. depends on I2C
  137. select GPIO_MAX730X
  138. help
  139. GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
  140. config GPIO_MAX732X
  141. tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
  142. depends on I2C
  143. help
  144. Say yes here to support the MAX7319, MAX7320-7327 series of I2C
  145. Port Expanders. Each IO port on these chips has a fixed role of
  146. Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
  147. Input and Output (designed by 'P'). The combinations are listed
  148. below:
  149. 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
  150. max7322 (4I4O), max7323 (4P4O)
  151. 16 bits: max7324 (8I8O), max7325 (8P8O),
  152. max7326 (4I12O), max7327 (4P12O)
  153. Board setup code must specify the model to use, and the start
  154. number for these GPIOs.
  155. config GPIO_MAX732X_IRQ
  156. bool "Interrupt controller support for MAX732x"
  157. depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
  158. help
  159. Say yes here to enable the max732x to be used as an interrupt
  160. controller. It requires the driver to be built in the kernel.
  161. config GPIO_PCA953X
  162. tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
  163. depends on I2C
  164. help
  165. Say yes here to provide access to several register-oriented
  166. SMBus I/O expanders, made mostly by NXP or TI. Compatible
  167. models include:
  168. 4 bits: pca9536, pca9537
  169. 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
  170. tca6408
  171. 16 bits: pca9535, pca9539, pca9555, tca6416
  172. This driver can also be built as a module. If so, the module
  173. will be called pca953x.
  174. config GPIO_PCA953X_IRQ
  175. bool "Interrupt controller support for PCA953x"
  176. depends on GPIO_PCA953X=y
  177. help
  178. Say yes here to enable the pca953x to be used as an interrupt
  179. controller. It requires the driver to be built in the kernel.
  180. config GPIO_PCF857X
  181. tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
  182. depends on I2C
  183. help
  184. Say yes here to provide access to most "quasi-bidirectional" I2C
  185. GPIO expanders used for additional digital outputs or inputs.
  186. Most of these parts are from NXP, though TI is a second source for
  187. some of them. Compatible models include:
  188. 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
  189. pca9670, pca9672, pca9674, pca9674a,
  190. max7328, max7329
  191. 16 bits: pcf8575, pcf8575c, pca8575,
  192. pca9671, pca9673, pca9675
  193. Your board setup code will need to declare the expanders in
  194. use, and assign numbers to the GPIOs they expose. Those GPIOs
  195. can then be used from drivers and other kernel code, just like
  196. other GPIOs, but only accessible from task contexts.
  197. This driver provides an in-kernel interface to those GPIOs using
  198. platform-neutral GPIO calls.
  199. config GPIO_SX150X
  200. bool "Semtech SX150x I2C GPIO expander"
  201. depends on I2C=y
  202. default n
  203. help
  204. Say yes here to provide support for Semtech SX150-series I2C
  205. GPIO expanders. Compatible models include:
  206. 8 bits: sx1508q
  207. 16 bits: sx1509q
  208. config GPIO_STMPE
  209. bool "STMPE GPIOs"
  210. depends on MFD_STMPE
  211. help
  212. This enables support for the GPIOs found on the STMPE I/O
  213. Expanders.
  214. config GPIO_TC3589X
  215. bool "TC3589X GPIOs"
  216. depends on MFD_TC3589X
  217. help
  218. This enables support for the GPIOs found on the TC3589X
  219. I/O Expander.
  220. config GPIO_TWL4030
  221. tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
  222. depends on TWL4030_CORE
  223. help
  224. Say yes here to access the GPIO signals of various multi-function
  225. power management chips from Texas Instruments.
  226. config GPIO_WM831X
  227. tristate "WM831x GPIOs"
  228. depends on MFD_WM831X
  229. help
  230. Say yes here to access the GPIO signals of WM831x power management
  231. chips from Wolfson Microelectronics.
  232. config GPIO_WM8350
  233. tristate "WM8350 GPIOs"
  234. depends on MFD_WM8350
  235. help
  236. Say yes here to access the GPIO signals of WM8350 power management
  237. chips from Wolfson Microelectronics.
  238. config GPIO_WM8994
  239. tristate "WM8994 GPIOs"
  240. depends on MFD_WM8994
  241. help
  242. Say yes here to access the GPIO signals of WM8994 audio hub
  243. CODECs from Wolfson Microelectronics.
  244. config GPIO_ADP5520
  245. tristate "GPIO Support for ADP5520 PMIC"
  246. depends on PMIC_ADP5520
  247. help
  248. This option enables support for on-chip GPIO found
  249. on Analog Devices ADP5520 PMICs.
  250. To compile this driver as a module, choose M here: the module will
  251. be called adp5520-gpio.
  252. config GPIO_ADP5588
  253. tristate "ADP5588 I2C GPIO expander"
  254. depends on I2C
  255. help
  256. This option enables support for 18 GPIOs found
  257. on Analog Devices ADP5588 GPIO Expanders.
  258. To compile this driver as a module, choose M here: the module will be
  259. called adp5588-gpio.
  260. config GPIO_ADP5588_IRQ
  261. bool "Interrupt controller support for ADP5588"
  262. depends on GPIO_ADP5588=y
  263. help
  264. Say yes here to enable the adp5588 to be used as an interrupt
  265. controller. It requires the driver to be built in the kernel.
  266. comment "PCI GPIO expanders:"
  267. config GPIO_CS5535
  268. tristate "AMD CS5535/CS5536 GPIO support"
  269. depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
  270. help
  271. The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
  272. can be used for quite a number of things. The CS5535/6 is found on
  273. AMD Geode and Lemote Yeeloong devices.
  274. If unsure, say N.
  275. config GPIO_BT8XX
  276. tristate "BT8XX GPIO abuser"
  277. depends on PCI && VIDEO_BT848=n
  278. help
  279. The BT8xx frame grabber chip has 24 GPIO pins than can be abused
  280. as a cheap PCI GPIO card.
  281. This chip can be found on Miro, Hauppauge and STB TV-cards.
  282. The card needs to be physically altered for using it as a
  283. GPIO card. For more information on how to build a GPIO card
  284. from a BT8xx TV card, see the documentation file at
  285. Documentation/bt8xxgpio.txt
  286. If unsure, say N.
  287. config GPIO_LANGWELL
  288. bool "Intel Langwell/Penwell GPIO support"
  289. depends on PCI && X86
  290. help
  291. Say Y here to support Intel Langwell/Penwell GPIO.
  292. config GPIO_PCH
  293. tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
  294. depends on PCI && X86
  295. help
  296. This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
  297. which is an IOH(Input/Output Hub) for x86 embedded processor.
  298. This driver can access PCH GPIO device.
  299. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
  300. Output Hub), ML7223.
  301. ML7223 IOH is for MP(Media Phone) use.
  302. ML7223 is companion chip for Intel Atom E6xx series.
  303. ML7223 is completely compatible for Intel EG20T PCH.
  304. config GPIO_ML_IOH
  305. tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
  306. depends on PCI
  307. help
  308. ML7213 is companion chip for Intel Atom E6xx series.
  309. This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
  310. Hub) which is for IVI(In-Vehicle Infotainment) use.
  311. This driver can access the IOH's GPIO device.
  312. config GPIO_TIMBERDALE
  313. bool "Support for timberdale GPIO IP"
  314. depends on MFD_TIMBERDALE && HAS_IOMEM
  315. ---help---
  316. Add support for the GPIO IP in the timberdale FPGA.
  317. config GPIO_RDC321X
  318. tristate "RDC R-321x GPIO support"
  319. depends on PCI
  320. select MFD_SUPPORT
  321. select MFD_CORE
  322. select MFD_RDC321X
  323. help
  324. Support for the RDC R321x SoC GPIOs over southbridge
  325. PCI configuration space.
  326. comment "SPI GPIO expanders:"
  327. config GPIO_MAX7301
  328. tristate "Maxim MAX7301 GPIO expander"
  329. depends on SPI_MASTER
  330. select GPIO_MAX730X
  331. help
  332. GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
  333. config GPIO_MCP23S08
  334. tristate "Microchip MCP23Sxx I/O expander"
  335. depends on SPI_MASTER
  336. help
  337. SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
  338. This provides a GPIO interface supporting inputs and outputs.
  339. config GPIO_MC33880
  340. tristate "Freescale MC33880 high-side/low-side switch"
  341. depends on SPI_MASTER
  342. help
  343. SPI driver for Freescale MC33880 high-side/low-side switch.
  344. This provides GPIO interface supporting inputs and outputs.
  345. config GPIO_74X164
  346. tristate "74x164 serial-in/parallel-out 8-bits shift register"
  347. depends on SPI_MASTER
  348. help
  349. Platform driver for 74x164 compatible serial-in/parallel-out
  350. 8-outputs shift registers. This driver can be used to provide access
  351. to more gpio outputs.
  352. comment "AC97 GPIO expanders:"
  353. config GPIO_UCB1400
  354. bool "Philips UCB1400 GPIO"
  355. depends on UCB1400_CORE
  356. help
  357. This enables support for the Philips UCB1400 GPIO pins.
  358. The UCB1400 is an AC97 audio codec.
  359. To compile this driver as a module, choose M here: the
  360. module will be called ucb1400_gpio.
  361. comment "MODULbus GPIO expanders:"
  362. config GPIO_JANZ_TTL
  363. tristate "Janz VMOD-TTL Digital IO Module"
  364. depends on MFD_JANZ_CMODIO
  365. help
  366. This enables support for the Janz VMOD-TTL Digital IO module.
  367. This driver provides support for driving the pins in output
  368. mode only. Input mode is not supported.
  369. config AB8500_GPIO
  370. bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
  371. depends on AB8500_CORE && BROKEN
  372. help
  373. Select this to enable the AB8500 IC GPIO driver
  374. config GPIO_TPS65910
  375. bool "TPS65910 GPIO"
  376. depends on MFD_TPS65910
  377. help
  378. Select this option to enable GPIO driver for the TPS65910
  379. chip family.
  380. endif