Kconfig 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. #
  2. # GPIO infrastructure and expanders
  3. #
  4. config HAVE_GPIO_LIB
  5. bool
  6. help
  7. Platforms select gpiolib if they use this infrastructure
  8. for all their GPIOs, usually starting with ones integrated
  9. into SOC processors.
  10. menu "GPIO Support"
  11. depends on HAVE_GPIO_LIB
  12. config DEBUG_GPIO
  13. bool "Debug GPIO calls"
  14. depends on DEBUG_KERNEL
  15. help
  16. Say Y here to add some extra checks and diagnostics to GPIO calls.
  17. The checks help ensure that GPIOs have been properly initialized
  18. before they are used and that sleeping calls aren not made from
  19. nonsleeping contexts. They can make bitbanged serial protocols
  20. slower. The diagnostics help catch the type of setup errors
  21. that are most common when setting up new platforms or boards.
  22. # put expanders in the right section, in alphabetical order
  23. comment "I2C GPIO expanders:"
  24. config GPIO_PCA953X
  25. tristate "PCA953x I/O ports"
  26. depends on I2C
  27. help
  28. Say yes here to support the PCA9534 (8-bit), PCA9535 (16-bit),
  29. PCA9536 (4-bit), PCA9537 (4-bit), PCA9538 (8-bit), and PCA9539
  30. (16-bit) I/O ports. These parts are made by NXP and TI.
  31. This driver can also be built as a module. If so, the module
  32. will be called pca953x.
  33. config GPIO_PCF857X
  34. tristate "PCF857x, PCA857x, and PCA967x I2C GPIO expanders"
  35. depends on I2C
  36. help
  37. Say yes here to provide access to most "quasi-bidirectional" I2C
  38. GPIO expanders used for additional digital outputs or inputs.
  39. Most of these parts are from NXP, though TI is a second source for
  40. some of them. Compatible models include:
  41. 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
  42. pca9670, pca9672, pca9674, pca9674a
  43. 16 bits: pcf8575, pcf8575c, pca8575,
  44. pca9671, pca9673, pca9675
  45. Your board setup code will need to declare the expanders in
  46. use, and assign numbers to the GPIOs they expose. Those GPIOs
  47. can then be used from drivers and other kernel code, just like
  48. other GPIOs, but only accessible from task contexts.
  49. This driver provides an in-kernel interface to those GPIOs using
  50. platform-neutral GPIO calls.
  51. comment "SPI GPIO expanders:"
  52. config GPIO_MCP23S08
  53. tristate "Microchip MCP23S08 I/O expander"
  54. depends on SPI_MASTER
  55. help
  56. SPI driver for Microchip MCP23S08 I/O expander. This provides
  57. a GPIO interface supporting inputs and outputs.
  58. endmenu