Kconfig 13 KB

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