Kconfig 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346
  1. #
  2. # platform-neutral GPIO infrastructure and expanders
  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 expansion card 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 expanders in the right section, in alphabetical order
  55. config GPIO_MAX730X
  56. tristate
  57. comment "Memory mapped GPIO expanders:"
  58. config GPIO_IT8761E
  59. tristate "IT8761E GPIO support"
  60. depends on GPIOLIB
  61. help
  62. Say yes here to support GPIO functionality of IT8761E super I/O chip.
  63. config GPIO_PL061
  64. bool "PrimeCell PL061 GPIO support"
  65. depends on ARM_AMBA
  66. help
  67. Say yes here to support the PrimeCell PL061 GPIO device
  68. config GPIO_XILINX
  69. bool "Xilinx GPIO support"
  70. depends on PPC_OF || MICROBLAZE
  71. help
  72. Say yes here to support the Xilinx FPGA GPIO device
  73. config GPIO_VR41XX
  74. tristate "NEC VR4100 series General-purpose I/O Uint support"
  75. depends on CPU_VR41XX
  76. help
  77. Say yes here to support the NEC VR4100 series General-purpose I/O Uint
  78. config GPIO_SCH
  79. tristate "Intel SCH GPIO"
  80. depends on GPIOLIB && PCI
  81. select MFD_CORE
  82. select LPC_SCH
  83. help
  84. Say yes here to support GPIO interface on Intel Poulsbo SCH.
  85. The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
  86. powered by the core power rail and are turned off during sleep
  87. modes (S3 and higher). The remaining four GPIOs are powered by
  88. the Intel SCH suspend power supply. These GPIOs remain
  89. active during S3. The suspend powered GPIOs can be used to wake the
  90. system from the Suspend-to-RAM state.
  91. This driver can also be built as a module. If so, the module
  92. will be called sch-gpio.
  93. comment "I2C GPIO expanders:"
  94. config GPIO_MAX7300
  95. tristate "Maxim MAX7300 GPIO expander"
  96. depends on I2C
  97. select GPIO_MAX730X
  98. help
  99. GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
  100. config GPIO_MAX732X
  101. tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
  102. depends on I2C
  103. help
  104. Say yes here to support the MAX7319, MAX7320-7327 series of I2C
  105. Port Expanders. Each IO port on these chips has a fixed role of
  106. Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
  107. Input and Output (designed by 'P'). The combinations are listed
  108. below:
  109. 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
  110. max7322 (4I4O), max7323 (4P4O)
  111. 16 bits: max7324 (8I8O), max7325 (8P8O),
  112. max7326 (4I12O), max7327 (4P12O)
  113. Board setup code must specify the model to use, and the start
  114. number for these GPIOs.
  115. config GPIO_MAX732X_IRQ
  116. bool "Interrupt controller support for MAX732x"
  117. depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
  118. help
  119. Say yes here to enable the max732x to be used as an interrupt
  120. controller. It requires the driver to be built in the kernel.
  121. config GPIO_PCA953X
  122. tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
  123. depends on I2C
  124. help
  125. Say yes here to provide access to several register-oriented
  126. SMBus I/O expanders, made mostly by NXP or TI. Compatible
  127. models include:
  128. 4 bits: pca9536, pca9537
  129. 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
  130. tca6408
  131. 16 bits: pca9535, pca9539, pca9555, tca6416
  132. This driver can also be built as a module. If so, the module
  133. will be called pca953x.
  134. config GPIO_PCA953X_IRQ
  135. bool "Interrupt controller support for PCA953x"
  136. depends on GPIO_PCA953X=y
  137. help
  138. Say yes here to enable the pca953x to be used as an interrupt
  139. controller. It requires the driver to be built in the kernel.
  140. config GPIO_PCF857X
  141. tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
  142. depends on I2C
  143. help
  144. Say yes here to provide access to most "quasi-bidirectional" I2C
  145. GPIO expanders used for additional digital outputs or inputs.
  146. Most of these parts are from NXP, though TI is a second source for
  147. some of them. Compatible models include:
  148. 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
  149. pca9670, pca9672, pca9674, pca9674a,
  150. max7328, max7329
  151. 16 bits: pcf8575, pcf8575c, pca8575,
  152. pca9671, pca9673, pca9675
  153. Your board setup code will need to declare the expanders in
  154. use, and assign numbers to the GPIOs they expose. Those GPIOs
  155. can then be used from drivers and other kernel code, just like
  156. other GPIOs, but only accessible from task contexts.
  157. This driver provides an in-kernel interface to those GPIOs using
  158. platform-neutral GPIO calls.
  159. config GPIO_TC35892
  160. bool "TC35892 GPIOs"
  161. depends on MFD_TC35892
  162. help
  163. This enables support for the GPIOs found on the TC35892
  164. I/O Expander.
  165. config GPIO_TWL4030
  166. tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
  167. depends on TWL4030_CORE
  168. help
  169. Say yes here to access the GPIO signals of various multi-function
  170. power management chips from Texas Instruments.
  171. config GPIO_WM831X
  172. tristate "WM831x GPIOs"
  173. depends on MFD_WM831X
  174. help
  175. Say yes here to access the GPIO signals of WM831x power management
  176. chips from Wolfson Microelectronics.
  177. config GPIO_WM8350
  178. tristate "WM8350 GPIOs"
  179. depends on MFD_WM8350
  180. help
  181. Say yes here to access the GPIO signals of WM8350 power management
  182. chips from Wolfson Microelectronics.
  183. config GPIO_WM8994
  184. tristate "WM8994 GPIOs"
  185. depends on MFD_WM8994
  186. help
  187. Say yes here to access the GPIO signals of WM8994 audio hub
  188. CODECs from Wolfson Microelectronics.
  189. config GPIO_ADP5520
  190. tristate "GPIO Support for ADP5520 PMIC"
  191. depends on PMIC_ADP5520
  192. help
  193. This option enables support for on-chip GPIO found
  194. on Analog Devices ADP5520 PMICs.
  195. To compile this driver as a module, choose M here: the module will
  196. be called adp5520-gpio.
  197. config GPIO_ADP5588
  198. tristate "ADP5588 I2C GPIO expander"
  199. depends on I2C
  200. help
  201. This option enables support for 18 GPIOs found
  202. on Analog Devices ADP5588 GPIO Expanders.
  203. To compile this driver as a module, choose M here: the module will be
  204. called adp5588-gpio.
  205. comment "PCI GPIO expanders:"
  206. config GPIO_CS5535
  207. tristate "AMD CS5535/CS5536 GPIO support"
  208. depends on PCI && !CS5535_GPIO
  209. help
  210. The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
  211. can be used for quite a number of things. The CS5535/6 is found on
  212. AMD Geode and Lemote Yeeloong devices.
  213. If unsure, say N.
  214. config GPIO_BT8XX
  215. tristate "BT8XX GPIO abuser"
  216. depends on PCI && VIDEO_BT848=n
  217. help
  218. The BT8xx frame grabber chip has 24 GPIO pins than can be abused
  219. as a cheap PCI GPIO card.
  220. This chip can be found on Miro, Hauppauge and STB TV-cards.
  221. The card needs to be physically altered for using it as a
  222. GPIO card. For more information on how to build a GPIO card
  223. from a BT8xx TV card, see the documentation file at
  224. Documentation/bt8xxgpio.txt
  225. If unsure, say N.
  226. config GPIO_LANGWELL
  227. bool "Intel Langwell/Penwell GPIO support"
  228. depends on PCI
  229. help
  230. Say Y here to support Intel Langwell/Penwell GPIO.
  231. config GPIO_TIMBERDALE
  232. bool "Support for timberdale GPIO IP"
  233. depends on MFD_TIMBERDALE && GPIOLIB && HAS_IOMEM
  234. ---help---
  235. Add support for the GPIO IP in the timberdale FPGA.
  236. config GPIO_RDC321X
  237. tristate "RDC R-321x GPIO support"
  238. depends on PCI && GPIOLIB
  239. select MFD_CORE
  240. select MFD_RDC321X
  241. help
  242. Support for the RDC R321x SoC GPIOs over southbridge
  243. PCI configuration space.
  244. comment "SPI GPIO expanders:"
  245. config GPIO_MAX7301
  246. tristate "Maxim MAX7301 GPIO expander"
  247. depends on SPI_MASTER
  248. select GPIO_MAX730X
  249. help
  250. GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
  251. config GPIO_MCP23S08
  252. tristate "Microchip MCP23S08 I/O expander"
  253. depends on SPI_MASTER
  254. help
  255. SPI driver for Microchip MCP23S08 I/O expander. This provides
  256. a GPIO interface supporting inputs and outputs.
  257. config GPIO_MC33880
  258. tristate "Freescale MC33880 high-side/low-side switch"
  259. depends on SPI_MASTER
  260. help
  261. SPI driver for Freescale MC33880 high-side/low-side switch.
  262. This provides GPIO interface supporting inputs and outputs.
  263. comment "AC97 GPIO expanders:"
  264. config GPIO_UCB1400
  265. bool "Philips UCB1400 GPIO"
  266. depends on UCB1400_CORE
  267. help
  268. This enables support for the Philips UCB1400 GPIO pins.
  269. The UCB1400 is an AC97 audio codec.
  270. To compile this driver as a module, choose M here: the
  271. module will be called ucb1400_gpio.
  272. comment "MODULbus GPIO expanders:"
  273. config GPIO_JANZ_TTL
  274. tristate "Janz VMOD-TTL Digital IO Module"
  275. depends on MFD_JANZ_CMODIO
  276. help
  277. This enables support for the Janz VMOD-TTL Digital IO module.
  278. This driver provides support for driving the pins in output
  279. mode only. Input mode is not supported.
  280. endif