Lines Matching +full:zynq +full:- +full:can +full:- +full:1
1 # SPDX-License-Identifier: GPL-2.0-only
10 protocol. Chips that support SPI can have data transfer rates
13 dynamic device discovery; some are even write-only or read-only.
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
44 If your system has an master-capable SPI controller (which
45 provides the clock and chipselect), you can enable that
56 by providing a high-level interface to send memory-like commands.
69 This enables support for SPI-NAND mode on the Airoha NAND
71 is implemented as a SPI-MEM controller.
110 SPI-MEM interface, it doesn't support generic SPI.
117 This enables master mode support for the SPISG (SPI scatter-gather
129 to a single device like spi-nor (nvram), input device controller
188 supports spi-mem interface.
265 With a few GPIO pins, your system can bitbang the SPI protocol.
268 this code to manage the per-word or per-transfer accesses to the
283 This same cable can be used to flash new firmware.
289 used by Xilinx Zynq and ZynqMP.
298 Flash over 1/2/4-bit wide bus. Enable this option if you have a
310 Flash over up to 8-bit wide bus. Enable this option if you have a
324 This enables dedicated general purpose SPI/Microwire1-compatible
325 master mode interface (SSI1) for CLPS711X-based CPUs.
343 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
347 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
365 tristate "Memory-mapped io interface driver for DW SPI core"
369 tristate "Baikal-T1 SPI driver for DW SPI core"
373 Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI
376 part of the Baikal-T1 System Boot Controller has got a very
378 chip-select and Tx/Rx FIFO with just 8 words depth available.
379 The later one is normally connected to an external SPI-nor flash
380 of 128Mb (in general can be of bigger size).
383 bool "Directly mapped Baikal-T1 Boot SPI flash support"
387 Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which
388 can be used to access a peripheral memory device just by
392 time-critical tasks (like the SPI memory operations implemented
398 tristate "Diolan DLN-2 USB SPI adapter"
404 This driver can also be built as a module. If so, the module
405 will be called spi-dln2.
418 The external bus unit (EBU) found on the FALC-ON SoC has SPI
443 Up to four flash chips can be connected on two buses with two
446 supports the high-level SPI memory interface.
462 This driver can also be built as a module. If so, the module
463 will be called hisi-kunpeng-spi.
479 Up to four slave devices can be connected on two buses with two
482 supports the high-level SPI memory interface.
485 tristate "GPIO-based bitbanging SPI Master"
489 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
495 Note that this driver often won't achieve even 1 Mbit/sec speeds,
496 making it unusually slow for SPI. If your platform can inline
520 will be called spi-ingenic.
541 will be called spi-intel-pci.
553 exposes the low level SPI-NOR opcodes to the software. Using
560 will be called spi-intel-platform.
563 tristate "J-Core SPI Master"
566 This enables support for the SPI master controller in the J-Core
578 This driver can also be built as a module. If so, the module
579 will be called spi-kspi2.
617 tristate "ICP DAS LP-8841 SPI Controller for RTC"
621 DS-1302 real time clock.
624 LP-8x4x industrial computer.
627 tristate "Freescale MPC52xx SPI (non-PSC) controller support"
691 This driver can also be built as a module. If so, the module
692 will be called spi-ljca.
717 If built as a module, it will be called spi-microchip-core-qspi.
726 If built as a module, it will be called spi-microchip-core-spi.
749 It can perform generic SPI transfers up to 6 bytes via generic
758 This enables support for SPI-NAND mode on the MediaTek NAND
760 is implemented as a SPI-MEM controller with pipelined ECC
772 supports the spi-mem interface.
782 supports spi-mem interface.
849 This driver can be built as module. If so, the module will be
850 called as spi-pci1xxxx.
883 If built as a module, it will be called spi-mpfs.
898 controller. The driver can be configured to use any SSP port.
904 tristate "Realtek SPI-NAND Flash Controller"
908 This enables support for the SPI-NAND Flash controller on
912 only supports the spi-mem interface.
946 tristate "Renesas RPC-IF SPI driver"
949 SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF.
993 for serial peripheral interface (SPI) mini-core. SPI in master
997 This driver can also be built as a module. If so, the module
1006 yes to this option, support will be included for the built-in SPI
1009 This driver can also be built as a module. If so, the module
1010 will be called spi-geni-qcom.
1073 for connecting an SPI Flash memory over up to 8-bit wide bus.
1117 supports spi-mem interface.
1127 supports spi-mem interface.
1130 tristate "STMicroelectronics SPI SSC-based driver"
1154 This driver can also be built as a module. If so, the module will be
1155 called as spi-sunplus-sp7021.
1166 that use the de-facto standard SPI protocol.
1168 It also supports the new dual-bit and quad-bit SPI protocol.
1254 SPI controller driver. The hardware can be emulated by any device model
1257 This driver can also be built as a module. If so, the module
1258 will be called spi-virtio.
1261 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
1264 Support for the SPI-I2C bridge found on the Analog Devices
1265 AD-FMCOMMS1-EBZ board.
1302 tristate "Xilinx Zynq QSPI controller"
1306 This enables support for the Zynq Quad SPI controller
1314 Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
1338 select one or more specific mux-controller drivers.
1382 If your system has a slave-capable SPI controller, you can enable
1409 tristate "SPI offload trigger using ADI sigma-delta utility"
1411 SPI offload trigger from ADI sigma-delta utility FPGA IP block.