Lines Matching +full:memory +full:- +full:controllers
1 # SPDX-License-Identifier: GPL-2.0-only
13 dynamic device discovery; some are even write-only or read-only.
16 eeprom and flash memory, codecs and various other controller
17 chips, analog to digital (and d-to-a) converters, and more.
24 work with most such devices and controllers.
44 If your system has an master-capable SPI controller (which
52 bool "SPI memory extension"
54 Enable this option if you want to enable the SPI memory extension.
56 by providing a high-level interface to send memory-like commands.
66 This enables support for SPI-NAND mode on the Airoha NAND
68 is implemented as a SPI-MEM controller.
107 to a single device like spi-nor (nvram), input device controller
133 tristate "Aspeed flash controllers in SPI mode"
137 This enables support for the Firmware Memory controller (FMC)
139 to SPI NOR chips, and support for the SPI flash memory
166 supports spi-mem interface.
240 tristate "Utilities for Bitbanging SPI host controllers"
245 this code to manage the per-word or per-transfer accesses to the
275 Flash over 1/2/4-bit wide bus. Enable this option if you have a
287 Flash over up to 8-bit wide bus. Enable this option if you have a
301 This enables dedicated general purpose SPI/Microwire1-compatible
302 master mode interface (SSI1) for CLPS711X-based CPUs.
320 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
324 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
342 tristate "Memory-mapped io interface driver for DW SPI core"
346 tristate "Baikal-T1 SPI driver for DW SPI core"
350 Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI
351 controllers. Two of them are pretty much normal: with IRQ, DMA,
353 part of the Baikal-T1 System Boot Controller has got a very
355 chip-select and Tx/Rx FIFO with just 8 words depth available.
356 The later one is normally connected to an external SPI-nor flash
360 bool "Directly mapped Baikal-T1 Boot SPI flash support"
363 Directly mapped SPI flash memory is an interface specific to the
364 Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which
365 can be used to access a peripheral memory device just by
369 time-critical tasks (like the SPI memory operations implemented
375 tristate "Diolan DLN-2 USB SPI adapter"
382 will be called spi-dln2.
395 The external bus unit (EBU) found on the FALC-ON SoC has SPI
405 controllers.
411 This enables Freescale i.MX LPSPI controllers in master mode.
422 supports the high-level SPI memory interface.
429 controllers.
439 will be called hisi-kunpeng-spi.
458 supports the high-level SPI memory interface.
461 tristate "GPIO-based bitbanging SPI Master"
465 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
484 tristate "Freescale i.MX SPI controllers"
487 This enables support for the Freescale i.MX SPI controllers.
496 will be called spi-ingenic.
510 persistent settings. Controllers present in modern Intel hardware
517 will be called spi-intel-pci.
527 persistent settings. Most of these controllers work in
529 exposes the low level SPI-NOR opcodes to the software. Using
536 will be called spi-intel-platform.
539 tristate "J-Core SPI Master"
542 This enables support for the SPI master controller in the J-Core
555 will be called spi-kspi2.
593 tristate "ICP DAS LP-8841 SPI Controller for RTC"
597 DS-1302 real time clock.
600 LP-8x4x industrial computer.
603 tristate "Freescale MPC52xx SPI (non-PSC) controller support"
637 This enables using the Freescale SPI controllers in master mode.
655 This enables using the Freescale eSPI controllers in master mode.
668 will be called spi-ljca.
687 tristate "Microchip FPGA SPI controllers"
690 This enables the SPI driver for Microchip FPGA SPI controllers.
691 Say Y or M here if you want to use the "hard" controllers on
693 If built as a module, it will be called spi-microchip-core.
696 tristate "Microchip FPGA QSPI controllers"
699 This enables the QSPI driver for Microchip FPGA QSPI controllers.
700 Say Y or M here if you want to use the QSPI controllers on
702 If built as a module, it will be called spi-microchip-core-qspi.
734 This enables support for SPI-NAND mode on the MediaTek NAND
736 is implemented as a SPI-MEM controller with pipelined ECC
748 supports the spi-mem interface.
758 supports spi-mem interface.
826 called as spi-pci1xxxx.
870 tristate "Realtek SPI-NAND Flash Controller"
874 This enables support for the SPI-NAND Flash controller on
878 only supports the spi-mem interface.
911 tristate "Renesas RPC-IF SPI driver"
914 SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF.
941 for serial peripheral interface (SPI) mini-core. SPI in master
954 yes to this option, support will be included for the built-in SPI
958 will be called spi-geni-qcom.
1021 for connecting an SPI Flash memory over up to 8-bit wide bus.
1056 supports spi-mem interface.
1059 tristate "STMicroelectronics SPI SSC-based driver"
1084 called as spi-sunplus-sp7021.
1095 that use the de-facto standard SPI protocol.
1097 It also supports the new dual-bit and quad-bit SPI protocol.
1171 UniPhier SoCs have SCSSI and MCSSI SPI controllers.
1179 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
1182 Support for the SPI-I2C bridge found on the Analog Devices
1183 AD-FMCOMMS1-EBZ board.
1226 This controller only supports SPI memory interface.
1233 This controller only supports SPI memory interface.
1242 # Add new SPI master controllers in alphabetical order above this line
1254 select one or more specific mux-controller drivers.
1257 # There are lots of SPI device types, with sensors and memory
1298 If your system has a slave-capable SPI controller, you can enable