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

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