Kconfig 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455
  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. config GPIO_PLAT_SAMSUNG
  85. def_bool y
  86. depends on SAMSUNG_GPIOLIB_4BIT
  87. config GPIO_S5PC100
  88. def_bool y
  89. depends on CPU_S5PC100
  90. config GPIO_S5PV210
  91. def_bool y
  92. depends on CPU_S5PV210
  93. config GPIO_PL061
  94. bool "PrimeCell PL061 GPIO support"
  95. depends on ARM_AMBA
  96. help
  97. Say yes here to support the PrimeCell PL061 GPIO device
  98. config GPIO_XILINX
  99. bool "Xilinx GPIO support"
  100. depends on PPC_OF || MICROBLAZE
  101. help
  102. Say yes here to support the Xilinx FPGA GPIO device
  103. config GPIO_VR41XX
  104. tristate "NEC VR4100 series General-purpose I/O Uint support"
  105. depends on CPU_VR41XX
  106. help
  107. Say yes here to support the NEC VR4100 series General-purpose I/O Uint
  108. config GPIO_SCH
  109. tristate "Intel SCH/TunnelCreek GPIO"
  110. depends on PCI && X86
  111. select MFD_CORE
  112. select LPC_SCH
  113. help
  114. Say yes here to support GPIO interface on Intel Poulsbo SCH
  115. or Intel Tunnel Creek processor.
  116. The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
  117. powered by the core power rail and are turned off during sleep
  118. modes (S3 and higher). The remaining four GPIOs are powered by
  119. the Intel SCH suspend power supply. These GPIOs remain
  120. active during S3. The suspend powered GPIOs can be used to wake the
  121. system from the Suspend-to-RAM state.
  122. The Intel Tunnel Creek processor has 5 GPIOs powered by the
  123. core power rail and 9 from suspend power supply.
  124. config GPIO_VX855
  125. tristate "VIA VX855/VX875 GPIO"
  126. depends on MFD_SUPPORT && PCI
  127. select MFD_CORE
  128. select MFD_VX855
  129. help
  130. Support access to the VX855/VX875 GPIO lines through the gpio library.
  131. This driver provides common support for accessing the device,
  132. additional drivers must be enabled in order to use the
  133. functionality of the device.
  134. comment "I2C GPIO expanders:"
  135. config GPIO_MAX7300
  136. tristate "Maxim MAX7300 GPIO expander"
  137. depends on I2C
  138. select GPIO_MAX730X
  139. help
  140. GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
  141. config GPIO_MAX732X
  142. tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
  143. depends on I2C
  144. help
  145. Say yes here to support the MAX7319, MAX7320-7327 series of I2C
  146. Port Expanders. Each IO port on these chips has a fixed role of
  147. Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
  148. Input and Output (designed by 'P'). The combinations are listed
  149. below:
  150. 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
  151. max7322 (4I4O), max7323 (4P4O)
  152. 16 bits: max7324 (8I8O), max7325 (8P8O),
  153. max7326 (4I12O), max7327 (4P12O)
  154. Board setup code must specify the model to use, and the start
  155. number for these GPIOs.
  156. config GPIO_MAX732X_IRQ
  157. bool "Interrupt controller support for MAX732x"
  158. depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
  159. help
  160. Say yes here to enable the max732x to be used as an interrupt
  161. controller. It requires the driver to be built in the kernel.
  162. config GPIO_PCA953X
  163. tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
  164. depends on I2C
  165. help
  166. Say yes here to provide access to several register-oriented
  167. SMBus I/O expanders, made mostly by NXP or TI. Compatible
  168. models include:
  169. 4 bits: pca9536, pca9537
  170. 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
  171. tca6408
  172. 16 bits: pca9535, pca9539, pca9555, tca6416
  173. config GPIO_PCA953X_IRQ
  174. bool "Interrupt controller support for PCA953x"
  175. depends on GPIO_PCA953X=y
  176. help
  177. Say yes here to enable the pca953x to be used as an interrupt
  178. controller. It requires the driver to be built in the kernel.
  179. config GPIO_PCF857X
  180. tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
  181. depends on I2C
  182. help
  183. Say yes here to provide access to most "quasi-bidirectional" I2C
  184. GPIO expanders used for additional digital outputs or inputs.
  185. Most of these parts are from NXP, though TI is a second source for
  186. some of them. Compatible models include:
  187. 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
  188. pca9670, pca9672, pca9674, pca9674a,
  189. max7328, max7329
  190. 16 bits: pcf8575, pcf8575c, pca8575,
  191. pca9671, pca9673, pca9675
  192. Your board setup code will need to declare the expanders in
  193. use, and assign numbers to the GPIOs they expose. Those GPIOs
  194. can then be used from drivers and other kernel code, just like
  195. other GPIOs, but only accessible from task contexts.
  196. This driver provides an in-kernel interface to those GPIOs using
  197. platform-neutral GPIO calls.
  198. config GPIO_SX150X
  199. bool "Semtech SX150x I2C GPIO expander"
  200. depends on I2C=y
  201. default n
  202. help
  203. Say yes here to provide support for Semtech SX150-series I2C
  204. GPIO expanders. Compatible models include:
  205. 8 bits: sx1508q
  206. 16 bits: sx1509q
  207. config GPIO_STMPE
  208. bool "STMPE GPIOs"
  209. depends on MFD_STMPE
  210. help
  211. This enables support for the GPIOs found on the STMPE I/O
  212. Expanders.
  213. config GPIO_TC3589X
  214. bool "TC3589X GPIOs"
  215. depends on MFD_TC3589X
  216. help
  217. This enables support for the GPIOs found on the TC3589X
  218. I/O Expander.
  219. config GPIO_TWL4030
  220. tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
  221. depends on TWL4030_CORE
  222. help
  223. Say yes here to access the GPIO signals of various multi-function
  224. power management chips from Texas Instruments.
  225. config GPIO_WM831X
  226. tristate "WM831x GPIOs"
  227. depends on MFD_WM831X
  228. help
  229. Say yes here to access the GPIO signals of WM831x power management
  230. chips from Wolfson Microelectronics.
  231. config GPIO_WM8350
  232. tristate "WM8350 GPIOs"
  233. depends on MFD_WM8350
  234. help
  235. Say yes here to access the GPIO signals of WM8350 power management
  236. chips from Wolfson Microelectronics.
  237. config GPIO_WM8994
  238. tristate "WM8994 GPIOs"
  239. depends on MFD_WM8994
  240. help
  241. Say yes here to access the GPIO signals of WM8994 audio hub
  242. CODECs from Wolfson Microelectronics.
  243. config GPIO_ADP5520
  244. tristate "GPIO Support for ADP5520 PMIC"
  245. depends on PMIC_ADP5520
  246. help
  247. This option enables support for on-chip GPIO found
  248. on Analog Devices ADP5520 PMICs.
  249. config GPIO_ADP5588
  250. tristate "ADP5588 I2C GPIO expander"
  251. depends on I2C
  252. help
  253. This option enables support for 18 GPIOs found
  254. on Analog Devices ADP5588 GPIO Expanders.
  255. config GPIO_ADP5588_IRQ
  256. bool "Interrupt controller support for ADP5588"
  257. depends on GPIO_ADP5588=y
  258. help
  259. Say yes here to enable the adp5588 to be used as an interrupt
  260. controller. It requires the driver to be built in the kernel.
  261. comment "PCI GPIO expanders:"
  262. config GPIO_CS5535
  263. tristate "AMD CS5535/CS5536 GPIO support"
  264. depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
  265. help
  266. The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
  267. can be used for quite a number of things. The CS5535/6 is found on
  268. AMD Geode and Lemote Yeeloong devices.
  269. If unsure, say N.
  270. config GPIO_BT8XX
  271. tristate "BT8XX GPIO abuser"
  272. depends on PCI && VIDEO_BT848=n
  273. help
  274. The BT8xx frame grabber chip has 24 GPIO pins than can be abused
  275. as a cheap PCI GPIO card.
  276. This chip can be found on Miro, Hauppauge and STB TV-cards.
  277. The card needs to be physically altered for using it as a
  278. GPIO card. For more information on how to build a GPIO card
  279. from a BT8xx TV card, see the documentation file at
  280. Documentation/bt8xxgpio.txt
  281. If unsure, say N.
  282. config GPIO_LANGWELL
  283. bool "Intel Langwell/Penwell GPIO support"
  284. depends on PCI && X86
  285. help
  286. Say Y here to support Intel Langwell/Penwell GPIO.
  287. config GPIO_PCH
  288. tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
  289. depends on PCI && X86
  290. help
  291. This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
  292. which is an IOH(Input/Output Hub) for x86 embedded processor.
  293. This driver can access PCH GPIO device.
  294. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
  295. Output Hub), ML7223.
  296. ML7223 IOH is for MP(Media Phone) use.
  297. ML7223 is companion chip for Intel Atom E6xx series.
  298. ML7223 is completely compatible for Intel EG20T PCH.
  299. config GPIO_ML_IOH
  300. tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
  301. depends on PCI
  302. help
  303. ML7213 is companion chip for Intel Atom E6xx series.
  304. This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
  305. Hub) which is for IVI(In-Vehicle Infotainment) use.
  306. This driver can access the IOH's GPIO device.
  307. config GPIO_TIMBERDALE
  308. bool "Support for timberdale GPIO IP"
  309. depends on MFD_TIMBERDALE && HAS_IOMEM
  310. ---help---
  311. Add support for the GPIO IP in the timberdale FPGA.
  312. config GPIO_RDC321X
  313. tristate "RDC R-321x GPIO support"
  314. depends on PCI
  315. select MFD_SUPPORT
  316. select MFD_CORE
  317. select MFD_RDC321X
  318. help
  319. Support for the RDC R321x SoC GPIOs over southbridge
  320. PCI configuration space.
  321. comment "SPI GPIO expanders:"
  322. config GPIO_MAX7301
  323. tristate "Maxim MAX7301 GPIO expander"
  324. depends on SPI_MASTER
  325. select GPIO_MAX730X
  326. help
  327. GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
  328. config GPIO_MCP23S08
  329. tristate "Microchip MCP23Sxx I/O expander"
  330. depends on SPI_MASTER
  331. help
  332. SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
  333. This provides a GPIO interface supporting inputs and outputs.
  334. config GPIO_MC33880
  335. tristate "Freescale MC33880 high-side/low-side switch"
  336. depends on SPI_MASTER
  337. help
  338. SPI driver for Freescale MC33880 high-side/low-side switch.
  339. This provides GPIO interface supporting inputs and outputs.
  340. config GPIO_74X164
  341. tristate "74x164 serial-in/parallel-out 8-bits shift register"
  342. depends on SPI_MASTER
  343. help
  344. Platform driver for 74x164 compatible serial-in/parallel-out
  345. 8-outputs shift registers. This driver can be used to provide access
  346. to more gpio outputs.
  347. comment "AC97 GPIO expanders:"
  348. config GPIO_UCB1400
  349. bool "Philips UCB1400 GPIO"
  350. depends on UCB1400_CORE
  351. help
  352. This enables support for the Philips UCB1400 GPIO pins.
  353. The UCB1400 is an AC97 audio codec.
  354. comment "MODULbus GPIO expanders:"
  355. config GPIO_JANZ_TTL
  356. tristate "Janz VMOD-TTL Digital IO Module"
  357. depends on MFD_JANZ_CMODIO
  358. help
  359. This enables support for the Janz VMOD-TTL Digital IO module.
  360. This driver provides support for driving the pins in output
  361. mode only. Input mode is not supported.
  362. config GPIO_AB8500
  363. bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
  364. depends on AB8500_CORE && BROKEN
  365. help
  366. Select this to enable the AB8500 IC GPIO driver
  367. config GPIO_TPS65910
  368. bool "TPS65910 GPIO"
  369. depends on MFD_TPS65910
  370. help
  371. Select this option to enable GPIO driver for the TPS65910
  372. chip family.
  373. endif