Kconfig 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197
  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. depends on HAS_IOMEM
  10. config SPI
  11. bool "SPI support"
  12. help
  13. The "Serial Peripheral Interface" is a low level synchronous
  14. protocol. Chips that support SPI can have data transfer rates
  15. up to several tens of Mbit/sec. Chips are addressed with a
  16. controller and a chipselect. Most SPI slaves don't support
  17. dynamic device discovery; some are even write-only or read-only.
  18. SPI is widely used by microcontrollers to talk with sensors,
  19. eeprom and flash memory, codecs and various other controller
  20. chips, analog to digital (and d-to-a) converters, and more.
  21. MMC and SD cards can be accessed using SPI protocol; and for
  22. DataFlash cards used in MMC sockets, SPI must always be used.
  23. SPI is one of a family of similar protocols using a four wire
  24. interface (select, clock, data in, data out) including Microwire
  25. (half duplex), SSP, SSI, and PSP. This driver framework should
  26. work with most such devices and controllers.
  27. config SPI_DEBUG
  28. boolean "Debug support for SPI drivers"
  29. depends on SPI && DEBUG_KERNEL
  30. help
  31. Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
  32. sysfs, and debugfs support in SPI controller and protocol drivers.
  33. #
  34. # MASTER side ... talking to discrete SPI slave chips including microcontrollers
  35. #
  36. config SPI_MASTER
  37. # boolean "SPI Master Support"
  38. boolean
  39. default SPI
  40. help
  41. If your system has an master-capable SPI controller (which
  42. provides the clock and chipselect), you can enable that
  43. controller and the protocol drivers for the SPI slave chips
  44. that are connected.
  45. comment "SPI Master Controller Drivers"
  46. depends on SPI_MASTER
  47. config SPI_ATMEL
  48. tristate "Atmel SPI Controller"
  49. depends on (ARCH_AT91 || AVR32) && SPI_MASTER
  50. help
  51. This selects a driver for the Atmel SPI Controller, present on
  52. many AT32 (AVR32) and AT91 (ARM) chips.
  53. config SPI_BFIN
  54. tristate "SPI controller driver for ADI Blackfin5xx"
  55. depends on SPI_MASTER && BFIN
  56. help
  57. This is the SPI controller master driver for Blackfin 5xx processor.
  58. config SPI_AU1550
  59. tristate "Au1550/Au12x0 SPI Controller"
  60. depends on SPI_MASTER && (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
  61. select SPI_BITBANG
  62. help
  63. If you say yes to this option, support will be included for the
  64. Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
  65. This driver can also be built as a module. If so, the module
  66. will be called au1550_spi.
  67. config SPI_BITBANG
  68. tristate "Bitbanging SPI master"
  69. depends on SPI_MASTER && EXPERIMENTAL
  70. help
  71. With a few GPIO pins, your system can bitbang the SPI protocol.
  72. Select this to get SPI support through I/O pins (GPIO, parallel
  73. port, etc). Or, some systems' SPI master controller drivers use
  74. this code to manage the per-word or per-transfer accesses to the
  75. hardware shift registers.
  76. This is library code, and is automatically selected by drivers that
  77. need it. You only need to select this explicitly to support driver
  78. modules that aren't part of this kernel tree.
  79. config SPI_BUTTERFLY
  80. tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
  81. depends on SPI_MASTER && PARPORT && EXPERIMENTAL
  82. select SPI_BITBANG
  83. help
  84. This uses a custom parallel port cable to connect to an AVR
  85. Butterfly <http://www.atmel.com/products/avr/butterfly>, an
  86. inexpensive battery powered microcontroller evaluation board.
  87. This same cable can be used to flash new firmware.
  88. config SPI_IMX
  89. tristate "Freescale iMX SPI controller"
  90. depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL
  91. help
  92. This enables using the Freescale iMX SPI controller in master
  93. mode.
  94. config SPI_MPC52xx_PSC
  95. tristate "Freescale MPC52xx PSC SPI controller"
  96. depends on SPI_MASTER && PPC_MPC52xx && EXPERIMENTAL
  97. help
  98. This enables using the Freescale MPC52xx Programmable Serial
  99. Controller in master SPI mode.
  100. config SPI_MPC83xx
  101. tristate "Freescale MPC83xx SPI controller"
  102. depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
  103. select SPI_BITBANG
  104. help
  105. This enables using the Freescale MPC83xx SPI controller in master
  106. mode.
  107. Note, this driver uniquely supports the SPI controller on the MPC83xx
  108. family of PowerPC processors. The MPC83xx uses a simple set of shift
  109. registers for data (opposed to the CPM based descriptor model).
  110. config SPI_OMAP_UWIRE
  111. tristate "OMAP1 MicroWire"
  112. depends on SPI_MASTER && ARCH_OMAP1
  113. select SPI_BITBANG
  114. help
  115. This hooks up to the MicroWire controller on OMAP1 chips.
  116. config SPI_PXA2XX
  117. tristate "PXA2xx SSP SPI master"
  118. depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
  119. help
  120. This enables using a PXA2xx SSP port as a SPI master controller.
  121. The driver can be configured to use any SSP port and additional
  122. documentation can be found a Documentation/spi/pxa2xx.
  123. config SPI_S3C24XX
  124. tristate "Samsung S3C24XX series SPI"
  125. depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
  126. help
  127. SPI driver for Samsung S3C24XX series ARM SoCs
  128. config SPI_S3C24XX_GPIO
  129. tristate "Samsung S3C24XX series SPI by GPIO"
  130. depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
  131. help
  132. SPI driver for Samsung S3C24XX series ARM SoCs using
  133. GPIO lines to provide the SPI bus. This can be used where
  134. the inbuilt hardware cannot provide the transfer mode, or
  135. where the board is using non hardware connected pins.
  136. #
  137. # Add new SPI master controllers in alphabetical order above this line
  138. #
  139. #
  140. # There are lots of SPI device types, with sensors and memory
  141. # being probably the most widely used ones.
  142. #
  143. comment "SPI Protocol Masters"
  144. depends on SPI_MASTER
  145. config SPI_AT25
  146. tristate "SPI EEPROMs from most vendors"
  147. depends on SPI_MASTER && SYSFS
  148. help
  149. Enable this driver to get read/write support to most SPI EEPROMs,
  150. after you configure the board init code to know about each eeprom
  151. on your target board.
  152. This driver can also be built as a module. If so, the module
  153. will be called at25.
  154. config SPI_SPIDEV
  155. tristate "User mode SPI device driver support"
  156. depends on SPI_MASTER && EXPERIMENTAL
  157. help
  158. This supports user mode SPI protocol drivers.
  159. Note that this application programming interface is EXPERIMENTAL
  160. and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
  161. #
  162. # Add new SPI protocol masters in alphabetical order above this line
  163. #
  164. # (slave support would go here)
  165. endmenu # "SPI support"