Kconfig 39 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # SPI driver configuration
  4. #
  5. menuconfig SPI
  6. bool "SPI support"
  7. depends on HAS_IOMEM
  8. help
  9. The "Serial Peripheral Interface" is a low level synchronous
  10. protocol. Chips that support SPI can have data transfer rates
  11. up to several tens of Mbit/sec. Chips are addressed with a
  12. controller and a chipselect. Most SPI slaves don't support
  13. dynamic device discovery; some are even write-only or read-only.
  14. SPI is widely used by microcontrollers to talk with sensors,
  15. eeprom and flash memory, codecs and various other controller
  16. chips, analog to digital (and d-to-a) converters, and more.
  17. MMC and SD cards can be accessed using SPI protocol; and for
  18. DataFlash cards used in MMC sockets, SPI must always be used.
  19. SPI is one of a family of similar protocols using a four wire
  20. interface (select, clock, data in, data out) including Microwire
  21. (half duplex), SSP, SSI, and PSP. This driver framework should
  22. work with most such devices and controllers.
  23. if SPI
  24. config SPI_DEBUG
  25. bool "Debug support for SPI drivers"
  26. depends on DEBUG_KERNEL
  27. help
  28. Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
  29. sysfs, and debugfs support in SPI controller and protocol drivers.
  30. #
  31. # MASTER side ... talking to discrete SPI slave chips including microcontrollers
  32. #
  33. config SPI_MASTER
  34. # bool "SPI Master Support"
  35. bool
  36. default SPI
  37. help
  38. If your system has an master-capable SPI controller (which
  39. provides the clock and chipselect), you can enable that
  40. controller and the protocol drivers for the SPI slave chips
  41. that are connected.
  42. if SPI_MASTER
  43. config SPI_MEM
  44. bool "SPI memory extension"
  45. help
  46. Enable this option if you want to enable the SPI memory extension.
  47. This extension is meant to simplify interaction with SPI memories
  48. by providing a high-level interface to send memory-like commands.
  49. comment "SPI Master Controller Drivers"
  50. config SPI_ALTERA
  51. tristate "Altera SPI Controller platform driver"
  52. select SPI_ALTERA_CORE
  53. select REGMAP_MMIO
  54. help
  55. This is the driver for the Altera SPI Controller.
  56. config SPI_ALTERA_CORE
  57. tristate "Altera SPI Controller core code" if COMPILE_TEST
  58. select REGMAP
  59. help
  60. "The core code for the Altera SPI Controller"
  61. config SPI_ALTERA_DFL
  62. tristate "DFL bus driver for Altera SPI Controller"
  63. depends on FPGA_DFL
  64. select SPI_ALTERA_CORE
  65. help
  66. This is a Device Feature List (DFL) bus driver for the
  67. Altera SPI master controller. The SPI master is connected
  68. to a SPI slave to Avalon bridge in a Intel MAX BMC.
  69. config SPI_AR934X
  70. tristate "Qualcomm Atheros AR934X/QCA95XX SPI controller driver"
  71. depends on ATH79 || COMPILE_TEST
  72. help
  73. This enables support for the SPI controller present on the
  74. Qualcomm Atheros AR934X/QCA95XX SoCs.
  75. config SPI_ATH79
  76. tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
  77. depends on ATH79 || COMPILE_TEST
  78. select SPI_BITBANG
  79. help
  80. This enables support for the SPI controller present on the
  81. Atheros AR71XX/AR724X/AR913X SoCs.
  82. config SPI_ARMADA_3700
  83. tristate "Marvell Armada 3700 SPI Controller"
  84. depends on (ARCH_MVEBU && OF) || COMPILE_TEST
  85. help
  86. This enables support for the SPI controller present on the
  87. Marvell Armada 3700 SoCs.
  88. config SPI_ASPEED_SMC
  89. tristate "Aspeed flash controllers in SPI mode"
  90. depends on ARCH_ASPEED || COMPILE_TEST
  91. depends on OF
  92. help
  93. This enables support for the Firmware Memory controller (FMC)
  94. in the Aspeed AST2600, AST2500 and AST2400 SoCs when attached
  95. to SPI NOR chips, and support for the SPI flash memory
  96. controller (SPI) for the host firmware. The implementation
  97. only supports SPI NOR.
  98. config SPI_ATMEL
  99. tristate "Atmel SPI Controller"
  100. depends on ARCH_AT91 || COMPILE_TEST
  101. depends on OF
  102. help
  103. This selects a driver for the Atmel SPI Controller, present on
  104. many AT91 ARM chips.
  105. config SPI_AT91_USART
  106. tristate "Atmel USART Controller SPI driver"
  107. depends on (ARCH_AT91 || COMPILE_TEST)
  108. depends on MFD_AT91_USART
  109. help
  110. This selects a driver for the AT91 USART Controller as SPI Master,
  111. present on AT91 and SAMA5 SoC series.
  112. config SPI_ATMEL_QUADSPI
  113. tristate "Atmel Quad SPI Controller"
  114. depends on ARCH_AT91 || COMPILE_TEST
  115. depends on OF && HAS_IOMEM
  116. help
  117. This enables support for the Quad SPI controller in master mode.
  118. This driver does not support generic SPI. The implementation only
  119. supports spi-mem interface.
  120. config SPI_AU1550
  121. tristate "Au1550/Au1200/Au1300 SPI Controller"
  122. depends on MIPS_ALCHEMY
  123. select SPI_BITBANG
  124. help
  125. If you say yes to this option, support will be included for the
  126. PSC SPI controller found on Au1550, Au1200 and Au1300 series.
  127. config SPI_AXI_SPI_ENGINE
  128. tristate "Analog Devices AXI SPI Engine controller"
  129. depends on HAS_IOMEM
  130. help
  131. This enables support for the Analog Devices AXI SPI Engine SPI controller.
  132. It is part of the SPI Engine framework that is used in some Analog Devices
  133. reference designs for FPGAs.
  134. config SPI_BCM2835
  135. tristate "BCM2835 SPI controller"
  136. depends on GPIOLIB
  137. depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
  138. help
  139. This selects a driver for the Broadcom BCM2835 SPI master.
  140. The BCM2835 contains two types of SPI master controller; the
  141. "universal SPI master", and the regular SPI controller. This driver
  142. is for the regular SPI controller. Slave mode operation is not also
  143. not supported.
  144. config SPI_BCM2835AUX
  145. tristate "BCM2835 SPI auxiliary controller"
  146. depends on ((ARCH_BCM2835 || ARCH_BRCMSTB) && GPIOLIB) || COMPILE_TEST
  147. help
  148. This selects a driver for the Broadcom BCM2835 SPI aux master.
  149. The BCM2835 contains two types of SPI master controller; the
  150. "universal SPI master", and the regular SPI controller.
  151. This driver is for the universal/auxiliary SPI controller.
  152. config SPI_BCM63XX
  153. tristate "Broadcom BCM63xx SPI controller"
  154. depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
  155. help
  156. Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
  157. config SPI_BCM63XX_HSSPI
  158. tristate "Broadcom BCM63XX HS SPI controller driver"
  159. depends on BCM63XX || BMIPS_GENERIC || ARCH_BCMBCA || COMPILE_TEST
  160. help
  161. This enables support for the High Speed SPI controller present on
  162. newer Broadcom BCM63XX SoCs.
  163. config SPI_BCM_QSPI
  164. tristate "Broadcom BSPI and MSPI controller support"
  165. depends on ARCH_BRCMSTB || ARCH_BCM || ARCH_BCM_IPROC || \
  166. BMIPS_GENERIC || COMPILE_TEST
  167. default ARCH_BCM_IPROC
  168. help
  169. Enables support for the Broadcom SPI flash and MSPI controller.
  170. Select this option for any one of BRCMSTB, iProc NSP and NS2 SoCs
  171. based platforms. This driver works for both SPI master for SPI NOR
  172. flash device as well as MSPI device.
  173. config SPI_BITBANG
  174. tristate "Utilities for Bitbanging SPI masters"
  175. help
  176. With a few GPIO pins, your system can bitbang the SPI protocol.
  177. Select this to get SPI support through I/O pins (GPIO, parallel
  178. port, etc). Or, some systems' SPI master controller drivers use
  179. this code to manage the per-word or per-transfer accesses to the
  180. hardware shift registers.
  181. This is library code, and is automatically selected by drivers that
  182. need it. You only need to select this explicitly to support driver
  183. modules that aren't part of this kernel tree.
  184. config SPI_BUTTERFLY
  185. tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
  186. depends on PARPORT
  187. select SPI_BITBANG
  188. help
  189. This uses a custom parallel port cable to connect to an AVR
  190. Butterfly <http://www.atmel.com/products/avr/butterfly>, an
  191. inexpensive battery powered microcontroller evaluation board.
  192. This same cable can be used to flash new firmware.
  193. config SPI_CADENCE
  194. tristate "Cadence SPI controller"
  195. help
  196. This selects the Cadence SPI controller master driver
  197. used by Xilinx Zynq and ZynqMP.
  198. config SPI_CADENCE_QUADSPI
  199. tristate "Cadence Quad SPI controller"
  200. depends on OF && (ARM || ARM64 || X86 || COMPILE_TEST)
  201. help
  202. Enable support for the Cadence Quad SPI Flash controller.
  203. Cadence QSPI is a specialized controller for connecting an SPI
  204. Flash over 1/2/4-bit wide bus. Enable this option if you have a
  205. device with a Cadence QSPI controller and want to access the
  206. Flash as an MTD device.
  207. config SPI_CADENCE_XSPI
  208. tristate "Cadence XSPI controller"
  209. depends on (OF || COMPILE_TEST) && HAS_IOMEM
  210. depends on SPI_MEM
  211. help
  212. Enable support for the Cadence XSPI Flash controller.
  213. Cadence XSPI is a specialized controller for connecting an SPI
  214. Flash over upto 8bit wide bus. Enable this option if you have a
  215. device with a Cadence XSPI controller and want to access the
  216. Flash as an MTD device.
  217. config SPI_CLPS711X
  218. tristate "CLPS711X host SPI controller"
  219. depends on ARCH_CLPS711X || COMPILE_TEST
  220. help
  221. This enables dedicated general purpose SPI/Microwire1-compatible
  222. master mode interface (SSI1) for CLPS711X-based CPUs.
  223. config SPI_COLDFIRE_QSPI
  224. tristate "Freescale Coldfire QSPI controller"
  225. depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
  226. help
  227. This enables support for the Coldfire QSPI controller in master
  228. mode.
  229. config SPI_DAVINCI
  230. tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
  231. depends on ARCH_DAVINCI || ARCH_KEYSTONE
  232. select SPI_BITBANG
  233. help
  234. SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
  235. config SPI_DESIGNWARE
  236. tristate "DesignWare SPI controller core support"
  237. imply SPI_MEM
  238. help
  239. general driver for SPI controller core from DesignWare
  240. if SPI_DESIGNWARE
  241. config SPI_DW_DMA
  242. bool "DMA support for DW SPI controller"
  243. config SPI_DW_PCI
  244. tristate "PCI interface driver for DW SPI core"
  245. depends on PCI
  246. config SPI_DW_MMIO
  247. tristate "Memory-mapped io interface driver for DW SPI core"
  248. depends on HAS_IOMEM
  249. config SPI_DW_BT1
  250. tristate "Baikal-T1 SPI driver for DW SPI core"
  251. depends on MIPS_BAIKAL_T1 || COMPILE_TEST
  252. select MULTIPLEXER
  253. help
  254. Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI
  255. controllers. Two of them are pretty much normal: with IRQ, DMA,
  256. FIFOs of 64 words depth, 4x CSs, but the third one as being a
  257. part of the Baikal-T1 System Boot Controller has got a very
  258. limited resources: no IRQ, no DMA, only a single native
  259. chip-select and Tx/Rx FIFO with just 8 words depth available.
  260. The later one is normally connected to an external SPI-nor flash
  261. of 128Mb (in general can be of bigger size).
  262. config SPI_DW_BT1_DIRMAP
  263. bool "Directly mapped Baikal-T1 Boot SPI flash support"
  264. depends on SPI_DW_BT1
  265. help
  266. Directly mapped SPI flash memory is an interface specific to the
  267. Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which
  268. can be used to access a peripheral memory device just by
  269. reading/writing data from/to it. Note that the system APB bus
  270. will stall during each IO from/to the dirmap region until the
  271. operation is finished. So try not to use it concurrently with
  272. time-critical tasks (like the SPI memory operations implemented
  273. in this driver).
  274. endif
  275. config SPI_DLN2
  276. tristate "Diolan DLN-2 USB SPI adapter"
  277. depends on MFD_DLN2
  278. help
  279. If you say yes to this option, support will be included for Diolan
  280. DLN2, a USB to SPI interface.
  281. This driver can also be built as a module. If so, the module
  282. will be called spi-dln2.
  283. config SPI_EP93XX
  284. tristate "Cirrus Logic EP93xx SPI controller"
  285. depends on ARCH_EP93XX || COMPILE_TEST
  286. help
  287. This enables using the Cirrus EP93xx SPI controller in master
  288. mode.
  289. config SPI_FALCON
  290. bool "Falcon SPI controller support"
  291. depends on SOC_FALCON
  292. help
  293. The external bus unit (EBU) found on the FALC-ON SoC has SPI
  294. emulation that is designed for serial flash access. This driver
  295. has only been tested with m25p80 type chips. The hardware has no
  296. support for other types of SPI peripherals.
  297. config SPI_FSI
  298. tristate "FSI SPI driver"
  299. depends on FSI
  300. help
  301. This enables support for the driver for FSI bus attached SPI
  302. controllers.
  303. config SPI_FSL_LPSPI
  304. tristate "Freescale i.MX LPSPI controller"
  305. depends on ARCH_MXC || COMPILE_TEST
  306. help
  307. This enables Freescale i.MX LPSPI controllers in master mode.
  308. config SPI_FSL_QUADSPI
  309. tristate "Freescale QSPI controller"
  310. depends on ARCH_MXC || SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST
  311. depends on HAS_IOMEM
  312. help
  313. This enables support for the Quad SPI controller in master mode.
  314. Up to four flash chips can be connected on two buses with two
  315. chipselects each.
  316. This controller does not support generic SPI messages. It only
  317. supports the high-level SPI memory interface.
  318. config SPI_GXP
  319. tristate "GXP SPI driver"
  320. depends on ARCH_HPE || COMPILE_TEST
  321. help
  322. This enables support for the driver for GXP bus attached SPI
  323. controllers.
  324. config SPI_HISI_KUNPENG
  325. tristate "HiSilicon SPI Controller for Kunpeng SoCs"
  326. depends on (ARM64 && ACPI) || COMPILE_TEST
  327. help
  328. This enables support for HiSilicon SPI controller found on
  329. Kunpeng SoCs.
  330. This driver can also be built as a module. If so, the module
  331. will be called hisi-kunpeng-spi.
  332. config SPI_HISI_SFC_V3XX
  333. tristate "HiSilicon SPI NOR Flash Controller for Hi16XX chipsets"
  334. depends on (ARM64 && ACPI) || COMPILE_TEST
  335. depends on HAS_IOMEM
  336. help
  337. This enables support for HiSilicon v3xx SPI NOR flash controller
  338. found in hi16xx chipsets.
  339. config SPI_NXP_FLEXSPI
  340. tristate "NXP Flex SPI controller"
  341. depends on ARCH_LAYERSCAPE || HAS_IOMEM
  342. help
  343. This enables support for the Flex SPI controller in master mode.
  344. Up to four slave devices can be connected on two buses with two
  345. chipselects each.
  346. This controller does not support generic SPI messages and only
  347. supports the high-level SPI memory interface.
  348. config SPI_GPIO
  349. tristate "GPIO-based bitbanging SPI Master"
  350. depends on GPIOLIB || COMPILE_TEST
  351. select SPI_BITBANG
  352. help
  353. This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
  354. interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
  355. slaves connected to a bus using this driver are configured as usual,
  356. except that the spi_board_info.controller_data holds the GPIO number
  357. for the chipselect used by this controller driver.
  358. Note that this driver often won't achieve even 1 Mbit/sec speeds,
  359. making it unusually slow for SPI. If your platform can inline
  360. GPIO operations, you should be able to leverage that for better
  361. speed with a custom version of this driver; see the source code.
  362. config SPI_IMG_SPFI
  363. tristate "IMG SPFI controller"
  364. depends on MIPS || COMPILE_TEST
  365. help
  366. This enables support for the SPFI master controller found on
  367. IMG SoCs.
  368. config SPI_IMX
  369. tristate "Freescale i.MX SPI controllers"
  370. depends on ARCH_MXC || COMPILE_TEST
  371. help
  372. This enables support for the Freescale i.MX SPI controllers.
  373. config SPI_INGENIC
  374. tristate "Ingenic SoCs SPI controller"
  375. depends on MACH_INGENIC || COMPILE_TEST
  376. help
  377. This enables support for the Ingenic SoCs SPI controller.
  378. To compile this driver as a module, choose M here: the module
  379. will be called spi-ingenic.
  380. config SPI_INTEL
  381. tristate
  382. config SPI_INTEL_PCI
  383. tristate "Intel PCH/PCU SPI flash PCI driver (DANGEROUS)"
  384. depends on PCI
  385. depends on X86 || COMPILE_TEST
  386. depends on SPI_MEM
  387. select SPI_INTEL
  388. help
  389. This enables PCI support for the Intel PCH/PCU SPI controller in
  390. master mode. This controller is present in modern Intel hardware
  391. and is used to hold BIOS and other persistent settings. Using
  392. this driver it is possible to upgrade BIOS directly from Linux.
  393. Say N here unless you know what you are doing. Overwriting the
  394. SPI flash may render the system unbootable.
  395. To compile this driver as a module, choose M here: the module
  396. will be called spi-intel-pci.
  397. config SPI_INTEL_PLATFORM
  398. tristate "Intel PCH/PCU SPI flash platform driver (DANGEROUS)"
  399. depends on X86 || COMPILE_TEST
  400. depends on SPI_MEM
  401. select SPI_INTEL
  402. help
  403. This enables platform support for the Intel PCH/PCU SPI
  404. controller in master mode. This controller is present in modern
  405. Intel hardware and is used to hold BIOS and other persistent
  406. settings. Using this driver it is possible to upgrade BIOS
  407. directly from Linux.
  408. Say N here unless you know what you are doing. Overwriting the
  409. SPI flash may render the system unbootable.
  410. To compile this driver as a module, choose M here: the module
  411. will be called spi-intel-platform.
  412. config SPI_JCORE
  413. tristate "J-Core SPI Master"
  414. depends on OF && (SUPERH || COMPILE_TEST)
  415. help
  416. This enables support for the SPI master controller in the J-Core
  417. synthesizable, open source SoC.
  418. config SPI_LM70_LLP
  419. tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
  420. depends on PARPORT
  421. select SPI_BITBANG
  422. help
  423. This driver supports the NS LM70 LLP Evaluation Board,
  424. which interfaces to an LM70 temperature sensor using
  425. a parallel port.
  426. config SPI_LP8841_RTC
  427. tristate "ICP DAS LP-8841 SPI Controller for RTC"
  428. depends on MACH_PXA27X_DT || COMPILE_TEST
  429. help
  430. This driver provides an SPI master device to drive Maxim
  431. DS-1302 real time clock.
  432. Say N here unless you plan to run the kernel on an ICP DAS
  433. LP-8x4x industrial computer.
  434. config SPI_MPC52xx
  435. tristate "Freescale MPC52xx SPI (non-PSC) controller support"
  436. depends on PPC_MPC52xx
  437. help
  438. This drivers supports the MPC52xx SPI controller in master SPI
  439. mode.
  440. config SPI_MPC52xx_PSC
  441. tristate "Freescale MPC52xx PSC SPI controller"
  442. depends on PPC_MPC52xx
  443. help
  444. This enables using the Freescale MPC52xx Programmable Serial
  445. Controller in master SPI mode.
  446. config SPI_MPC512x_PSC
  447. tristate "Freescale MPC512x PSC SPI controller"
  448. depends on PPC_MPC512x
  449. help
  450. This enables using the Freescale MPC5121 Programmable Serial
  451. Controller in SPI master mode.
  452. config SPI_FSL_LIB
  453. tristate
  454. depends on OF
  455. config SPI_FSL_CPM
  456. tristate
  457. depends on FSL_SOC
  458. config SPI_FSL_SPI
  459. tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller"
  460. depends on OF
  461. select SPI_FSL_LIB
  462. select SPI_FSL_CPM if FSL_SOC
  463. help
  464. This enables using the Freescale SPI controllers in master mode.
  465. MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
  466. MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
  467. This also enables using the Aeroflex Gaisler GRLIB SPI controller in
  468. master mode.
  469. config SPI_FSL_DSPI
  470. tristate "Freescale DSPI controller"
  471. select REGMAP_MMIO
  472. depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || M5441x || COMPILE_TEST
  473. help
  474. This enables support for the Freescale DSPI controller in master
  475. mode. VF610, LS1021A and ColdFire platforms uses the controller.
  476. config SPI_FSL_ESPI
  477. tristate "Freescale eSPI controller"
  478. depends on FSL_SOC
  479. help
  480. This enables using the Freescale eSPI controllers in master mode.
  481. From MPC8536, 85xx platform uses the controller, and all P10xx,
  482. P20xx, P30xx,P40xx, P50xx uses this controller.
  483. config SPI_MESON_SPICC
  484. tristate "Amlogic Meson SPICC controller"
  485. depends on COMMON_CLK
  486. depends on ARCH_MESON || COMPILE_TEST
  487. help
  488. This enables master mode support for the SPICC (SPI communication
  489. controller) available in Amlogic Meson SoCs.
  490. config SPI_MESON_SPIFC
  491. tristate "Amlogic Meson SPIFC controller"
  492. depends on ARCH_MESON || COMPILE_TEST
  493. select REGMAP_MMIO
  494. help
  495. This enables master mode support for the SPIFC (SPI flash
  496. controller) available in Amlogic Meson SoCs.
  497. config SPI_MICROCHIP_CORE
  498. tristate "Microchip FPGA SPI controllers"
  499. depends on SPI_MASTER
  500. help
  501. This enables the SPI driver for Microchip FPGA SPI controllers.
  502. Say Y or M here if you want to use the "hard" controllers on
  503. PolarFire SoC.
  504. If built as a module, it will be called spi-microchip-core.
  505. config SPI_MICROCHIP_CORE_QSPI
  506. tristate "Microchip FPGA QSPI controllers"
  507. depends on SPI_MASTER
  508. help
  509. This enables the QSPI driver for Microchip FPGA QSPI controllers.
  510. Say Y or M here if you want to use the QSPI controllers on
  511. PolarFire SoC.
  512. If built as a module, it will be called spi-microchip-core-qspi.
  513. config SPI_MT65XX
  514. tristate "MediaTek SPI controller"
  515. depends on ARCH_MEDIATEK || COMPILE_TEST
  516. help
  517. This selects the MediaTek(R) SPI bus driver.
  518. If you want to use MediaTek(R) SPI interface,
  519. say Y or M here.If you are not sure, say N.
  520. SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs.
  521. config SPI_MT7621
  522. tristate "MediaTek MT7621 SPI Controller"
  523. depends on RALINK || COMPILE_TEST
  524. help
  525. This selects a driver for the MediaTek MT7621 SPI Controller.
  526. config SPI_MTK_NOR
  527. tristate "MediaTek SPI NOR controller"
  528. depends on ARCH_MEDIATEK || COMPILE_TEST
  529. help
  530. This enables support for SPI NOR controller found on MediaTek
  531. ARM SoCs. This is a controller specifically for SPI NOR flash.
  532. It can perform generic SPI transfers up to 6 bytes via generic
  533. SPI interface as well as several SPI NOR specific instructions
  534. via SPI MEM interface.
  535. config SPI_MTK_SNFI
  536. tristate "MediaTek SPI NAND Flash Interface"
  537. depends on ARCH_MEDIATEK || COMPILE_TEST
  538. depends on MTD_NAND_ECC_MEDIATEK
  539. help
  540. This enables support for SPI-NAND mode on the MediaTek NAND
  541. Flash Interface found on MediaTek ARM SoCs. This controller
  542. is implemented as a SPI-MEM controller with pipelined ECC
  543. capcability.
  544. config SPI_NPCM_FIU
  545. tristate "Nuvoton NPCM FLASH Interface Unit"
  546. depends on ARCH_NPCM || COMPILE_TEST
  547. depends on OF && HAS_IOMEM
  548. help
  549. This enables support for the Flash Interface Unit SPI controller
  550. in master mode.
  551. This driver does not support generic SPI. The implementation only
  552. supports spi-mem interface.
  553. config SPI_NPCM_PSPI
  554. tristate "Nuvoton NPCM PSPI Controller"
  555. depends on ARCH_NPCM || COMPILE_TEST
  556. help
  557. This driver provides support for Nuvoton NPCM BMC
  558. Peripheral SPI controller in master mode.
  559. config SPI_LANTIQ_SSC
  560. tristate "Lantiq SSC SPI controller"
  561. depends on LANTIQ || X86 || COMPILE_TEST
  562. help
  563. This driver supports the Lantiq SSC SPI controller in master
  564. mode. This controller is found on Intel (former Lantiq) SoCs like
  565. the Danube, Falcon, xRX200, xRX300, Lightning Mountain.
  566. config SPI_OC_TINY
  567. tristate "OpenCores tiny SPI"
  568. depends on GPIOLIB || COMPILE_TEST
  569. select SPI_BITBANG
  570. help
  571. This is the driver for OpenCores tiny SPI master controller.
  572. config SPI_OCTEON
  573. tristate "Cavium OCTEON SPI controller"
  574. depends on CAVIUM_OCTEON_SOC
  575. help
  576. SPI host driver for the hardware found on some Cavium OCTEON
  577. SOCs.
  578. config SPI_OMAP_UWIRE
  579. tristate "OMAP1 MicroWire"
  580. depends on ARCH_OMAP1 || (ARM && COMPILE_TEST)
  581. select SPI_BITBANG
  582. help
  583. This hooks up to the MicroWire controller on OMAP1 chips.
  584. config SPI_OMAP24XX
  585. tristate "McSPI driver for OMAP"
  586. depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST
  587. select SG_SPLIT
  588. help
  589. SPI master controller for OMAP24XX and later Multichannel SPI
  590. (McSPI) modules.
  591. config SPI_TI_QSPI
  592. tristate "DRA7xxx QSPI controller support"
  593. depends on ARCH_OMAP2PLUS || COMPILE_TEST
  594. help
  595. QSPI master controller for DRA7xxx used for flash devices.
  596. This device supports single, dual and quad read support, while
  597. it only supports single write mode.
  598. config SPI_OMAP_100K
  599. tristate "OMAP SPI 100K"
  600. depends on ARCH_OMAP850 || ARCH_OMAP730 || COMPILE_TEST
  601. help
  602. OMAP SPI 100K master controller for omap7xx boards.
  603. config SPI_ORION
  604. tristate "Orion SPI master"
  605. depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST
  606. help
  607. This enables using the SPI master controller on the Orion
  608. and MVEBU chips.
  609. config SPI_PIC32
  610. tristate "Microchip PIC32 series SPI"
  611. depends on MACH_PIC32 || COMPILE_TEST
  612. help
  613. SPI driver for Microchip PIC32 SPI master controller.
  614. config SPI_PIC32_SQI
  615. tristate "Microchip PIC32 Quad SPI driver"
  616. depends on MACH_PIC32 || COMPILE_TEST
  617. help
  618. SPI driver for PIC32 Quad SPI controller.
  619. config SPI_PL022
  620. tristate "ARM AMBA PL022 SSP controller"
  621. depends on ARM_AMBA
  622. default y if ARCH_REALVIEW
  623. default y if INTEGRATOR_IMPD1
  624. default y if ARCH_VERSATILE
  625. help
  626. This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
  627. controller. If you have an embedded system with an AMBA(R)
  628. bus and a PL022 controller, say Y or M here.
  629. config SPI_PPC4xx
  630. tristate "PPC4xx SPI Controller"
  631. depends on PPC32 && 4xx
  632. select SPI_BITBANG
  633. help
  634. This selects a driver for the PPC4xx SPI Controller.
  635. config SPI_PXA2XX
  636. tristate "PXA2xx SSP SPI master"
  637. depends on ARCH_PXA || ARCH_MMP || PCI || ACPI || COMPILE_TEST
  638. select PXA_SSP if ARCH_PXA || ARCH_MMP
  639. help
  640. This enables using a PXA2xx or Sodaville SSP port as a SPI master
  641. controller. The driver can be configured to use any SSP port and
  642. additional documentation can be found a Documentation/spi/pxa2xx.rst.
  643. config SPI_PXA2XX_PCI
  644. def_tristate SPI_PXA2XX && PCI && COMMON_CLK
  645. config SPI_ROCKCHIP
  646. tristate "Rockchip SPI controller driver"
  647. help
  648. This selects a driver for Rockchip SPI controller.
  649. If you say yes to this option, support will be included for
  650. RK3066, RK3188 and RK3288 families of SPI controller.
  651. Rockchip SPI controller support DMA transport and PIO mode.
  652. The main usecase of this controller is to use spi flash as boot
  653. device.
  654. config SPI_ROCKCHIP_SFC
  655. tristate "Rockchip Serial Flash Controller (SFC)"
  656. depends on ARCH_ROCKCHIP || COMPILE_TEST
  657. depends on HAS_IOMEM && HAS_DMA
  658. help
  659. This enables support for Rockchip serial flash controller. This
  660. is a specialized controller used to access SPI flash on some
  661. Rockchip SOCs.
  662. ROCKCHIP SFC supports DMA and PIO modes. When DMA is not available,
  663. the driver automatically falls back to PIO mode.
  664. config SPI_RB4XX
  665. tristate "Mikrotik RB4XX SPI master"
  666. depends on SPI_MASTER && ATH79
  667. help
  668. SPI controller driver for the Mikrotik RB4xx series boards.
  669. config SPI_RPCIF
  670. tristate "Renesas RPC-IF SPI driver"
  671. depends on RENESAS_RPCIF
  672. help
  673. SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF.
  674. config SPI_RSPI
  675. tristate "Renesas RSPI/QSPI controller"
  676. depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
  677. help
  678. SPI driver for Renesas RSPI and QSPI blocks.
  679. config SPI_QCOM_QSPI
  680. tristate "QTI QSPI controller"
  681. depends on ARCH_QCOM
  682. help
  683. QSPI(Quad SPI) driver for Qualcomm QSPI controller.
  684. config SPI_QUP
  685. tristate "Qualcomm SPI controller with QUP interface"
  686. depends on ARCH_QCOM || COMPILE_TEST
  687. help
  688. Qualcomm Universal Peripheral (QUP) core is an AHB slave that
  689. provides a common data path (an output FIFO and an input FIFO)
  690. for serial peripheral interface (SPI) mini-core. SPI in master
  691. mode supports up to 50MHz, up to four chip selects, programmable
  692. data path from 4 bits to 32 bits and numerous protocol variants.
  693. This driver can also be built as a module. If so, the module
  694. will be called spi_qup.
  695. config SPI_QCOM_GENI
  696. tristate "Qualcomm GENI based SPI controller"
  697. depends on QCOM_GENI_SE
  698. help
  699. This driver supports GENI serial engine based SPI controller in
  700. master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
  701. yes to this option, support will be included for the built-in SPI
  702. interface on the Qualcomm Technologies Inc.'s SoCs.
  703. This driver can also be built as a module. If so, the module
  704. will be called spi-geni-qcom.
  705. config Q2SPI_MSM_GENI
  706. tristate "Qualcomm Technologies Inc.'s GENI based Q2SPI controller"
  707. depends on QCOM_GENI_SE
  708. help
  709. This driver supports GENI serial engine based Q2SPI controller in
  710. master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
  711. yes to this option, support will be included for the built-in Q2SPI
  712. interface on the Qualcomm Technologies Inc.'s SoCs.
  713. This driver can also be built as a module. If so, the module
  714. will be called q2spi-geni.
  715. config SPI_MSM_GENI
  716. tristate "Qualcomm Technologies Inc.'s GENI based SPI controller"
  717. depends on QCOM_GENI_SE
  718. help
  719. This driver supports GENI serial engine based SPI controller in
  720. master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
  721. yes to this option, support will be included for the built-in SPI
  722. interface on the Qualcomm Technologies Inc.'s SoCs.
  723. This driver can also be built as a module. If so, the module
  724. will be called spi-msm-geni.
  725. config VIRTIO_SPI
  726. tristate "VirtIO SPI driver"
  727. depends on VIRTIO
  728. help
  729. This spi driver for virtio. It can be used on virtual machine.
  730. Say Y if you want to support virtual SPI for the build-in SPI
  731. interface. This driver can also be built as a module. If so,
  732. the module will be called virtio-spi.
  733. config SPI_S3C24XX
  734. tristate "Samsung S3C24XX series SPI"
  735. depends on ARCH_S3C24XX
  736. select SPI_BITBANG
  737. help
  738. SPI driver for Samsung S3C24XX series ARM SoCs
  739. config SPI_S3C24XX_FIQ
  740. bool "S3C24XX driver with FIQ pseudo-DMA"
  741. depends on SPI_S3C24XX
  742. select FIQ
  743. help
  744. Enable FIQ support for the S3C24XX SPI driver to provide pseudo
  745. DMA by using the fast-interrupt request framework, This allows
  746. the driver to get DMA-like performance when there are either
  747. no free DMA channels, or when doing transfers that required both
  748. TX and RX data paths.
  749. config SPI_S3C64XX
  750. tristate "Samsung S3C64XX/Exynos SoC series type SPI"
  751. depends on (PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST)
  752. help
  753. SPI driver for Samsung S3C64XX, S5Pv210 and Exynos SoCs.
  754. Choose Y/M here only if you build for such Samsung SoC.
  755. config SPI_SC18IS602
  756. tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"
  757. depends on I2C
  758. help
  759. SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.
  760. config SPI_SH_MSIOF
  761. tristate "SuperH MSIOF SPI controller"
  762. depends on HAVE_CLK
  763. depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
  764. help
  765. SPI driver for SuperH and SH Mobile MSIOF blocks.
  766. config SPI_SH
  767. tristate "SuperH SPI controller"
  768. depends on SUPERH || COMPILE_TEST
  769. help
  770. SPI driver for SuperH SPI blocks.
  771. config SPI_SH_SCI
  772. tristate "SuperH SCI SPI controller"
  773. depends on SUPERH
  774. select SPI_BITBANG
  775. help
  776. SPI driver for SuperH SCI blocks.
  777. config SPI_SH_HSPI
  778. tristate "SuperH HSPI controller"
  779. depends on ARCH_RENESAS || COMPILE_TEST
  780. help
  781. SPI driver for SuperH HSPI blocks.
  782. config SPI_SIFIVE
  783. tristate "SiFive SPI controller"
  784. depends on HAS_IOMEM
  785. help
  786. This exposes the SPI controller IP from SiFive.
  787. config SPI_SLAVE_MT27XX
  788. tristate "MediaTek SPI slave device"
  789. depends on ARCH_MEDIATEK || COMPILE_TEST
  790. depends on SPI_SLAVE
  791. help
  792. This selects the MediaTek(R) SPI slave device driver.
  793. If you want to use MediaTek(R) SPI slave interface,
  794. say Y or M here.If you are not sure, say N.
  795. SPI slave drivers for Mediatek MT27XX series ARM SoCs.
  796. config SPI_SPRD
  797. tristate "Spreadtrum SPI controller"
  798. depends on ARCH_SPRD || COMPILE_TEST
  799. help
  800. SPI driver for Spreadtrum SoCs.
  801. config SPI_SPRD_ADI
  802. tristate "Spreadtrum ADI controller"
  803. depends on ARCH_SPRD || COMPILE_TEST
  804. depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK)
  805. help
  806. ADI driver based on SPI for Spreadtrum SoCs.
  807. config SPI_STM32
  808. tristate "STMicroelectronics STM32 SPI controller"
  809. depends on ARCH_STM32 || COMPILE_TEST
  810. help
  811. SPI driver for STMicroelectronics STM32 SoCs.
  812. STM32 SPI controller supports DMA and PIO modes. When DMA
  813. is not available, the driver automatically falls back to
  814. PIO mode.
  815. config SPI_STM32_QSPI
  816. tristate "STMicroelectronics STM32 QUAD SPI controller"
  817. depends on ARCH_STM32 || COMPILE_TEST
  818. depends on OF
  819. depends on SPI_MEM
  820. help
  821. This enables support for the Quad SPI controller in master mode.
  822. This driver does not support generic SPI. The implementation only
  823. supports spi-mem interface.
  824. config SPI_ST_SSC4
  825. tristate "STMicroelectronics SPI SSC-based driver"
  826. depends on ARCH_STI || COMPILE_TEST
  827. help
  828. STMicroelectronics SoCs support for SPI. If you say yes to
  829. this option, support will be included for the SSC driven SPI.
  830. config SPI_SUN4I
  831. tristate "Allwinner A10 SoCs SPI controller"
  832. depends on ARCH_SUNXI || COMPILE_TEST
  833. help
  834. SPI driver for Allwinner sun4i, sun5i and sun7i SoCs
  835. config SPI_SUN6I
  836. tristate "Allwinner A31 SPI controller"
  837. depends on ARCH_SUNXI || COMPILE_TEST
  838. depends on RESET_CONTROLLER
  839. help
  840. This enables using the SPI controller on the Allwinner A31 SoCs.
  841. config SPI_SUNPLUS_SP7021
  842. tristate "Sunplus SP7021 SPI controller"
  843. depends on SOC_SP7021 || COMPILE_TEST
  844. help
  845. This enables Sunplus SP7021 SPI controller driver on the SP7021 SoCs.
  846. This driver can also be built as a module. If so, the module will be
  847. called as spi-sunplus-sp7021.
  848. If you have a Sunplus SP7021 platform say Y here.
  849. If unsure, say N.
  850. config SPI_SYNQUACER
  851. tristate "Socionext's SynQuacer HighSpeed SPI controller"
  852. depends on ARCH_SYNQUACER || COMPILE_TEST
  853. help
  854. SPI driver for Socionext's High speed SPI controller which provides
  855. various operating modes for interfacing to serial peripheral devices
  856. that use the de-facto standard SPI protocol.
  857. It also supports the new dual-bit and quad-bit SPI protocol.
  858. config SPI_MXIC
  859. tristate "Macronix MX25F0A SPI controller"
  860. depends on SPI_MASTER
  861. imply MTD_NAND_ECC_MXIC
  862. help
  863. This selects the Macronix MX25F0A SPI controller driver.
  864. config SPI_MXS
  865. tristate "Freescale MXS SPI controller"
  866. depends on ARCH_MXS
  867. select STMP_DEVICE
  868. help
  869. SPI driver for Freescale MXS devices.
  870. config SPI_TEGRA210_QUAD
  871. tristate "NVIDIA Tegra QSPI Controller"
  872. depends on ARCH_TEGRA || COMPILE_TEST
  873. depends on RESET_CONTROLLER
  874. help
  875. QSPI driver for NVIDIA Tegra QSPI Controller interface. This
  876. controller is different from the SPI controller and is available
  877. on Tegra SoCs starting from Tegra210.
  878. config SPI_TEGRA114
  879. tristate "NVIDIA Tegra114 SPI Controller"
  880. depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
  881. depends on RESET_CONTROLLER
  882. help
  883. SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
  884. is different than the older SoCs SPI controller and also register interface
  885. get changed with this controller.
  886. config SPI_TEGRA20_SFLASH
  887. tristate "Nvidia Tegra20 Serial flash Controller"
  888. depends on ARCH_TEGRA || COMPILE_TEST
  889. depends on RESET_CONTROLLER
  890. help
  891. SPI driver for Nvidia Tegra20 Serial flash Controller interface.
  892. The main usecase of this controller is to use spi flash as boot
  893. device.
  894. config SPI_TEGRA20_SLINK
  895. tristate "Nvidia Tegra20/Tegra30 SLINK Controller"
  896. depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
  897. depends on RESET_CONTROLLER
  898. help
  899. SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.
  900. config SPI_THUNDERX
  901. tristate "Cavium ThunderX SPI controller"
  902. depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
  903. help
  904. SPI host driver for the hardware found on Cavium ThunderX
  905. SOCs.
  906. config SPI_TOPCLIFF_PCH
  907. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
  908. depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
  909. help
  910. SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
  911. used in some x86 embedded processors.
  912. This driver also supports the ML7213/ML7223/ML7831, a companion chip
  913. for the Atom E6xx series and compatible with the Intel EG20T PCH.
  914. config SPI_UNIPHIER
  915. tristate "Socionext UniPhier SPI Controller"
  916. depends on (ARCH_UNIPHIER || COMPILE_TEST) && OF
  917. depends on HAS_IOMEM
  918. help
  919. This enables a driver for the Socionext UniPhier SoC SCSSI SPI controller.
  920. UniPhier SoCs have SCSSI and MCSSI SPI controllers.
  921. Every UniPhier SoC has SCSSI which supports single channel.
  922. Older UniPhier Pro4/Pro5 also has MCSSI which support multiple channels.
  923. This driver supports SCSSI only.
  924. If your SoC supports SCSSI, say Y here.
  925. config SPI_XCOMM
  926. tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
  927. depends on I2C
  928. help
  929. Support for the SPI-I2C bridge found on the Analog Devices
  930. AD-FMCOMMS1-EBZ board.
  931. config SPI_XILINX
  932. tristate "Xilinx SPI controller common module"
  933. depends on HAS_IOMEM
  934. select SPI_BITBANG
  935. help
  936. This exposes the SPI controller IP from the Xilinx EDK.
  937. See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
  938. Product Specification document (DS464) for hardware details.
  939. Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
  940. config SPI_XLP
  941. tristate "Cavium ThunderX2 SPI controller driver"
  942. depends on ARCH_THUNDER2 || COMPILE_TEST
  943. help
  944. Enable support for the SPI controller on the Cavium ThunderX2.
  945. (Originally on Netlogic XLP SoCs.)
  946. If you have a Cavium ThunderX2 platform say Y here.
  947. If unsure, say N.
  948. config SPI_XTENSA_XTFPGA
  949. tristate "Xtensa SPI controller for xtfpga"
  950. depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST
  951. select SPI_BITBANG
  952. help
  953. SPI driver for xtfpga SPI master controller.
  954. This simple SPI master controller is built into xtfpga bitstreams
  955. and is used to control daughterboard audio codec. It always transfers
  956. 16 bit words in SPI mode 0, automatically asserting CS on transfer
  957. start and deasserting on end.
  958. config SPI_ZYNQ_QSPI
  959. tristate "Xilinx Zynq QSPI controller"
  960. depends on ARCH_ZYNQ || COMPILE_TEST
  961. depends on SPI_MEM
  962. help
  963. This enables support for the Zynq Quad SPI controller
  964. in master mode.
  965. This controller only supports SPI memory interface.
  966. config SPI_ZYNQMP_GQSPI
  967. tristate "Xilinx ZynqMP GQSPI controller"
  968. depends on (SPI_MASTER && HAS_DMA) || COMPILE_TEST
  969. help
  970. Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
  971. config SPI_AMD
  972. tristate "AMD SPI controller"
  973. depends on SPI_MASTER || COMPILE_TEST
  974. help
  975. Enables SPI controller driver for AMD SoC.
  976. #
  977. # Add new SPI master controllers in alphabetical order above this line
  978. #
  979. comment "SPI Multiplexer support"
  980. config SPI_MUX
  981. tristate "SPI multiplexer support"
  982. select MULTIPLEXER
  983. help
  984. This adds support for SPI multiplexers. Each SPI mux will be
  985. accessible as a SPI controller, the devices behind the mux will appear
  986. to be chip selects on this controller. It is still necessary to
  987. select one or more specific mux-controller drivers.
  988. #
  989. # There are lots of SPI device types, with sensors and memory
  990. # being probably the most widely used ones.
  991. #
  992. comment "SPI Protocol Masters"
  993. config SPI_SPIDEV
  994. tristate "User mode SPI device driver support"
  995. help
  996. This supports user mode SPI protocol drivers.
  997. Note that this application programming interface is EXPERIMENTAL
  998. and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
  999. config SPI_LOOPBACK_TEST
  1000. tristate "spi loopback test framework support"
  1001. depends on m
  1002. help
  1003. This enables the SPI loopback testing framework driver
  1004. primarily used for development of spi_master drivers
  1005. and to detect regressions
  1006. config SPI_TLE62X0
  1007. tristate "Infineon TLE62X0 (for power switching)"
  1008. depends on SYSFS
  1009. help
  1010. SPI driver for Infineon TLE62X0 series line driver chips,
  1011. such as the TLE6220, TLE6230 and TLE6240. This provides a
  1012. sysfs interface, with each line presented as a kind of GPIO
  1013. exposing both switch control and diagnostic feedback.
  1014. #
  1015. # Add new SPI protocol masters in alphabetical order above this line
  1016. #
  1017. endif # SPI_MASTER
  1018. #
  1019. # SLAVE side ... listening to other SPI masters
  1020. #
  1021. config SPI_SLAVE
  1022. bool "SPI slave protocol handlers"
  1023. help
  1024. If your system has a slave-capable SPI controller, you can enable
  1025. slave protocol handlers.
  1026. if SPI_SLAVE
  1027. config SPI_SLAVE_TIME
  1028. tristate "SPI slave handler reporting boot up time"
  1029. help
  1030. SPI slave handler responding with the time of reception of the last
  1031. SPI message.
  1032. config SPI_SLAVE_SYSTEM_CONTROL
  1033. tristate "SPI slave handler controlling system state"
  1034. help
  1035. SPI slave handler to allow remote control of system reboot, power
  1036. off, halt, and suspend.
  1037. endif # SPI_SLAVE
  1038. config SPI_DYNAMIC
  1039. def_bool ACPI || OF_DYNAMIC || SPI_SLAVE
  1040. endif # SPI