Kconfig 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144
  1. #
  2. # 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. The checks help ensure that GPIOs have been properly initialized
  38. before they are used and that sleeping calls aren not made from
  39. nonsleeping 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. comment "I2C GPIO expanders:"
  56. config GPIO_PCA953X
  57. tristate "PCA953x, PCA955x, and MAX7310 I/O ports"
  58. depends on I2C
  59. help
  60. Say yes here to provide access to several register-oriented
  61. SMBus I/O expanders, made mostly by NXP or TI. Compatible
  62. models include:
  63. 4 bits: pca9536, pca9537
  64. 8 bits: max7310, pca9534, pca9538, pca9554, pca9557
  65. 16 bits: pca9535, pca9539, pca9555
  66. This driver can also be built as a module. If so, the module
  67. will be called pca953x.
  68. config GPIO_PCF857X
  69. tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
  70. depends on I2C
  71. help
  72. Say yes here to provide access to most "quasi-bidirectional" I2C
  73. GPIO expanders used for additional digital outputs or inputs.
  74. Most of these parts are from NXP, though TI is a second source for
  75. some of them. Compatible models include:
  76. 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
  77. pca9670, pca9672, pca9674, pca9674a,
  78. max7328, max7329
  79. 16 bits: pcf8575, pcf8575c, pca8575,
  80. pca9671, pca9673, pca9675
  81. Your board setup code will need to declare the expanders in
  82. use, and assign numbers to the GPIOs they expose. Those GPIOs
  83. can then be used from drivers and other kernel code, just like
  84. other GPIOs, but only accessible from task contexts.
  85. This driver provides an in-kernel interface to those GPIOs using
  86. platform-neutral GPIO calls.
  87. comment "PCI GPIO expanders:"
  88. config GPIO_BT8XX
  89. tristate "BT8XX GPIO abuser"
  90. depends on PCI && VIDEO_BT848=n
  91. help
  92. The BT8xx frame grabber chip has 24 GPIO pins than can be abused
  93. as a cheap PCI GPIO card.
  94. This chip can be found on Miro, Hauppauge and STB TV-cards.
  95. The card needs to be physically altered for using it as a
  96. GPIO card. For more information on how to build a GPIO card
  97. from a BT8xx TV card, see the documentation file at
  98. Documentation/bt8xxgpio.txt
  99. If unsure, say N.
  100. comment "SPI GPIO expanders:"
  101. config GPIO_MAX7301
  102. tristate "Maxim MAX7301 GPIO expander"
  103. depends on SPI_MASTER
  104. help
  105. gpio driver for Maxim MAX7301 SPI GPIO expander.
  106. config GPIO_MCP23S08
  107. tristate "Microchip MCP23S08 I/O expander"
  108. depends on SPI_MASTER
  109. help
  110. SPI driver for Microchip MCP23S08 I/O expander. This provides
  111. a GPIO interface supporting inputs and outputs.
  112. endif