Kconfig 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189
  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 microcontrollers 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_ATMEL
  47. tristate "Atmel SPI Controller"
  48. depends on (ARCH_AT91 || AVR32) && SPI_MASTER
  49. help
  50. This selects a driver for the Atmel SPI Controller, present on
  51. many AT32 (AVR32) and AT91 (ARM) chips.
  52. config SPI_BFIN
  53. tristate "SPI controller driver for ADI Blackfin5xx"
  54. depends on SPI_MASTER && BFIN
  55. help
  56. This is the SPI controller master driver for Blackfin 5xx processor.
  57. config SPI_AU1550
  58. tristate "Au1550/Au12x0 SPI Controller"
  59. depends on SPI_MASTER && (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
  60. select SPI_BITBANG
  61. help
  62. If you say yes to this option, support will be included for the
  63. Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
  64. This driver can also be built as a module. If so, the module
  65. will be called au1550_spi.
  66. config SPI_BITBANG
  67. tristate "Bitbanging SPI master"
  68. depends on SPI_MASTER && EXPERIMENTAL
  69. help
  70. With a few GPIO pins, your system can bitbang the SPI protocol.
  71. Select this to get SPI support through I/O pins (GPIO, parallel
  72. port, etc). Or, some systems' SPI master controller drivers use
  73. this code to manage the per-word or per-transfer accesses to the
  74. hardware shift registers.
  75. This is library code, and is automatically selected by drivers that
  76. need it. You only need to select this explicitly to support driver
  77. modules that aren't part of this kernel tree.
  78. config SPI_BUTTERFLY
  79. tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
  80. depends on SPI_MASTER && PARPORT && EXPERIMENTAL
  81. select SPI_BITBANG
  82. help
  83. This uses a custom parallel port cable to connect to an AVR
  84. Butterfly <http://www.atmel.com/products/avr/butterfly>, an
  85. inexpensive battery powered microcontroller evaluation board.
  86. This same cable can be used to flash new firmware.
  87. config SPI_IMX
  88. tristate "Freescale iMX SPI controller"
  89. depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL
  90. help
  91. This enables using the Freescale iMX SPI controller in master
  92. mode.
  93. config SPI_MPC83xx
  94. tristate "Freescale MPC83xx SPI controller"
  95. depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
  96. select SPI_BITBANG
  97. help
  98. This enables using the Freescale MPC83xx SPI controller in master
  99. mode.
  100. Note, this driver uniquely supports the SPI controller on the MPC83xx
  101. family of PowerPC processors. The MPC83xx uses a simple set of shift
  102. registers for data (opposed to the CPM based descriptor model).
  103. config SPI_OMAP_UWIRE
  104. tristate "OMAP1 MicroWire"
  105. depends on SPI_MASTER && ARCH_OMAP1
  106. select SPI_BITBANG
  107. help
  108. This hooks up to the MicroWire controller on OMAP1 chips.
  109. config SPI_PXA2XX
  110. tristate "PXA2xx SSP SPI master"
  111. depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
  112. help
  113. This enables using a PXA2xx SSP port as a SPI master controller.
  114. The driver can be configured to use any SSP port and additional
  115. documentation can be found a Documentation/spi/pxa2xx.
  116. config SPI_S3C24XX
  117. tristate "Samsung S3C24XX series SPI"
  118. depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
  119. help
  120. SPI driver for Samsung S3C24XX series ARM SoCs
  121. config SPI_S3C24XX_GPIO
  122. tristate "Samsung S3C24XX series SPI by GPIO"
  123. depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
  124. help
  125. SPI driver for Samsung S3C24XX series ARM SoCs using
  126. GPIO lines to provide the SPI bus. This can be used where
  127. the inbuilt hardware cannot provide the transfer mode, or
  128. where the board is using non hardware connected pins.
  129. #
  130. # Add new SPI master controllers in alphabetical order above this line
  131. #
  132. #
  133. # There are lots of SPI device types, with sensors and memory
  134. # being probably the most widely used ones.
  135. #
  136. comment "SPI Protocol Masters"
  137. depends on SPI_MASTER
  138. config SPI_AT25
  139. tristate "SPI EEPROMs from most vendors"
  140. depends on SPI_MASTER && SYSFS
  141. help
  142. Enable this driver to get read/write support to most SPI EEPROMs,
  143. after you configure the board init code to know about each eeprom
  144. on your target board.
  145. This driver can also be built as a module. If so, the module
  146. will be called at25.
  147. config SPI_SPIDEV
  148. tristate "User mode SPI device driver support"
  149. depends on SPI_MASTER && EXPERIMENTAL
  150. help
  151. This supports user mode SPI protocol drivers.
  152. Note that this application programming interface is EXPERIMENTAL
  153. and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
  154. #
  155. # Add new SPI protocol masters in alphabetical order above this line
  156. #
  157. # (slave support would go here)
  158. endmenu # "SPI support"