Kconfig 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  1. #
  2. # SPI driver configuration
  3. #
  4. # NOTE: the reason this doesn't show SPI slave support is mostly that
  5. # nobody's needed a slave side API yet. The master-role API is not
  6. # fully appropriate there, so it'd need some thought to do well.
  7. #
  8. menu "SPI support"
  9. config SPI
  10. bool "SPI support"
  11. help
  12. The "Serial Peripheral Interface" is a low level synchronous
  13. protocol. Chips that support SPI can have data transfer rates
  14. up to several tens of Mbit/sec. Chips are addressed with a
  15. controller and a chipselect. Most SPI slaves don't support
  16. dynamic device discovery; some are even write-only or read-only.
  17. SPI is widely used by microcontollers to talk with sensors,
  18. eeprom and flash memory, codecs and various other controller
  19. chips, analog to digital (and d-to-a) converters, and more.
  20. MMC and SD cards can be accessed using SPI protocol; and for
  21. DataFlash cards used in MMC sockets, SPI must always be used.
  22. SPI is one of a family of similar protocols using a four wire
  23. interface (select, clock, data in, data out) including Microwire
  24. (half duplex), SSP, SSI, and PSP. This driver framework should
  25. work with most such devices and controllers.
  26. config SPI_DEBUG
  27. boolean "Debug support for SPI drivers"
  28. depends on SPI && DEBUG_KERNEL
  29. help
  30. Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
  31. sysfs, and debugfs support in SPI controller and protocol drivers.
  32. #
  33. # MASTER side ... talking to discrete SPI slave chips including microcontrollers
  34. #
  35. config SPI_MASTER
  36. # boolean "SPI Master Support"
  37. boolean
  38. default SPI
  39. help
  40. If your system has an master-capable SPI controller (which
  41. provides the clock and chipselect), you can enable that
  42. controller and the protocol drivers for the SPI slave chips
  43. that are connected.
  44. comment "SPI Master Controller Drivers"
  45. depends on SPI_MASTER
  46. config SPI_BITBANG
  47. tristate "Bitbanging SPI master"
  48. depends on SPI_MASTER && EXPERIMENTAL
  49. help
  50. With a few GPIO pins, your system can bitbang the SPI protocol.
  51. Select this to get SPI support through I/O pins (GPIO, parallel
  52. port, etc). Or, some systems' SPI master controller drivers use
  53. this code to manage the per-word or per-transfer accesses to the
  54. hardware shift registers.
  55. This is library code, and is automatically selected by drivers that
  56. need it. You only need to select this explicitly to support driver
  57. modules that aren't part of this kernel tree.
  58. config SPI_BUTTERFLY
  59. tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
  60. depends on SPI_MASTER && PARPORT && EXPERIMENTAL
  61. select SPI_BITBANG
  62. help
  63. This uses a custom parallel port cable to connect to an AVR
  64. Butterfly <http://www.atmel.com/products/avr/butterfly>, an
  65. inexpensive battery powered microcontroller evaluation board.
  66. This same cable can be used to flash new firmware.
  67. config SPI_MPC83xx
  68. tristate "Freescale MPC83xx SPI controller"
  69. depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
  70. select SPI_BITBANG
  71. help
  72. This enables using the Freescale MPC83xx SPI controller in master
  73. mode.
  74. Note, this driver uniquely supports the SPI controller on the MPC83xx
  75. family of PowerPC processors. The MPC83xx uses a simple set of shift
  76. registers for data (opposed to the CPM based descriptor model).
  77. config SPI_PXA2XX
  78. tristate "PXA2xx SSP SPI master"
  79. depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
  80. help
  81. This enables using a PXA2xx SSP port as a SPI master controller.
  82. The driver can be configured to use any SSP port and additional
  83. documentation can be found a Documentation/spi/pxa2xx.
  84. config SPI_S3C24XX_GPIO
  85. tristate "Samsung S3C24XX series SPI by GPIO"
  86. depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
  87. help
  88. SPI driver for Samsung S3C24XX series ARM SoCs using
  89. GPIO lines to provide the SPI bus. This can be used where
  90. the inbuilt hardware cannot provide the transfer mode, or
  91. where the board is using non hardware connected pins.
  92. #
  93. # Add new SPI master controllers in alphabetical order above this line
  94. #
  95. config SPI_S3C24XX
  96. tristate "Samsung S3C24XX series SPI"
  97. depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
  98. help
  99. SPI driver for Samsung S3C24XX series ARM SoCs
  100. #
  101. # There are lots of SPI device types, with sensors and memory
  102. # being probably the most widely used ones.
  103. #
  104. comment "SPI Protocol Masters"
  105. depends on SPI_MASTER
  106. #
  107. # Add new SPI protocol masters in alphabetical order above this line
  108. #
  109. # (slave support would go here)
  110. endmenu # "SPI support"