Kconfig 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456
  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. config GPIO_GENERIC
  55. tristate
  56. # put drivers in the right section, in alphabetical order
  57. config GPIO_MAX730X
  58. tristate
  59. comment "Memory mapped GPIO drivers:"
  60. config GPIO_GENERIC_PLATFORM
  61. tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
  62. select GPIO_GENERIC
  63. help
  64. Say yes here to support basic platform_device memory-mapped GPIO controllers.
  65. config GPIO_IT8761E
  66. tristate "IT8761E GPIO support"
  67. help
  68. Say yes here to support GPIO functionality of IT8761E super I/O chip.
  69. config GPIO_EP93XX
  70. def_bool y
  71. depends on ARCH_EP93XX
  72. config GPIO_EXYNOS4
  73. def_bool y
  74. depends on CPU_EXYNOS4210
  75. config GPIO_MXC
  76. def_bool y
  77. depends on ARCH_MXC
  78. select GPIO_GENERIC
  79. select GENERIC_IRQ_CHIP
  80. config GPIO_MXS
  81. def_bool y
  82. depends on ARCH_MXS
  83. select GPIO_GENERIC
  84. select GENERIC_IRQ_CHIP
  85. config GPIO_PLAT_SAMSUNG
  86. def_bool y
  87. depends on SAMSUNG_GPIOLIB_4BIT
  88. config GPIO_S5PC100
  89. def_bool y
  90. depends on CPU_S5PC100
  91. config GPIO_S5PV210
  92. def_bool y
  93. depends on CPU_S5PV210
  94. config GPIO_PL061
  95. bool "PrimeCell PL061 GPIO support"
  96. depends on ARM_AMBA
  97. help
  98. Say yes here to support the PrimeCell PL061 GPIO device
  99. config GPIO_XILINX
  100. bool "Xilinx GPIO support"
  101. depends on PPC_OF || MICROBLAZE
  102. help
  103. Say yes here to support the Xilinx FPGA GPIO device
  104. config GPIO_VR41XX
  105. tristate "NEC VR4100 series General-purpose I/O Uint support"
  106. depends on CPU_VR41XX
  107. help
  108. Say yes here to support the NEC VR4100 series General-purpose I/O Uint
  109. config GPIO_SCH
  110. tristate "Intel SCH/TunnelCreek GPIO"
  111. depends on PCI && X86
  112. select MFD_CORE
  113. select LPC_SCH
  114. help
  115. Say yes here to support GPIO interface on Intel Poulsbo SCH
  116. or Intel Tunnel Creek processor.
  117. The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
  118. powered by the core power rail and are turned off during sleep
  119. modes (S3 and higher). The remaining four GPIOs are powered by
  120. the Intel SCH suspend power supply. These GPIOs remain
  121. active during S3. The suspend powered GPIOs can be used to wake the
  122. system from the Suspend-to-RAM state.
  123. The Intel Tunnel Creek processor has 5 GPIOs powered by the
  124. core power rail and 9 from suspend power supply.
  125. config GPIO_VX855
  126. tristate "VIA VX855/VX875 GPIO"
  127. depends on MFD_SUPPORT && PCI
  128. select MFD_CORE
  129. select MFD_VX855
  130. help
  131. Support access to the VX855/VX875 GPIO lines through the gpio library.
  132. This driver provides common support for accessing the device,
  133. additional drivers must be enabled in order to use the
  134. functionality of the device.
  135. comment "I2C GPIO expanders:"
  136. config GPIO_MAX7300
  137. tristate "Maxim MAX7300 GPIO expander"
  138. depends on I2C
  139. select GPIO_MAX730X
  140. help
  141. GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
  142. config GPIO_MAX732X
  143. tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
  144. depends on I2C
  145. help
  146. Say yes here to support the MAX7319, MAX7320-7327 series of I2C
  147. Port Expanders. Each IO port on these chips has a fixed role of
  148. Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
  149. Input and Output (designed by 'P'). The combinations are listed
  150. below:
  151. 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
  152. max7322 (4I4O), max7323 (4P4O)
  153. 16 bits: max7324 (8I8O), max7325 (8P8O),
  154. max7326 (4I12O), max7327 (4P12O)
  155. Board setup code must specify the model to use, and the start
  156. number for these GPIOs.
  157. config GPIO_MAX732X_IRQ
  158. bool "Interrupt controller support for MAX732x"
  159. depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
  160. help
  161. Say yes here to enable the max732x to be used as an interrupt
  162. controller. It requires the driver to be built in the kernel.
  163. config GPIO_PCA953X
  164. tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
  165. depends on I2C
  166. help
  167. Say yes here to provide access to several register-oriented
  168. SMBus I/O expanders, made mostly by NXP or TI. Compatible
  169. models include:
  170. 4 bits: pca9536, pca9537
  171. 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
  172. tca6408
  173. 16 bits: pca9535, pca9539, pca9555, tca6416
  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. config GPIO_ADP5588
  251. tristate "ADP5588 I2C GPIO expander"
  252. depends on I2C
  253. help
  254. This option enables support for 18 GPIOs found
  255. on Analog Devices ADP5588 GPIO Expanders.
  256. config GPIO_ADP5588_IRQ
  257. bool "Interrupt controller support for ADP5588"
  258. depends on GPIO_ADP5588=y
  259. help
  260. Say yes here to enable the adp5588 to be used as an interrupt
  261. controller. It requires the driver to be built in the kernel.
  262. comment "PCI GPIO expanders:"
  263. config GPIO_CS5535
  264. tristate "AMD CS5535/CS5536 GPIO support"
  265. depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
  266. help
  267. The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
  268. can be used for quite a number of things. The CS5535/6 is found on
  269. AMD Geode and Lemote Yeeloong devices.
  270. If unsure, say N.
  271. config GPIO_BT8XX
  272. tristate "BT8XX GPIO abuser"
  273. depends on PCI && VIDEO_BT848=n
  274. help
  275. The BT8xx frame grabber chip has 24 GPIO pins than can be abused
  276. as a cheap PCI GPIO card.
  277. This chip can be found on Miro, Hauppauge and STB TV-cards.
  278. The card needs to be physically altered for using it as a
  279. GPIO card. For more information on how to build a GPIO card
  280. from a BT8xx TV card, see the documentation file at
  281. Documentation/bt8xxgpio.txt
  282. If unsure, say N.
  283. config GPIO_LANGWELL
  284. bool "Intel Langwell/Penwell GPIO support"
  285. depends on PCI && X86
  286. help
  287. Say Y here to support Intel Langwell/Penwell GPIO.
  288. config GPIO_PCH
  289. tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
  290. depends on PCI && X86
  291. help
  292. This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
  293. which is an IOH(Input/Output Hub) for x86 embedded processor.
  294. This driver can access PCH GPIO device.
  295. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
  296. Output Hub), ML7223.
  297. ML7223 IOH is for MP(Media Phone) use.
  298. ML7223 is companion chip for Intel Atom E6xx series.
  299. ML7223 is completely compatible for Intel EG20T PCH.
  300. config GPIO_ML_IOH
  301. tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
  302. depends on PCI
  303. help
  304. ML7213 is companion chip for Intel Atom E6xx series.
  305. This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
  306. Hub) which is for IVI(In-Vehicle Infotainment) use.
  307. This driver can access the IOH's GPIO device.
  308. config GPIO_TIMBERDALE
  309. bool "Support for timberdale GPIO IP"
  310. depends on MFD_TIMBERDALE && HAS_IOMEM
  311. ---help---
  312. Add support for the GPIO IP in the timberdale FPGA.
  313. config GPIO_RDC321X
  314. tristate "RDC R-321x GPIO support"
  315. depends on PCI
  316. select MFD_SUPPORT
  317. select MFD_CORE
  318. select MFD_RDC321X
  319. help
  320. Support for the RDC R321x SoC GPIOs over southbridge
  321. PCI configuration space.
  322. comment "SPI GPIO expanders:"
  323. config GPIO_MAX7301
  324. tristate "Maxim MAX7301 GPIO expander"
  325. depends on SPI_MASTER
  326. select GPIO_MAX730X
  327. help
  328. GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
  329. config GPIO_MCP23S08
  330. tristate "Microchip MCP23Sxx I/O expander"
  331. depends on SPI_MASTER
  332. help
  333. SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
  334. This provides a GPIO interface supporting inputs and outputs.
  335. config GPIO_MC33880
  336. tristate "Freescale MC33880 high-side/low-side switch"
  337. depends on SPI_MASTER
  338. help
  339. SPI driver for Freescale MC33880 high-side/low-side switch.
  340. This provides GPIO interface supporting inputs and outputs.
  341. config GPIO_74X164
  342. tristate "74x164 serial-in/parallel-out 8-bits shift register"
  343. depends on SPI_MASTER
  344. help
  345. Platform driver for 74x164 compatible serial-in/parallel-out
  346. 8-outputs shift registers. This driver can be used to provide access
  347. to more gpio outputs.
  348. comment "AC97 GPIO expanders:"
  349. config GPIO_UCB1400
  350. bool "Philips UCB1400 GPIO"
  351. depends on UCB1400_CORE
  352. help
  353. This enables support for the Philips UCB1400 GPIO pins.
  354. The UCB1400 is an AC97 audio codec.
  355. comment "MODULbus GPIO expanders:"
  356. config GPIO_JANZ_TTL
  357. tristate "Janz VMOD-TTL Digital IO Module"
  358. depends on MFD_JANZ_CMODIO
  359. help
  360. This enables support for the Janz VMOD-TTL Digital IO module.
  361. This driver provides support for driving the pins in output
  362. mode only. Input mode is not supported.
  363. config GPIO_AB8500
  364. bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
  365. depends on AB8500_CORE && BROKEN
  366. help
  367. Select this to enable the AB8500 IC GPIO driver
  368. config GPIO_TPS65910
  369. bool "TPS65910 GPIO"
  370. depends on MFD_TPS65910
  371. help
  372. Select this option to enable GPIO driver for the TPS65910
  373. chip family.
  374. endif