Kconfig 8.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247
  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. menuconfig SPI
  9. bool "SPI support"
  10. depends on HAS_IOMEM
  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. if SPI
  27. config SPI_DEBUG
  28. boolean "Debug support for SPI drivers"
  29. depends on 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 && BLACKFIN
  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_LM70_LLP
  95. tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
  96. depends on SPI_MASTER && PARPORT && EXPERIMENTAL
  97. select SPI_BITBANG
  98. help
  99. This driver supports the NS LM70 LLP Evaluation Board,
  100. which interfaces to an LM70 temperature sensor using
  101. a parallel port.
  102. config SPI_MPC52xx_PSC
  103. tristate "Freescale MPC52xx PSC SPI controller"
  104. depends on SPI_MASTER && PPC_MPC52xx && EXPERIMENTAL
  105. help
  106. This enables using the Freescale MPC52xx Programmable Serial
  107. Controller in master SPI mode.
  108. config SPI_MPC83xx
  109. tristate "Freescale MPC83xx/QUICC Engine SPI controller"
  110. depends on SPI_MASTER && (PPC_83xx || QUICC_ENGINE) && EXPERIMENTAL
  111. help
  112. This enables using the Freescale MPC83xx and QUICC Engine SPI
  113. controllers in master mode.
  114. Note, this driver uniquely supports the SPI controller on the MPC83xx
  115. family of PowerPC processors, plus processors with QUICC Engine
  116. technology. This driver uses a simple set of shift registers for data
  117. (opposed to the CPM based descriptor model).
  118. config SPI_OMAP_UWIRE
  119. tristate "OMAP1 MicroWire"
  120. depends on SPI_MASTER && ARCH_OMAP1
  121. select SPI_BITBANG
  122. help
  123. This hooks up to the MicroWire controller on OMAP1 chips.
  124. config SPI_OMAP24XX
  125. tristate "McSPI driver for OMAP24xx/OMAP34xx"
  126. depends on SPI_MASTER && (ARCH_OMAP24XX || ARCH_OMAP34XX)
  127. help
  128. SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
  129. (McSPI) modules.
  130. config SPI_PXA2XX
  131. tristate "PXA2xx SSP SPI master"
  132. depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
  133. select PXA_SSP
  134. help
  135. This enables using a PXA2xx SSP port as a SPI master controller.
  136. The driver can be configured to use any SSP port and additional
  137. documentation can be found a Documentation/spi/pxa2xx.
  138. config SPI_S3C24XX
  139. tristate "Samsung S3C24XX series SPI"
  140. depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
  141. select SPI_BITBANG
  142. help
  143. SPI driver for Samsung S3C24XX series ARM SoCs
  144. config SPI_S3C24XX_GPIO
  145. tristate "Samsung S3C24XX series SPI by GPIO"
  146. depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
  147. select SPI_BITBANG
  148. help
  149. SPI driver for Samsung S3C24XX series ARM SoCs using
  150. GPIO lines to provide the SPI bus. This can be used where
  151. the inbuilt hardware cannot provide the transfer mode, or
  152. where the board is using non hardware connected pins.
  153. config SPI_SH_SCI
  154. tristate "SuperH SCI SPI controller"
  155. depends on SPI_MASTER && SUPERH
  156. select SPI_BITBANG
  157. help
  158. SPI driver for SuperH SCI blocks.
  159. config SPI_TXX9
  160. tristate "Toshiba TXx9 SPI controller"
  161. depends on SPI_MASTER && GENERIC_GPIO && CPU_TX49XX
  162. help
  163. SPI driver for Toshiba TXx9 MIPS SoCs
  164. config SPI_XILINX
  165. tristate "Xilinx SPI controller"
  166. depends on SPI_MASTER && XILINX_VIRTEX && EXPERIMENTAL
  167. select SPI_BITBANG
  168. help
  169. This exposes the SPI controller IP from the Xilinx EDK.
  170. See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
  171. Product Specification document (DS464) for hardware details.
  172. #
  173. # Add new SPI master controllers in alphabetical order above this line
  174. #
  175. #
  176. # There are lots of SPI device types, with sensors and memory
  177. # being probably the most widely used ones.
  178. #
  179. comment "SPI Protocol Masters"
  180. depends on SPI_MASTER
  181. config SPI_AT25
  182. tristate "SPI EEPROMs from most vendors"
  183. depends on SPI_MASTER && SYSFS
  184. help
  185. Enable this driver to get read/write support to most SPI EEPROMs,
  186. after you configure the board init code to know about each eeprom
  187. on your target board.
  188. This driver can also be built as a module. If so, the module
  189. will be called at25.
  190. config SPI_SPIDEV
  191. tristate "User mode SPI device driver support"
  192. depends on SPI_MASTER && EXPERIMENTAL
  193. help
  194. This supports user mode SPI protocol drivers.
  195. Note that this application programming interface is EXPERIMENTAL
  196. and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
  197. config SPI_TLE62X0
  198. tristate "Infineon TLE62X0 (for power switching)"
  199. depends on SPI_MASTER && SYSFS
  200. help
  201. SPI driver for Infineon TLE62X0 series line driver chips,
  202. such as the TLE6220, TLE6230 and TLE6240. This provides a
  203. sysfs interface, with each line presented as a kind of GPIO
  204. exposing both switch control and diagnostic feedback.
  205. #
  206. # Add new SPI protocol masters in alphabetical order above this line
  207. #
  208. # (slave support would go here)
  209. endif # SPI