Kconfig 7.8 KB

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