| /openbmc/u-boot/drivers/spi/ |
| H A D | Kconfig | 1 menuconfig SPI config
2 bool "SPI Support"
4 if SPI
7 bool "Enable Driver Model for SPI drivers"
10 Enable driver model for SPI. The SPI slave interface
12 the SPI uclass. Drivers provide methods to access the SPI
20 bool "SPI memory extension"
22 Enable this option if you want to enable the SPI memory extension.
23 This extension is meant to simplify interaction with SPI memories
29 bool "Altera SPI driver"
[all …]
|
| /openbmc/linux/drivers/spi/ |
| H A D | Kconfig | 3 # SPI driver configuration
5 menuconfig SPI config
6 bool "SPI support"
10 protocol. Chips that support SPI can have data transfer rates
12 controller and a chipselect. Most SPI slaves don't support
15 SPI is widely used by microcontrollers to talk with sensors,
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.
21 SPI is one of a family of similar protocols using a four wire
26 if SPI
[all …]
|
| /openbmc/u-boot/drivers/mtd/spi/ |
| H A D | Kconfig | 1 menu "SPI Flash Support"
4 bool "Enable Driver Model for SPI flash"
7 Enable driver model for SPI flash. This SPI flash interface
9 implemented by the SPI flash uclass. There is one standard
10 SPI flash driver which knows how to probe most chips
14 during the transition parent. SPI and SPI flash must be
19 bool "Support sandbox SPI flash device"
23 provided instead. Drivers can be connected up to the sandbox SPI
24 bus (see CONFIG_SANDBOX_SPI) and SPI traffic will be routed to this
25 device. Typically the contents of the emulated SPI flash device is
[all …]
|
| /openbmc/linux/Documentation/driver-api/mtd/ |
| H A D | spi-nor.rst | 2 SPI NOR framework
8 SPI bus controllers (drivers/spi/) only deal with streams of bytes; the bus
11 arbitrary streams of bytes, but rather are designed specifically for SPI NOR.
14 find the right LUT sequence. Unfortunately, the SPI subsystem has no notion of
15 opcodes, addresses, or data payloads; a SPI controller simply knows to send or
18 details of the SPI NOR protocol.
23 This framework just adds a new layer between the MTD and the SPI bus driver.
24 With this new layer, the SPI NOR controller driver does not depend on the
33 SPI bus driver
35 SPI NOR chip
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/spi/ |
| H A D | spi-bus.txt | 1 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.
13 - compatible - name of SPI bus controller following generic names
16 No other properties are required in the SPI bus node. It is assumed
17 that a driver for an SPI bus device will understand that it is an SPI bus.
[all …]
|
| H A D | soft-spi.txt | 1 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 D | spi-atcspi200.txt | 1 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 D | Kconfig | 2 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 D | README.sandbox-spi | 1 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 D | status.txt | 1 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 D | spi-sprd.txt | 1 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 D | spi-davinci.txt | 1 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/Documentation/spi/ |
| H A D | spi-summary.rst | 2 Overview of Linux kernel SPI support
7 What is SPI?
9 The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial
12 standardization body. SPI uses a master/slave configuration.
22 SPI masters use a fourth "chip select" line to activate a given SPI slave
24 in parallel. All SPI slaves support chipselects; they are usually active
29 SPI slave functions are usually not interoperable between vendors
30 (except for commodities like SPI memory chips).
32 - SPI may be used for request/response style device protocols, as with
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
[all …]
|
| H A D | spidev.rst | 2 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
36 The following are the SPI device tables supported by the spidev driver:
50 You are encouraged to add an entry for your SPI device name to relevant
54 It used to be supported to define an SPI device using the "spidev" name.
56 is no longer supported by the Linux kernel and instead a real SPI device
59 Not having a real SPI device name will lead to an error being printed and
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | qca,qca7000.txt | 4 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
22 - spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at.
24 are invalid. Missing the property will set the SPI
26 - qca,legacy-mode : Set the SPI data transfer of the QCA7000 to legacy mode.
27 In this mode the SPI master must toggle the chip select
36 SPI Example:
[all …]
|
| /openbmc/linux/drivers/pinctrl/ |
| H A D | pinctrl-xway.c | 122 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),
186 GRP_MUX("spi", SPI, ase_pins_spi), /* DEPRECATED */
187 GRP_MUX("spi_di", SPI, ase_pins_spi_di),
188 GRP_MUX("spi_do", SPI, ase_pins_spi_do),
189 GRP_MUX("spi_clk", SPI, ase_pins_spi_clk),
[all …]
|
| /openbmc/linux/drivers/net/can/spi/ |
| H A D | Kconfig | 2 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/driver-api/ |
| H A D | spi.rst | 1 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.)
26 SPI shift register (maximizing throughput). Such drivers bridge between
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
[all …]
|
| /openbmc/u-boot/drivers/pinctrl/mscc/ |
| H A D | pinctrl-servalt.c | 130 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 D | Kconfig | 10 tristate "Analog Devices ADIS16080/100 Yaw Rate Gyroscope with SPI driver"
11 depends on SPI
14 Rate Gyroscope with SPI.
18 depends on SPI
33 tristate "Analog Devices ADIS16260 Digital Gyroscope Sensor SPI driver"
34 depends on SPI
45 tristate "Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver"
46 depends on SPI
57 tristate "Analog Devices ADXRS450/3 Digital Output Gyroscope SPI driver"
58 depends on SPI
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-dfsdm-adc-stm32 | 9 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/net/wireless/microchip/wilc1000/ |
| H A D | Kconfig | 6 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/linux/drivers/net/ieee802154/ |
| H A D | Kconfig | 27 depends on SPI
30 Say Y here to enable the at86rf230/231/233/212 SPI 802.15.4 wireless
39 depends on SPI
42 Say Y here to enable the MRF24J20 SPI 802.15.4 wireless
51 depends on SPI
53 Say Y here to enable the CC2520 SPI 802.15.4 wireless
72 depends on SPI
74 Say Y here to enable the ADF7242 SPI 802.15.4 wireless
84 depends on SPI
86 Say Y here to enable the CA8210 SPI 802.15.4 wireless
[all …]
|
| /openbmc/openbmc/meta-phosphor/dynamic-layers/aspeed-layer/recipes-bsp/u-boot/files/ |
| H A D | 0006-aspeed-Enable-SPI-master-mode-by-default.patch | 4 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.
28 + //pin switch by trap[13:12] -- [0:1] Enable SPI Master
29 + ast_scu_spi_master(1); /* enable SPI master */
|
| /openbmc/u-boot/doc/ |
| H A D | README.sh7753evb | 12 - SPI ROM 8MB
35 You can write MAC address to SPI ROM.
57 Update SPI ROM:
61 2. Probe SPI device.
64 3. Erase SPI ROM.
66 4. Write u-boot image to SPI ROM.
|