Home
last modified time | relevance | path

Searched refs:SPI (Results 1 – 25 of 929) sorted by relevance

12345678910>>...38

/openbmc/u-boot/drivers/spi/
H A DKconfig1 menuconfig SPI config
2 bool "SPI Support"
4 if SPI
10 Enable driver model for SPI. The SPI slave interface
12 the SPI uclass. Drivers provide methods to access the SPI
63 to access SPI NOR flash and other SPI peripherals. This driver
81 SPI core.
89 SPI cores.
178 to access the SPI NOR flash, MMC-over-SPI on platforms based on
281 Enable the Xilinx SPI driver from the Xilinx EDK. This SPI
[all …]
/openbmc/linux/drivers/spi/
H A DKconfig5 menuconfig SPI config
6 bool "SPI support"
26 if SPI
42 default SPI
79 Altera SPI master controller. The SPI master is connected
118 to SPI NOR chips, and support for the SPI flash memory
318 tristate "Baikal-T1 SPI driver for DW SPI core"
787 SPI driver for PIC32 Quad SPI controller.
922 SPI driver for SuperH SPI blocks.
1150 SPI driver for xtfpga SPI master controller.
[all …]
/openbmc/u-boot/drivers/mtd/spi/
H A DKconfig1 menu "SPI Flash Support"
4 bool "Enable Driver Model for SPI flash"
7 Enable driver model for SPI flash. This SPI flash interface
14 during the transition parent. SPI and SPI flash must be
30 depends on SPI
99 bool "Atmel SPI flash support"
104 bool "EON SPI flash support"
114 bool "ISSI SPI flash support"
134 bool "SST SPI flash support"
144 bool "XMC SPI flash support"
[all …]
/openbmc/linux/Documentation/driver-api/mtd/
H A Dspi-nor.rst2 SPI NOR framework
8 SPI bus controllers (drivers/spi/) only deal with streams of bytes; the bus
18 details of the SPI NOR protocol.
33 SPI bus driver
35 SPI NOR chip
41 SPI NOR framework
45 SPI bus driver
47 SPI NOR chip
53 SPI NOR framework
57 SPI NOR chip
[all …]
/openbmc/u-boot/doc/device-tree-bindings/spi/
H A Dspi-bus.txt1 SPI (Serial Peripheral Interface) busses
3 SPI busses can be described with a node for the SPI master device
4 and a set of child nodes for each SPI slave on the bus. For this
5 discussion, it is assumed that the system's SPI controller is in
6 SPI master mode. This binding does not describe SPI controllers
9 The SPI master node requires the following properties:
11 address on the SPI bus.
17 that a driver for an SPI bus device will understand that it is an SPI bus.
44 SPI slave nodes must be children of the SPI master node and can
65 Some SPI controllers and devices support Dual and Quad SPI transfer mode.
[all …]
H A Dsoft-spi.txt1 Soft SPI
3 The soft SPI bus implementation allows the use of GPIO pins to simulate a
4 SPI bus. No SPI host is required for this to work. The down-side is that the
5 performance will typically be much lower than a real SPI bus.
7 The soft SPI node requires the following properties:
11 cs-gpios: GPIOs to use for SPI chip select (output)
12 gpio-sck: GPIO to use for SPI clock (output)
14 gpio-mosi: GPIO to use for SPI MOSI line (output)
15 gpio-miso: GPIO to use for SPI MISO line (input)
H A Dspi-atcspi200.txt1 Andestech ATCSPI200 SPI controller Device Tree Bindings
3 ATCSPI200 is a Serial Peripheral Interface (SPI) controller
4 which serves as a SPI master or a SPI slave.
11 - #address-cells: <1>, as required by generic SPI binding.
12 - #size-cells: <0>, also as required by generic SPI binding.
15 - spi-max-frequency: Maximum SPI clocking speed of device in Hz.
/openbmc/linux/drivers/media/spi/
H A DKconfig2 if VIDEO_DEV && SPI
4 comment "SPI I2C drivers auto-selected by 'Autoselect ancillary drivers'"
5 depends on MEDIA_HIDE_ANCILLARY_SUBDRV && SPI
7 menu "Media SPI Adapters"
10 tristate "Sony CXD2880 SPI support"
11 depends on DVB_CORE && SPI
14 Choose if you would like to have SPI interface support for Sony CXD2880.
18 depends on SPI && VIDEO_DEV
/openbmc/u-boot/doc/SPI/
H A DREADME.sandbox-spi1 Sandbox SPI/SPI Flash Implementation
4 U-Boot supports SPI and SPI flash emulation in sandbox. This must be enabled
15 SPI bus number (typically 0)
16 SPI chip select number (typically 0)
17 SPI chip to emulate
37 SPI flash test:
52 Since the SPI bus is fully implemented as well as the SPI flash connected to
53 it, you can also use low-level SPI commands to access the flash. For example
63 Note that the sandbox SPI implementation was written by Mike Frysinger
H A Dstatus.txt1 Status on SPI subsystem:
4 SPI COMMAND (common/cmd_sf, cmd_spi):
7 SPI FLASH (drivers/mtd/spi):
8 - sf_probe.c: SPI flash probing code.
9 - sf_ops.c: SPI flash operations code.
10 - sf.c: SPI flash interface, which interacts controller driver.
20 SPI DRIVERS (drivers/spi):
/openbmc/linux/Documentation/devicetree/bindings/spi/
H A Dsnps,dw-apb-ssi.yaml55 - description: Generic DW SPI Controller
65 - description: Microchip Sparx5 SoC SPI Controller
67 - description: Amazon Alpine SPI Controller
69 - description: Renesas RZ/N1 SPI Controller
73 - description: Intel Keem Bay SPI Controller
75 - description: Intel Thunder Bay SPI Controller
81 - description: Baikal-T1 SPI Controller
87 - description: Renesas RZ/N1 SPI Controller
98 - description: SPI MST region map or directly mapped SPI ROM
146 for a SPI slave device.
[all …]
H A Dspi-sprd.txt1 Spreadtrum SPI Controller
5 - reg: Offset and length of SPI controller register space.
6 - interrupts: Should contain SPI interrupt.
8 "spi" for SPI clock,
9 "source" for SPI source (parent) clock,
10 "enable" for SPI module enable clock.
14 address on the SPI bus. Should be set to 1.
18 dma-names: Should contain names of the SPI used DMA channel.
19 dmas: Should contain DMA channels and DMA slave ids which the SPI used
H A Dspi-davinci.txt1 Davinci SPI controller device bindings
10 address on the SPI bus. Should be set to 1.
13 - "ti,dm6441-spi" for SPI used similar to that on DM644x SoC family
14 - "ti,da830-spi" for SPI used similar to that on DA8xx SoC family
15 - "ti,keystone-spi" for SPI used similar to that on Keystone2 SoC
17 - reg: Offset and length of SPI controller register space
20 - ti,davinci-spi-intr-line: interrupt line used to connect the SPI
35 and an args specifier containing the SPI device id
45 SPI slave nodes can contain the following properties.
46 Not all SPI Peripherals from Texas Instruments support this.
[all …]
/openbmc/linux/drivers/net/can/spi/
H A DKconfig2 menu "CAN SPI interfaces"
3 depends on SPI
6 tristate "Holt HI311x SPI CAN controllers"
8 Driver for the Holt HI311x SPI CAN controllers.
11 tristate "Microchip MCP251x and MCP25625 SPI CAN controllers"
13 Driver for the Microchip MCP251x and MCP25625 SPI CAN
/openbmc/linux/Documentation/devicetree/bindings/net/
H A Dqca,qca7000.txt4 be configured either as SPI or UART slave. This configuration is done by
7 (a) Ethernet over SPI
9 In order to use the QCA7000 as SPI device it must be defined as a child of a
10 SPI master in the device tree.
14 - reg : Should specify the SPI chip select
24 are invalid. Missing the property will set the SPI
27 In this mode the SPI master must toggle the chip select
36 SPI Example:
38 /* Freescale i.MX28 SPI master*/
51 spi-cpha; /* SPI mode: CPHA=1 */
[all …]
/openbmc/linux/Documentation/spi/
H A Dspi-summary.rst2 Overview of Linux kernel SPI support
7 What is SPI?
22 SPI masters use a fourth "chip select" line to activate a given SPI slave
76 support only SPI.) Some PC hardware uses SPI flash for BIOS code.
91 interfaces with SPI modes. Given SPI support, they could use MMC or SD
135 SPI requests always go into I/O queues. Requests for a given SPI device
197 the physical SPI bus segment with other SPI slave devices.
494 used to interact with the SPI core and SPI protocol drivers. It will
522 SPI Master Methods
580 This method allows SPI client drivers to request SPI master controller
[all …]
H A Dspidev.rst2 SPI userspace API
5 SPI devices have a limited userspace API, supporting basic half-duplex
6 read() and write() access to SPI slave devices. Using ioctl() requests,
23 as SPI slaves, which you may need to change quite often.
33 The spidev driver contains lists of SPI devices that are supported for
74 For a SPI device with chipselect C on bus B, you should see:
82 as usual, the SPI device node will
83 be a child of its SPI master controller.
99 for its SPI controller (so its spi_master vanishes).
104 SPI device, and you'll get a /dev device node for each device.
[all …]
/openbmc/linux/Documentation/driver-api/
H A Dspi.rst1 Serial Peripheral Interface (SPI)
4 SPI is the "Serial Peripheral Interface", widely used with embedded
8 line, and a "Master In, Slave Out" (MISO) data line. SPI is a full
15 The SPI bus facilities listed here provide a generalized interface to
16 declare SPI busses and devices, manage them according to the standard
18 only "master" side interfaces are supported, where Linux talks to SPI
20 to support implementing SPI slaves would necessarily look different.)
27 whatever bus they sit on (often the platform bus) and SPI, and expose
28 the SPI side of their device as a :c:type:`struct spi_controller
29 <spi_controller>`. SPI devices are children of that master,
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-iio-dfsdm-adc-stm329 This is mandatory if DFSDM is slave on SPI bus, to
10 provide information on the SPI clock frequency during runtime
11 Notice that the SPI frequency should be a multiple of sample
14 if DFSDM input is SPI master:
16 Reading SPI clkout frequency,
19 If DFSDM input is SPI Slave:
/openbmc/linux/drivers/pinctrl/
H A Dpinctrl-xway.c122 MFP_XWAY(GPIO7, GPIO, SPI, MII, JTAG),
123 MFP_XWAY(GPIO8, GPIO, SPI, MII, JTAG),
124 MFP_XWAY(GPIO9, GPIO, SPI, MII, JTAG),
125 MFP_XWAY(GPIO10, GPIO, SPI, MII, JTAG),
129 MFP_XWAY(GPIO14, GPIO, EBU, SPI, CGU),
130 MFP_XWAY(GPIO15, GPIO, EBU, SPI, SDIO),
252 MFP_XWAY(GPIO9, GPIO, ASC, SPI, MII),
253 MFP_XWAY(GPIO10, GPIO, ASC, SPI, MII),
254 MFP_XWAY(GPIO11, GPIO, ASC, CBUS, SPI),
256 MFP_XWAY(GPIO13, GPIO, EBU, SPI, MII),
[all …]
/openbmc/u-boot/drivers/pinctrl/mscc/
H A Dpinctrl-servalt.c130 MSCC_P(8, SPI, SFP0, TWI_SCL_M);
131 MSCC_P(9, PCI_WAKE, SFP1, SPI);
136 MSCC_P(14, REF_CLK2, IRQ0_OUT, SPI);
137 MSCC_P(15, REF_CLK3, IRQ1_OUT, SPI);
138 MSCC_P(16, TACHO, SFP6, SPI);
140 MSCC_P(18, PTP2, SFP7, SPI);
141 MSCC_P(19, PTP3, SFP8, SPI);
142 MSCC_P(20, UART2, SFP9, SPI);
148 MSCC_P(26, TWI_SCL_M, SFP13, SPI);
149 MSCC_P(27, TWI_SCL_M, SFP14, SPI);
[all …]
/openbmc/linux/drivers/iio/gyro/
H A DKconfig11 depends on SPI
14 Rate Gyroscope with SPI.
18 depends on SPI
34 depends on SPI
46 depends on SPI
58 depends on SPI
72 select BMG160_SPI if (SPI)
94 select FXAS21002C_SPI if (SPI)
98 Sensor driver connected via I2C or SPI.
163 tristate "STMicroelectronics gyroscopes 3-Axis SPI Interface"
[all …]
/openbmc/linux/drivers/net/wireless/microchip/wilc1000/
H A DKconfig6 This provides Wi-FI over an SDIO or SPI interface, and
26 tristate "Atmel WILC1000 SPI (WiFi only)"
27 depends on CFG80211 && INET && SPI
32 This module adds support for the SPI interface of adapters using
34 Interface (SPI) that operates as a SPI slave. This SPI interface can
35 be used for control and for serial I/O of 802.11 data. The SPI is a
38 VDDIO. Select this if your platform is using the SPI bus.
/openbmc/openbmc/meta-phosphor/dynamic-layers/aspeed-layer/recipes-bsp/u-boot/files/
H A D0006-aspeed-Enable-SPI-master-mode-by-default.patch4 Subject: [PATCH] aspeed: Enable SPI master mode by default
7 for SPI interface mode selection ( pin[12:13] ).
9 It makes the SPI interface mode setting is not correct.
11 This patch will enable the SPI master mode by default.
26 + //pin switch by trap[13:12] -- [0:1] Enable SPI Master
27 + ast_scu_spi_master(1); /* enable SPI master */
/openbmc/linux/drivers/mtd/spi-nor/controllers/
H A DKconfig3 tristate "Hisilicon FMC SPI NOR Flash Controller(SFC)"
7 This enables support for HiSilicon FMC SPI NOR flash controller.
10 tristate "NXP SPI Flash Interface (SPIFI)"
14 Enable support for the NXP LPC SPI Flash Interface controller.
16 SPIFI is a specialized controller for connecting serial SPI

12345678910>>...38