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