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