1287 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# SPI driver configuration4#5menuconfig SPI6 bool "SPI support"7 depends on HAS_IOMEM8 help9 The "Serial Peripheral Interface" is a low level synchronous10 protocol. Chips that support SPI can have data transfer rates11 up to several tens of Mbit/sec. Chips are addressed with a12 controller and a chipselect. Most SPI slaves don't support13 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 controller17 chips, analog to digital (and d-to-a) converters, and more.18 MMC and SD cards can be accessed using SPI protocol; and for19 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 wire22 interface (select, clock, data in, data out) including Microwire23 (half duplex), SSP, SSI, and PSP. This driver framework should24 work with most such devices and controllers.25 26if SPI27 28config SPI_DEBUG29 bool "Debug support for SPI drivers"30 depends on DEBUG_KERNEL31 help32 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 microcontrollers37#38 39config SPI_MASTER40# bool "SPI Master Support"41 bool42 default SPI43 help44 If your system has an master-capable SPI controller (which45 provides the clock and chipselect), you can enable that46 controller and the protocol drivers for the SPI slave chips47 that are connected.48 49if SPI_MASTER50 51config SPI_MEM52 bool "SPI memory extension"53 help54 Enable this option if you want to enable the SPI memory extension.55 This extension is meant to simplify interaction with SPI memories56 by providing a high-level interface to send memory-like commands.57 58comment "SPI Master Controller Drivers"59 60config SPI_AIROHA_SNFI61 tristate "Airoha SPI NAND Flash Interface"62 depends on ARCH_AIROHA || COMPILE_TEST63 depends on SPI_MASTER64 select REGMAP_MMIO65 help66 This enables support for SPI-NAND mode on the Airoha NAND67 Flash Interface found on Airoha ARM SoCs. This controller68 is implemented as a SPI-MEM controller.69 70config SPI_ALTERA71 tristate "Altera SPI Controller platform driver"72 select SPI_ALTERA_CORE73 select REGMAP_MMIO74 help75 This is the driver for the Altera SPI Controller.76 77config SPI_ALTERA_CORE78 tristate "Altera SPI Controller core code" if COMPILE_TEST79 select REGMAP80 help81 "The core code for the Altera SPI Controller"82 83config SPI_ALTERA_DFL84 tristate "DFL bus driver for Altera SPI Controller"85 depends on FPGA_DFL86 select SPI_ALTERA_CORE87 help88 This is a Device Feature List (DFL) bus driver for the89 Altera SPI master controller. The SPI master is connected90 to a SPI slave to Avalon bridge in a Intel MAX BMC.91 92config SPI_AMLOGIC_SPIFC_A193 tristate "Amlogic A1 SPIFC controller"94 depends on ARCH_MESON || COMPILE_TEST95 help96 This enables master mode support for the SPIFC (SPI flash97 controller) available in Amlogic A1 (A113L SoC).98 99config SPI_AR934X100 tristate "Qualcomm Atheros AR934X/QCA95XX SPI controller driver"101 depends on ATH79 || COMPILE_TEST102 help103 This enables support for the SPI controller present on the104 Qualcomm Atheros AR934X/QCA95XX SoCs.105 106config SPI_ATH79107 tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"108 depends on ATH79 || COMPILE_TEST109 select SPI_BITBANG110 help111 This enables support for the SPI controller present on the112 Atheros AR71XX/AR724X/AR913X SoCs.113 114config SPI_ARMADA_3700115 tristate "Marvell Armada 3700 SPI Controller"116 depends on (ARCH_MVEBU && OF) || COMPILE_TEST117 help118 This enables support for the SPI controller present on the119 Marvell Armada 3700 SoCs.120 121config SPI_ASPEED_SMC122 tristate "Aspeed flash controllers in SPI mode"123 depends on ARCH_ASPEED || COMPILE_TEST124 depends on OF125 help126 This enables support for the Firmware Memory controller (FMC)127 in the Aspeed AST2600, AST2500 and AST2400 SoCs when attached128 to SPI NOR chips, and support for the SPI flash memory129 controller (SPI) for the host firmware. The implementation130 only supports SPI NOR.131 132config SPI_ATMEL133 tristate "Atmel SPI Controller"134 depends on ARCH_AT91 || COMPILE_TEST135 depends on OF136 help137 This selects a driver for the Atmel SPI Controller, present on138 many AT91 ARM chips.139 140config SPI_AT91_USART141 tristate "Atmel USART Controller SPI driver"142 depends on (ARCH_AT91 || COMPILE_TEST)143 depends on MFD_AT91_USART144 help145 This selects a driver for the AT91 USART Controller as SPI Master,146 present on AT91 and SAMA5 SoC series.147 148config SPI_ATMEL_QUADSPI149 tristate "Atmel Quad SPI Controller"150 depends on ARCH_AT91 || COMPILE_TEST151 depends on OF && HAS_IOMEM152 help153 This enables support for the Quad SPI controller in master mode.154 This driver does not support generic SPI. The implementation only155 supports spi-mem interface.156 157config SPI_AU1550158 tristate "Au1550/Au1200/Au1300 SPI Controller"159 depends on MIPS_ALCHEMY160 select SPI_BITBANG161 help162 If you say yes to this option, support will be included for the163 PSC SPI controller found on Au1550, Au1200 and Au1300 series.164 165config SPI_AXI_SPI_ENGINE166 tristate "Analog Devices AXI SPI Engine controller"167 depends on HAS_IOMEM168 help169 This enables support for the Analog Devices AXI SPI Engine SPI controller.170 It is part of the SPI Engine framework that is used in some Analog Devices171 reference designs for FPGAs.172 173config SPI_BCM2835174 tristate "BCM2835 SPI controller"175 depends on GPIOLIB176 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST177 help178 This selects a driver for the Broadcom BCM2835 SPI master.179 180 The BCM2835 contains two types of SPI master controller; the181 "universal SPI master", and the regular SPI controller. This driver182 is for the regular SPI controller. Slave mode operation is not also183 not supported.184 185config SPI_BCM2835AUX186 tristate "BCM2835 SPI auxiliary controller"187 depends on ((ARCH_BCM2835 || ARCH_BRCMSTB) && GPIOLIB) || COMPILE_TEST188 help189 This selects a driver for the Broadcom BCM2835 SPI aux master.190 191 The BCM2835 contains two types of SPI master controller; the192 "universal SPI master", and the regular SPI controller.193 This driver is for the universal/auxiliary SPI controller.194 195config SPI_BCM63XX196 tristate "Broadcom BCM63xx SPI controller"197 depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST198 help199 Enable support for the SPI controller on the Broadcom BCM63xx SoCs.200 201config SPI_BCM63XX_HSSPI202 tristate "Broadcom BCM63XX HS SPI controller driver"203 depends on BCM63XX || BMIPS_GENERIC || ARCH_BCMBCA || COMPILE_TEST204 help205 This enables support for the High Speed SPI controller present on206 newer Broadcom BCM63XX SoCs.207 208config SPI_BCM_QSPI209 tristate "Broadcom BSPI and MSPI controller support"210 depends on ARCH_BRCMSTB || ARCH_BCM || ARCH_BCM_IPROC || \211 BMIPS_GENERIC || COMPILE_TEST212 default ARCH_BCM_IPROC213 help214 Enables support for the Broadcom SPI flash and MSPI controller.215 Select this option for any one of BRCMSTB, iProc NSP and NS2 SoCs216 based platforms. This driver works for both SPI master for SPI NOR217 flash device as well as MSPI device.218 219config SPI_BCMBCA_HSSPI220 tristate "Broadcom BCMBCA HS SPI controller driver"221 depends on ARCH_BCMBCA || COMPILE_TEST222 help223 This enables support for the High Speed SPI controller present on224 newer Broadcom BCMBCA SoCs. These SoCs include an updated SPI controller225 that adds the capability to allow the driver to control chip select226 explicitly.227 228config SPI_BITBANG229 tristate "Utilities for Bitbanging SPI host controllers"230 help231 With a few GPIO pins, your system can bitbang the SPI protocol.232 Select this to get SPI support through I/O pins (GPIO, parallel233 port, etc). Or, some systems' SPI host controller drivers use234 this code to manage the per-word or per-transfer accesses to the235 hardware shift registers.236 237 This is library code, and is automatically selected by drivers that238 need it. You only need to select this explicitly to support driver239 modules that aren't part of this kernel tree.240 241config SPI_BUTTERFLY242 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"243 depends on PARPORT244 select SPI_BITBANG245 help246 This uses a custom parallel port cable to connect to an AVR247 Butterfly <http://www.atmel.com/products/avr/butterfly>, an248 inexpensive battery powered microcontroller evaluation board.249 This same cable can be used to flash new firmware.250 251config SPI_CADENCE252 tristate "Cadence SPI controller"253 help254 This selects the Cadence SPI controller master driver255 used by Xilinx Zynq and ZynqMP.256 257config SPI_CADENCE_QUADSPI258 tristate "Cadence Quad SPI controller"259 depends on OF && (ARM || ARM64 || X86 || RISCV || MIPS || COMPILE_TEST)260 help261 Enable support for the Cadence Quad SPI Flash controller.262 263 Cadence QSPI is a specialized controller for connecting an SPI264 Flash over 1/2/4-bit wide bus. Enable this option if you have a265 device with a Cadence QSPI controller and want to access the266 Flash as an MTD device.267 268config SPI_CADENCE_XSPI269 tristate "Cadence XSPI controller"270 depends on OF && HAS_IOMEM && 64BIT271 depends on SPI_MEM272 help273 Enable support for the Cadence XSPI Flash controller.274 275 Cadence XSPI is a specialized controller for connecting an SPI276 Flash over up to 8-bit wide bus. Enable this option if you have a277 device with a Cadence XSPI controller and want to access the278 Flash as an MTD device.279 280config SPI_CH341281 tristate "CH341 USB2SPI adapter"282 depends on SPI_MASTER && USB283 help284 Enables the SPI controller on the CH341a USB to serial chip285 286config SPI_CLPS711X287 tristate "CLPS711X host SPI controller"288 depends on ARCH_CLPS711X || COMPILE_TEST289 help290 This enables dedicated general purpose SPI/Microwire1-compatible291 master mode interface (SSI1) for CLPS711X-based CPUs.292 293config SPI_COLDFIRE_QSPI294 tristate "Freescale Coldfire QSPI controller"295 depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)296 help297 This enables support for the Coldfire QSPI controller in master298 mode.299 300config SPI_CS42L43301 tristate "Cirrus Logic CS42L43 SPI controller"302 depends on MFD_CS42L43 && PINCTRL_CS42L43303 select GPIO_SWNODE_UNDEFINED304 help305 This enables support for the SPI controller inside the Cirrus Logic306 CS42L43 audio codec.307 308config SPI_DAVINCI309 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"310 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST311 select SPI_BITBANG312 help313 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.314 315config SPI_DESIGNWARE316 tristate "DesignWare SPI controller core support"317 imply SPI_MEM318 help319 general driver for SPI controller core from DesignWare320 321if SPI_DESIGNWARE322 323config SPI_DW_DMA324 bool "DMA support for DW SPI controller"325 326config SPI_DW_PCI327 tristate "PCI interface driver for DW SPI core"328 depends on PCI329 330config SPI_DW_MMIO331 tristate "Memory-mapped io interface driver for DW SPI core"332 depends on HAS_IOMEM333 334config SPI_DW_BT1335 tristate "Baikal-T1 SPI driver for DW SPI core"336 depends on MIPS_BAIKAL_T1 || COMPILE_TEST337 select MULTIPLEXER338 help339 Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI340 controllers. Two of them are pretty much normal: with IRQ, DMA,341 FIFOs of 64 words depth, 4x CSs, but the third one as being a342 part of the Baikal-T1 System Boot Controller has got a very343 limited resources: no IRQ, no DMA, only a single native344 chip-select and Tx/Rx FIFO with just 8 words depth available.345 The later one is normally connected to an external SPI-nor flash346 of 128Mb (in general can be of bigger size).347 348config SPI_DW_BT1_DIRMAP349 bool "Directly mapped Baikal-T1 Boot SPI flash support"350 depends on SPI_DW_BT1351 help352 Directly mapped SPI flash memory is an interface specific to the353 Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which354 can be used to access a peripheral memory device just by355 reading/writing data from/to it. Note that the system APB bus356 will stall during each IO from/to the dirmap region until the357 operation is finished. So try not to use it concurrently with358 time-critical tasks (like the SPI memory operations implemented359 in this driver).360 361endif362 363config SPI_DLN2364 tristate "Diolan DLN-2 USB SPI adapter"365 depends on MFD_DLN2366 help367 If you say yes to this option, support will be included for Diolan368 DLN2, a USB to SPI interface.369 370 This driver can also be built as a module. If so, the module371 will be called spi-dln2.372 373config SPI_EP93XX374 tristate "Cirrus Logic EP93xx SPI controller"375 depends on ARCH_EP93XX || COMPILE_TEST376 help377 This enables using the Cirrus EP93xx SPI controller in master378 mode.379 380config SPI_FALCON381 bool "Falcon SPI controller support"382 depends on SOC_FALCON383 help384 The external bus unit (EBU) found on the FALC-ON SoC has SPI385 emulation that is designed for serial flash access. This driver386 has only been tested with m25p80 type chips. The hardware has no387 support for other types of SPI peripherals.388 389config SPI_FSI390 tristate "FSI SPI driver"391 depends on FSI392 help393 This enables support for the driver for FSI bus attached SPI394 controllers.395 396config SPI_FSL_LPSPI397 tristate "Freescale i.MX LPSPI controller"398 depends on ARCH_MXC || COMPILE_TEST399 help400 This enables Freescale i.MX LPSPI controllers in master mode.401 402config SPI_FSL_QUADSPI403 tristate "Freescale QSPI controller"404 depends on ARCH_MXC || SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST405 depends on HAS_IOMEM406 help407 This enables support for the Quad SPI controller in master mode.408 Up to four flash chips can be connected on two buses with two409 chipselects each.410 This controller does not support generic SPI messages. It only411 supports the high-level SPI memory interface.412 413config SPI_GXP414 tristate "GXP SPI driver"415 depends on ARCH_HPE || COMPILE_TEST416 help417 This enables support for the driver for GXP bus attached SPI418 controllers.419 420config SPI_HISI_KUNPENG421 tristate "HiSilicon SPI Controller for Kunpeng SoCs"422 depends on (ARM64 && ACPI) || COMPILE_TEST423 help424 This enables support for HiSilicon SPI controller found on425 Kunpeng SoCs.426 427 This driver can also be built as a module. If so, the module428 will be called hisi-kunpeng-spi.429 430config SPI_HISI_SFC_V3XX431 tristate "HiSilicon SPI NOR Flash Controller for Hi16XX chipsets"432 depends on (ARM64 && ACPI) || COMPILE_TEST433 depends on HAS_IOMEM434 help435 This enables support for HiSilicon v3xx SPI NOR flash controller436 found in hi16xx chipsets.437 438config SPI_NXP_FLEXSPI439 tristate "NXP Flex SPI controller"440 depends on ARCH_LAYERSCAPE || ARCH_MXC || COMPILE_TEST441 depends on HAS_IOMEM442 help443 This enables support for the Flex SPI controller in master mode.444 Up to four slave devices can be connected on two buses with two445 chipselects each.446 This controller does not support generic SPI messages and only447 supports the high-level SPI memory interface.448 449config SPI_GPIO450 tristate "GPIO-based bitbanging SPI Master"451 depends on GPIOLIB || COMPILE_TEST452 select SPI_BITBANG453 help454 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO455 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI456 slaves connected to a bus using this driver are configured as usual,457 except that the spi_board_info.controller_data holds the GPIO number458 for the chipselect used by this controller driver.459 460 Note that this driver often won't achieve even 1 Mbit/sec speeds,461 making it unusually slow for SPI. If your platform can inline462 GPIO operations, you should be able to leverage that for better463 speed with a custom version of this driver; see the source code.464 465config SPI_IMG_SPFI466 tristate "IMG SPFI controller"467 depends on MIPS || COMPILE_TEST468 help469 This enables support for the SPFI master controller found on470 IMG SoCs.471 472config SPI_IMX473 tristate "Freescale i.MX SPI controllers"474 depends on ARCH_MXC || COMPILE_TEST475 help476 This enables support for the Freescale i.MX SPI controllers.477 478config SPI_INGENIC479 tristate "Ingenic SoCs SPI controller"480 depends on MACH_INGENIC || COMPILE_TEST481 help482 This enables support for the Ingenic SoCs SPI controller.483 484 To compile this driver as a module, choose M here: the module485 will be called spi-ingenic.486 487config SPI_INTEL488 tristate489 490config SPI_INTEL_PCI491 tristate "Intel PCH/PCU SPI flash PCI driver"492 depends on PCI493 depends on X86 || COMPILE_TEST494 depends on SPI_MEM495 select SPI_INTEL496 help497 This enables PCI support for the Intel PCH/PCU SPI controller in498 master mode. This controller is used to hold BIOS and other499 persistent settings. Controllers present in modern Intel hardware500 only work in hardware sequencing mode, this means that the501 controller exposes a subset of operations that makes it safer to502 use. Using this driver it is possible to upgrade BIOS directly503 from Linux.504 505 To compile this driver as a module, choose M here: the module506 will be called spi-intel-pci.507 508config SPI_INTEL_PLATFORM509 tristate "Intel PCH/PCU SPI flash platform driver (DANGEROUS)"510 depends on X86 || COMPILE_TEST511 depends on SPI_MEM512 select SPI_INTEL513 help514 This enables platform support for the Intel PCH/PCU SPI515 controller in master mode that is used to hold BIOS and other516 persistent settings. Most of these controllers work in517 software sequencing mode, which means that the controller518 exposes the low level SPI-NOR opcodes to the software. Using519 this driver it is possible to upgrade BIOS directly from Linux.520 521 Say N here unless you know what you are doing. Overwriting the522 SPI flash may render the system unbootable.523 524 To compile this driver as a module, choose M here: the module525 will be called spi-intel-platform.526 527config SPI_JCORE528 tristate "J-Core SPI Master"529 depends on OF && (SUPERH || COMPILE_TEST)530 help531 This enables support for the SPI master controller in the J-Core532 synthesizable, open source SoC.533 534config SPI_LM70_LLP535 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"536 depends on PARPORT537 select SPI_BITBANG538 help539 This driver supports the NS LM70 LLP Evaluation Board,540 which interfaces to an LM70 temperature sensor using541 a parallel port.542 543config SPI_LOONGSON_CORE544 tristate545 depends on LOONGARCH || COMPILE_TEST546 547config SPI_LOONGSON_PCI548 tristate "Loongson SPI Controller PCI Driver Support"549 select SPI_LOONGSON_CORE550 depends on PCI && (LOONGARCH || COMPILE_TEST)551 help552 This bus driver supports the Loongson SPI hardware controller in553 the Loongson platforms and supports to use PCI framework to554 register SPI device resources.555 Say Y or M here if you want to use the SPI controller on556 Loongson platform.557 558config SPI_LOONGSON_PLATFORM559 tristate "Loongson SPI Controller Platform Driver Support"560 select SPI_LOONGSON_CORE561 depends on OF && (LOONGARCH || COMPILE_TEST)562 help563 This bus driver supports the Loongson SPI hardware controller in564 the Loongson platforms and supports to use DTS framework to565 register SPI device resources.566 Say Y or M here if you want to use the SPI controller on567 Loongson platform.568 569config SPI_LP8841_RTC570 tristate "ICP DAS LP-8841 SPI Controller for RTC"571 depends on MACH_PXA27X_DT || COMPILE_TEST572 help573 This driver provides an SPI master device to drive Maxim574 DS-1302 real time clock.575 576 Say N here unless you plan to run the kernel on an ICP DAS577 LP-8x4x industrial computer.578 579config SPI_MPC52xx580 tristate "Freescale MPC52xx SPI (non-PSC) controller support"581 depends on PPC_MPC52xx582 help583 This drivers supports the MPC52xx SPI controller in master SPI584 mode.585 586config SPI_MPC52xx_PSC587 tristate "Freescale MPC52xx PSC SPI controller"588 depends on PPC_MPC52xx589 help590 This enables using the Freescale MPC52xx Programmable Serial591 Controller in master SPI mode.592 593config SPI_MPC512x_PSC594 tristate "Freescale MPC512x PSC SPI controller"595 depends on PPC_MPC512x596 help597 This enables using the Freescale MPC5121 Programmable Serial598 Controller in SPI master mode.599 600config SPI_FSL_LIB601 tristate602 depends on OF603 604config SPI_FSL_CPM605 tristate606 depends on FSL_SOC607 608config SPI_FSL_SPI609 tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller"610 depends on OF611 select SPI_FSL_LIB612 select SPI_FSL_CPM if FSL_SOC613 help614 This enables using the Freescale SPI controllers in master mode.615 MPC83xx platform uses the controller in cpu mode or CPM/QE mode.616 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.617 This also enables using the Aeroflex Gaisler GRLIB SPI controller in618 master mode.619 620config SPI_FSL_DSPI621 tristate "Freescale DSPI controller"622 select REGMAP_MMIO623 depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || M5441x || COMPILE_TEST624 help625 This enables support for the Freescale DSPI controller in master626 mode. VF610, LS1021A and ColdFire platforms uses the controller.627 628config SPI_FSL_ESPI629 tristate "Freescale eSPI controller"630 depends on FSL_SOC631 help632 This enables using the Freescale eSPI controllers in master mode.633 From MPC8536, 85xx platform uses the controller, and all P10xx,634 P20xx, P30xx,P40xx, P50xx uses this controller.635 636config SPI_LJCA637 tristate "Intel La Jolla Cove Adapter SPI support"638 depends on USB_LJCA639 default USB_LJCA640 help641 Select this option to enable SPI driver for the Intel642 La Jolla Cove Adapter (LJCA) board.643 644 This driver can also be built as a module. If so, the module645 will be called spi-ljca.646 647config SPI_MESON_SPICC648 tristate "Amlogic Meson SPICC controller"649 depends on COMMON_CLK650 depends on ARCH_MESON || COMPILE_TEST651 help652 This enables master mode support for the SPICC (SPI communication653 controller) available in Amlogic Meson SoCs.654 655config SPI_MESON_SPIFC656 tristate "Amlogic Meson SPIFC controller"657 depends on ARCH_MESON || COMPILE_TEST658 select REGMAP_MMIO659 help660 This enables master mode support for the SPIFC (SPI flash661 controller) available in Amlogic Meson SoCs.662 663config SPI_MICROCHIP_CORE664 tristate "Microchip FPGA SPI controllers"665 depends on SPI_MASTER666 help667 This enables the SPI driver for Microchip FPGA SPI controllers.668 Say Y or M here if you want to use the "hard" controllers on669 PolarFire SoC.670 If built as a module, it will be called spi-microchip-core.671 672config SPI_MICROCHIP_CORE_QSPI673 tristate "Microchip FPGA QSPI controllers"674 depends on SPI_MASTER675 help676 This enables the QSPI driver for Microchip FPGA QSPI controllers.677 Say Y or M here if you want to use the QSPI controllers on678 PolarFire SoC.679 If built as a module, it will be called spi-microchip-core-qspi.680 681config SPI_MT65XX682 tristate "MediaTek SPI controller"683 depends on ARCH_MEDIATEK || COMPILE_TEST684 help685 This selects the MediaTek(R) SPI bus driver.686 If you want to use MediaTek(R) SPI interface,687 say Y or M here.If you are not sure, say N.688 SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs.689 690config SPI_MT7621691 tristate "MediaTek MT7621 SPI Controller"692 depends on RALINK || COMPILE_TEST693 help694 This selects a driver for the MediaTek MT7621 SPI Controller.695 696config SPI_MTK_NOR697 tristate "MediaTek SPI NOR controller"698 depends on ARCH_MEDIATEK || COMPILE_TEST699 help700 This enables support for SPI NOR controller found on MediaTek701 ARM SoCs. This is a controller specifically for SPI NOR flash.702 It can perform generic SPI transfers up to 6 bytes via generic703 SPI interface as well as several SPI NOR specific instructions704 via SPI MEM interface.705 706config SPI_MTK_SNFI707 tristate "MediaTek SPI NAND Flash Interface"708 depends on ARCH_MEDIATEK || COMPILE_TEST709 depends on MTD_NAND_ECC_MEDIATEK710 help711 This enables support for SPI-NAND mode on the MediaTek NAND712 Flash Interface found on MediaTek ARM SoCs. This controller713 is implemented as a SPI-MEM controller with pipelined ECC714 capability.715 716config SPI_WPCM_FIU717 tristate "Nuvoton WPCM450 Flash Interface Unit"718 depends on ARCH_NPCM || COMPILE_TEST719 select REGMAP720 help721 This enables support got the Flash Interface Unit SPI controller722 present in the Nuvoton WPCM450 SoC.723 724 This driver does not support generic SPI. The implementation only725 supports the spi-mem interface.726 727config SPI_NPCM_FIU728 tristate "Nuvoton NPCM FLASH Interface Unit"729 depends on ARCH_NPCM || COMPILE_TEST730 depends on OF && HAS_IOMEM731 help732 This enables support for the Flash Interface Unit SPI controller733 in master mode.734 This driver does not support generic SPI. The implementation only735 supports spi-mem interface.736 737config SPI_NPCM_PSPI738 tristate "Nuvoton NPCM PSPI Controller"739 depends on ARCH_NPCM || COMPILE_TEST740 help741 This driver provides support for Nuvoton NPCM BMC742 Peripheral SPI controller in master mode.743 744config SPI_LANTIQ_SSC745 tristate "Lantiq SSC SPI controller"746 depends on LANTIQ || X86 || COMPILE_TEST747 help748 This driver supports the Lantiq SSC SPI controller in master749 mode. This controller is found on Intel (former Lantiq) SoCs like750 the Danube, Falcon, xRX200, xRX300, Lightning Mountain.751 752config SPI_OC_TINY753 tristate "OpenCores tiny SPI"754 depends on GPIOLIB || COMPILE_TEST755 select SPI_BITBANG756 help757 This is the driver for OpenCores tiny SPI master controller.758 759config SPI_OCTEON760 tristate "Cavium OCTEON SPI controller"761 depends on CAVIUM_OCTEON_SOC762 help763 SPI host driver for the hardware found on some Cavium OCTEON764 SOCs.765 766config SPI_OMAP_UWIRE767 tristate "OMAP1 MicroWire"768 depends on ARCH_OMAP1 || (ARM && COMPILE_TEST)769 select SPI_BITBANG770 help771 This hooks up to the MicroWire controller on OMAP1 chips.772 773config SPI_OMAP24XX774 tristate "McSPI driver for OMAP"775 depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST776 select SG_SPLIT777 help778 SPI master controller for OMAP24XX and later Multichannel SPI779 (McSPI) modules.780 781config SPI_TI_QSPI782 tristate "DRA7xxx QSPI controller support"783 depends on ARCH_OMAP2PLUS || COMPILE_TEST784 help785 QSPI master controller for DRA7xxx used for flash devices.786 This device supports single, dual and quad read support, while787 it only supports single write mode.788 789config SPI_ORION790 tristate "Orion SPI master"791 depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST792 help793 This enables using the SPI master controller on the Orion794 and MVEBU chips.795 796config SPI_PCI1XXXX797 tristate "PCI1XXXX SPI Bus support"798 depends on PCI799 help800 Say "yes" to Enable the SPI Bus support for the PCI1xxxx card801 This is a PCI to SPI Bus driver802 This driver can be built as module. If so, the module will be803 called as spi-pci1xxxx.804 805config SPI_PIC32806 tristate "Microchip PIC32 series SPI"807 depends on MACH_PIC32 || COMPILE_TEST808 help809 SPI driver for Microchip PIC32 SPI master controller.810 811config SPI_PIC32_SQI812 tristate "Microchip PIC32 Quad SPI driver"813 depends on MACH_PIC32 || COMPILE_TEST814 help815 SPI driver for PIC32 Quad SPI controller.816 817config SPI_PL022818 tristate "ARM AMBA PL022 SSP controller"819 depends on ARM_AMBA820 default y if ARCH_REALVIEW821 default y if INTEGRATOR_IMPD1822 default y if ARCH_VERSATILE823 help824 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP825 controller. If you have an embedded system with an AMBA(R)826 bus and a PL022 controller, say Y or M here.827 828config SPI_PPC4xx829 tristate "PPC4xx SPI Controller"830 depends on PPC32 && 4xx831 select SPI_BITBANG832 help833 This selects a driver for the PPC4xx SPI Controller.834 835config SPI_PXA2XX836 tristate "PXA2xx SSP SPI master"837 depends on ARCH_PXA || ARCH_MMP || (X86 && (PCI || ACPI)) || COMPILE_TEST838 select PXA_SSP if ARCH_PXA || ARCH_MMP839 help840 This enables using a PXA2xx or Sodaville SSP port as a SPI master841 controller. The driver can be configured to use any SSP port.842 843config SPI_PXA2XX_PCI844 def_tristate SPI_PXA2XX && PCI && COMMON_CLK845 846config SPI_ROCKCHIP847 tristate "Rockchip SPI controller driver"848 depends on ARCH_ROCKCHIP || COMPILE_TEST849 help850 This selects a driver for Rockchip SPI controller.851 852 If you say yes to this option, support will be included for853 RK3066, RK3188 and RK3288 families of SPI controller.854 Rockchip SPI controller support DMA transport and PIO mode.855 The main usecase of this controller is to use spi flash as boot856 device.857 858config SPI_ROCKCHIP_SFC859 tristate "Rockchip Serial Flash Controller (SFC)"860 depends on ARCH_ROCKCHIP || COMPILE_TEST861 depends on HAS_IOMEM && HAS_DMA862 help863 This enables support for Rockchip serial flash controller. This864 is a specialized controller used to access SPI flash on some865 Rockchip SOCs.866 867 ROCKCHIP SFC supports DMA and PIO modes. When DMA is not available,868 the driver automatically falls back to PIO mode.869 870config SPI_RB4XX871 tristate "Mikrotik RB4XX SPI master"872 depends on SPI_MASTER && ATH79873 help874 SPI controller driver for the Mikrotik RB4xx series boards.875 876config SPI_RPCIF877 tristate "Renesas RPC-IF SPI driver"878 depends on RENESAS_RPCIF879 help880 SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF.881 882config SPI_RSPI883 tristate "Renesas RSPI/QSPI controller"884 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST885 help886 SPI driver for Renesas RSPI and QSPI blocks.887 888config SPI_RZV2M_CSI889 tristate "Renesas RZ/V2M CSI controller"890 depends on ARCH_RENESAS || COMPILE_TEST891 help892 SPI driver for Renesas RZ/V2M Clocked Serial Interface (CSI).893 CSI supports both SPI host and SPI target roles.894 895config SPI_QCOM_QSPI896 tristate "QTI QSPI controller"897 depends on ARCH_QCOM || COMPILE_TEST898 help899 QSPI(Quad SPI) driver for Qualcomm QSPI controller.900 901config SPI_QUP902 tristate "Qualcomm SPI controller with QUP interface"903 depends on ARCH_QCOM || COMPILE_TEST904 help905 Qualcomm Universal Peripheral (QUP) core is an AHB slave that906 provides a common data path (an output FIFO and an input FIFO)907 for serial peripheral interface (SPI) mini-core. SPI in master908 mode supports up to 50MHz, up to four chip selects, programmable909 data path from 4 bits to 32 bits and numerous protocol variants.910 911 This driver can also be built as a module. If so, the module912 will be called spi_qup.913 914config SPI_QCOM_GENI915 tristate "Qualcomm GENI based SPI controller"916 depends on QCOM_GENI_SE917 help918 This driver supports GENI serial engine based SPI controller in919 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say920 yes to this option, support will be included for the built-in SPI921 interface on the Qualcomm Technologies Inc.'s SoCs.922 923 This driver can also be built as a module. If so, the module924 will be called spi-geni-qcom.925 926config SPI_S3C64XX927 tristate "Samsung S3C64XX/Exynos SoC series type SPI"928 depends on (PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST)929 help930 SPI driver for Samsung S3C64XX, S5Pv210 and Exynos SoCs.931 Choose Y/M here only if you build for such Samsung SoC.932 933config SPI_SC18IS602934 tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"935 depends on I2C936 help937 SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.938 939config SPI_SH_MSIOF940 tristate "SuperH MSIOF SPI controller"941 depends on HAVE_CLK942 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST943 help944 SPI driver for SuperH and SH Mobile MSIOF blocks.945 946config SPI_SH947 tristate "SuperH SPI controller"948 depends on SUPERH || COMPILE_TEST949 help950 SPI driver for SuperH SPI blocks.951 952config SPI_SH_SCI953 tristate "SuperH SCI SPI controller"954 depends on SUPERH955 select SPI_BITBANG956 help957 SPI driver for SuperH SCI blocks.958 959config SPI_SH_HSPI960 tristate "SuperH HSPI controller"961 depends on ARCH_RENESAS || COMPILE_TEST962 help963 SPI driver for SuperH HSPI blocks.964 965config SPI_SIFIVE966 tristate "SiFive SPI controller"967 depends on HAS_IOMEM968 help969 This exposes the SPI controller IP from SiFive.970 971config SPI_SLAVE_MT27XX972 tristate "MediaTek SPI slave device"973 depends on ARCH_MEDIATEK || COMPILE_TEST974 depends on SPI_SLAVE975 help976 This selects the MediaTek(R) SPI slave device driver.977 If you want to use MediaTek(R) SPI slave interface,978 say Y or M here.If you are not sure, say N.979 SPI slave drivers for Mediatek MT27XX series ARM SoCs.980 981config SPI_SN_F_OSPI982 tristate "Socionext F_OSPI SPI flash controller"983 depends on OF && HAS_IOMEM984 depends on SPI_MEM985 help986 This enables support for the Socionext F_OSPI controller987 for connecting an SPI Flash memory over up to 8-bit wide bus.988 It supports indirect access mode only.989 990config SPI_SPRD991 tristate "Spreadtrum SPI controller"992 depends on ARCH_SPRD || COMPILE_TEST993 help994 SPI driver for Spreadtrum SoCs.995 996config SPI_SPRD_ADI997 tristate "Spreadtrum ADI controller"998 depends on ARCH_SPRD || COMPILE_TEST999 depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK)1000 help1001 ADI driver based on SPI for Spreadtrum SoCs.1002 1003config SPI_STM321004 tristate "STMicroelectronics STM32 SPI controller"1005 depends on ARCH_STM32 || COMPILE_TEST1006 select SPI_SLAVE1007 help1008 SPI driver for STMicroelectronics STM32 SoCs.1009 1010 STM32 SPI controller supports DMA and PIO modes. When DMA1011 is not available, the driver automatically falls back to1012 PIO mode.1013 1014config SPI_STM32_QSPI1015 tristate "STMicroelectronics STM32 QUAD SPI controller"1016 depends on ARCH_STM32 || COMPILE_TEST1017 depends on OF1018 depends on SPI_MEM1019 help1020 This enables support for the Quad SPI controller in master mode.1021 This driver does not support generic SPI. The implementation only1022 supports spi-mem interface.1023 1024config SPI_ST_SSC41025 tristate "STMicroelectronics SPI SSC-based driver"1026 depends on ARCH_STI || COMPILE_TEST1027 help1028 STMicroelectronics SoCs support for SPI. If you say yes to1029 this option, support will be included for the SSC driven SPI.1030 1031config SPI_SUN4I1032 tristate "Allwinner A10 SoCs SPI controller"1033 depends on ARCH_SUNXI || COMPILE_TEST1034 help1035 SPI driver for Allwinner sun4i, sun5i and sun7i SoCs1036 1037config SPI_SUN6I1038 tristate "Allwinner A31 SPI controller"1039 depends on ARCH_SUNXI || COMPILE_TEST1040 depends on RESET_CONTROLLER1041 help1042 This enables using the SPI controller on the Allwinner A31 SoCs.1043 1044config SPI_SUNPLUS_SP70211045 tristate "Sunplus SP7021 SPI controller"1046 depends on SOC_SP7021 || COMPILE_TEST1047 help1048 This enables Sunplus SP7021 SPI controller driver on the SP7021 SoCs.1049 This driver can also be built as a module. If so, the module will be1050 called as spi-sunplus-sp7021.1051 1052 If you have a Sunplus SP7021 platform say Y here.1053 If unsure, say N.1054 1055config SPI_SYNQUACER1056 tristate "Socionext's SynQuacer HighSpeed SPI controller"1057 depends on ARCH_SYNQUACER || COMPILE_TEST1058 help1059 SPI driver for Socionext's High speed SPI controller which provides1060 various operating modes for interfacing to serial peripheral devices1061 that use the de-facto standard SPI protocol.1062 1063 It also supports the new dual-bit and quad-bit SPI protocol.1064 1065config SPI_MXIC1066 tristate "Macronix MX25F0A SPI controller"1067 depends on SPI_MASTER1068 imply MTD_NAND_ECC_MXIC1069 help1070 This selects the Macronix MX25F0A SPI controller driver.1071 1072config SPI_MXS1073 tristate "Freescale MXS SPI controller"1074 depends on ARCH_MXS1075 select STMP_DEVICE1076 help1077 SPI driver for Freescale MXS devices.1078 1079config SPI_TEGRA210_QUAD1080 tristate "NVIDIA Tegra QSPI Controller"1081 depends on ARCH_TEGRA || COMPILE_TEST1082 depends on RESET_CONTROLLER1083 help1084 QSPI driver for NVIDIA Tegra QSPI Controller interface. This1085 controller is different from the SPI controller and is available1086 on Tegra SoCs starting from Tegra210.1087 1088config SPI_TEGRA1141089 tristate "NVIDIA Tegra114 SPI Controller"1090 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST1091 depends on RESET_CONTROLLER1092 help1093 SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller1094 is different than the older SoCs SPI controller and also register interface1095 get changed with this controller.1096 1097config SPI_TEGRA20_SFLASH1098 tristate "Nvidia Tegra20 Serial flash Controller"1099 depends on ARCH_TEGRA || COMPILE_TEST1100 depends on RESET_CONTROLLER1101 help1102 SPI driver for Nvidia Tegra20 Serial flash Controller interface.1103 The main usecase of this controller is to use spi flash as boot1104 device.1105 1106config SPI_TEGRA20_SLINK1107 tristate "Nvidia Tegra20/Tegra30 SLINK Controller"1108 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST1109 depends on RESET_CONTROLLER1110 help1111 SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.1112 1113config SPI_THUNDERX1114 tristate "Cavium ThunderX SPI controller"1115 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)1116 help1117 SPI host driver for the hardware found on Cavium ThunderX1118 SOCs.1119 1120config SPI_TOPCLIFF_PCH1121 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"1122 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)1123 help1124 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus1125 used in some x86 embedded processors.1126 1127 This driver also supports the ML7213/ML7223/ML7831, a companion chip1128 for the Atom E6xx series and compatible with the Intel EG20T PCH.1129 1130config SPI_UNIPHIER1131 tristate "Socionext UniPhier SPI Controller"1132 depends on (ARCH_UNIPHIER || COMPILE_TEST) && OF1133 depends on HAS_IOMEM1134 help1135 This enables a driver for the Socionext UniPhier SoC SCSSI SPI controller.1136 1137 UniPhier SoCs have SCSSI and MCSSI SPI controllers.1138 Every UniPhier SoC has SCSSI which supports single channel.1139 Older UniPhier Pro4/Pro5 also has MCSSI which support multiple channels.1140 This driver supports SCSSI only.1141 1142 If your SoC supports SCSSI, say Y here.1143 1144config SPI_XCOMM1145 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"1146 depends on I2C1147 help1148 Support for the SPI-I2C bridge found on the Analog Devices1149 AD-FMCOMMS1-EBZ board.1150 1151config SPI_XILINX1152 tristate "Xilinx SPI controller common module"1153 depends on HAS_IOMEM1154 select SPI_BITBANG1155 help1156 This exposes the SPI controller IP from the Xilinx EDK.1157 1158 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"1159 Product Specification document (DS464) for hardware details.1160 1161 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"1162 1163config SPI_XLP1164 tristate "Cavium ThunderX2 SPI controller driver"1165 depends on ARCH_THUNDER2 || COMPILE_TEST1166 help1167 Enable support for the SPI controller on the Cavium ThunderX2.1168 (Originally on Netlogic XLP SoCs.)1169 1170 If you have a Cavium ThunderX2 platform say Y here.1171 If unsure, say N.1172 1173config SPI_XTENSA_XTFPGA1174 tristate "Xtensa SPI controller for xtfpga"1175 depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST1176 select SPI_BITBANG1177 help1178 SPI driver for xtfpga SPI master controller.1179 1180 This simple SPI master controller is built into xtfpga bitstreams1181 and is used to control daughterboard audio codec. It always transfers1182 16 bit words in SPI mode 0, automatically asserting CS on transfer1183 start and deasserting on end.1184 1185config SPI_ZYNQ_QSPI1186 tristate "Xilinx Zynq QSPI controller"1187 depends on ARCH_ZYNQ || COMPILE_TEST1188 depends on SPI_MEM1189 help1190 This enables support for the Zynq Quad SPI controller1191 in master mode.1192 This controller only supports SPI memory interface.1193 1194config SPI_ZYNQMP_GQSPI1195 tristate "Xilinx ZynqMP GQSPI controller"1196 depends on (SPI_MEM && HAS_DMA) || COMPILE_TEST1197 help1198 Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.1199 This controller only supports SPI memory interface.1200 1201config SPI_AMD1202 tristate "AMD SPI controller"1203 depends on SPI_MASTER || COMPILE_TEST1204 help1205 Enables SPI controller driver for AMD SoC.1206 1207#1208# Add new SPI master controllers in alphabetical order above this line1209#1210 1211comment "SPI Multiplexer support"1212 1213config SPI_MUX1214 tristate "SPI multiplexer support"1215 select MULTIPLEXER1216 help1217 This adds support for SPI multiplexers. Each SPI mux will be1218 accessible as a SPI controller, the devices behind the mux will appear1219 to be chip selects on this controller. It is still necessary to1220 select one or more specific mux-controller drivers.1221 1222#1223# There are lots of SPI device types, with sensors and memory1224# being probably the most widely used ones.1225#1226comment "SPI Protocol Masters"1227 1228config SPI_SPIDEV1229 tristate "User mode SPI device driver support"1230 help1231 This supports user mode SPI protocol drivers.1232 1233config SPI_LOOPBACK_TEST1234 tristate "spi loopback test framework support"1235 depends on m1236 help1237 This enables the SPI loopback testing framework driver1238 1239 primarily used for development of spi_master drivers1240 and to detect regressions1241 1242config SPI_TLE62X01243 tristate "Infineon TLE62X0 (for power switching)"1244 depends on SYSFS1245 help1246 SPI driver for Infineon TLE62X0 series line driver chips,1247 such as the TLE6220, TLE6230 and TLE6240. This provides a1248 sysfs interface, with each line presented as a kind of GPIO1249 exposing both switch control and diagnostic feedback.1250 1251#1252# Add new SPI protocol masters in alphabetical order above this line1253#1254 1255endif # SPI_MASTER1256 1257#1258# SLAVE side ... listening to other SPI masters1259#1260 1261config SPI_SLAVE1262 bool "SPI slave protocol handlers"1263 help1264 If your system has a slave-capable SPI controller, you can enable1265 slave protocol handlers.1266 1267if SPI_SLAVE1268 1269config SPI_SLAVE_TIME1270 tristate "SPI slave handler reporting boot up time"1271 help1272 SPI slave handler responding with the time of reception of the last1273 SPI message.1274 1275config SPI_SLAVE_SYSTEM_CONTROL1276 tristate "SPI slave handler controlling system state"1277 help1278 SPI slave handler to allow remote control of system reboot, power1279 off, halt, and suspend.1280 1281endif # SPI_SLAVE1282 1283config SPI_DYNAMIC1284 def_bool ACPI || OF_DYNAMIC || SPI_SLAVE1285 1286endif # SPI1287