Kconfig 13 KB

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