| /OK3568_Linux_fs/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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/u-boot/drivers/mtd/nand/spi/ |
| H A D | Kconfig | 2 bool "SPI NAND device Support"
8 This is the framework for the SPI NAND device drivers.
13 bool "GIGADEVICE SPI flash support"
16 Add support for various GIGADEVICE SPI Nand flash chips
19 bool "MACRONIX SPI flash support"
22 Add support for various MACRONIX SPI Nand flash chips
25 bool "MICRON SPI flash support"
28 Add support for various MICRON SPI Nand flash chips
31 bool "TOSHIBA SPI flash support"
34 Add support for various TOSHIBA SPI Nand flash chips
[all …]
|
| /OK3568_Linux_fs/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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/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:
10 soft_spi_cs: GPIO number to use for SPI chip select (output)
11 soft_spi_sclk: GPIO number to use for SPI clock (output)
12 soft_spi_mosi: GPIO number to use for SPI MOSI line (output)
13 soft_spi_miso GPIO number to use for SPI MISO line (input)
|
| /OK3568_Linux_fs/kernel/drivers/mtd/spi-nor/controllers/ |
| H A D | Kconfig | 3 tristate "Aspeed flash controllers in SPI mode"
8 in the Aspeed AST2500/AST2400 SoCs when attached to SPI NOR chips,
9 and support for the SPI flash memory controller (SPI) for
10 the host firmware. The implementation only supports SPI NOR.
13 tristate "Hisilicon FMC SPI NOR Flash Controller(SFC)"
17 This enables support for HiSilicon FMC SPI NOR flash controller.
20 tristate "NXP SPI Flash Interface (SPIFI)"
24 Enable support for the NXP LPC SPI Flash Interface controller.
26 SPIFI is a specialized controller for connecting serial SPI
34 tristate "Intel PCH/PCU SPI flash PCI driver (DANGEROUS)"
[all …]
|
| /OK3568_Linux_fs/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):
|
| /OK3568_Linux_fs/kernel/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.
35 Set up the other device characteristics (bits per word, SPI clocking,
42 When you do that, the sysfs node for the SPI device will include a child
45 busybox; it's less featureful, but often enough.) For a SPI device with
54 as usual, the SPI device node will
55 be a child of its SPI master controller.
70 by having kernel code remove the SPI device, probably by removing the driver
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/pinctrl/ |
| H A D | pinctrl-xway.c | 125 MFP_XWAY(GPIO9, GPIO, ASC, SPI, EXIN),
126 MFP_XWAY(GPIO10, GPIO, ASC, SPI, NONE),
127 MFP_XWAY(GPIO11, GPIO, ASC, PCI, SPI),
129 MFP_XWAY(GPIO13, GPIO, EBU, SPI, NONE),
131 MFP_XWAY(GPIO15, GPIO, SPI, JTAG, NONE),
132 MFP_XWAY(GPIO16, GPIO, SPI, NONE, JTAG),
133 MFP_XWAY(GPIO17, GPIO, SPI, NONE, JTAG),
134 MFP_XWAY(GPIO18, GPIO, SPI, NONE, JTAG),
138 MFP_XWAY(GPIO22, GPIO, SPI, NONE, NONE),
252 GRP_MUX("spi", SPI, pins_spi),
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/media/spi/ |
| H A D | Kconfig | 4 comment "SPI I2C drivers auto-selected by 'Autoselect ancillary drivers'"
5 depends on MEDIA_HIDE_ANCILLARY_SUBDRV && SPI
7 menu "SPI helper chips"
12 depends on SPI && VIDEO_V4L2
31 if SPI
32 menu "Media SPI Adapters"
35 tristate "Sony CXD2880 SPI support"
36 depends on DVB_CORE && SPI
39 Choose if you would like to have SPI interface support for Sony CXD2880.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/spi/ |
| H A D | qcom,spi-geni-qcom.txt | 1 GENI based Qualcomm Universal Peripheral (QUP) Serial Peripheral Interface (SPI)
4 (an output FIFO and an input FIFO) for serial peripheral interface (SPI)
7 SPI in master mode supports up to 50MHz, up to four chip selects, programmable
12 - reg: Must contain SPI register location and length.
13 - interrupts: Must contain SPI controller interrupts.
17 the SPI bus.
20 SPI Controller nodes must be child of GENI based Qualcomm Universal
24 SPI slave nodes must be children of the SPI master node and conform to SPI bus
|
| 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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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_master
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mtd/ |
| H A D | aspeed-smc.txt | 2 * Aspeed SPI Flash Memory Controller
5 three chip selects, two of which are always of SPI type and the third
6 can be SPI or NOR type flash. These bindings only describe SPI.
8 The two SPI flash memory controllers in the AST2500 each support two
14 "aspeed,ast2400-spi" for the AST2400 SPI Flash memory Controller
16 "aspeed,ast2500-spi" for the AST2500 SPI flash memory controllers
27 The child nodes are the SPI flash modules which must have a compatible
30 Optionally, the child node can contain properties for SPI mode (may be
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/u-boot/drivers/rkflash/ |
| H A D | Kconfig | 13 Nand, SFC SPI Nand and SFC SPI Nor.
36 bool "Rockchip SFC SPI Nand Devices support"
40 This enables support for Rockchip SFC SPI Nand Devices.
44 Say Y when you have a board with SPI Nand Flash supported by Rockchip
47 bool "Rockchip SFC SPI Nor Devices Support"
50 This enables support for Rockchip SFC SPI Nor Devices.
54 Say Y when you have a board with SPI Nor Flash supported by Rockchip
|
| /OK3568_Linux_fs/kernel/drivers/net/dsa/microchip/ |
| H A D | Kconfig | 21 tristate "KSZ9477 series SPI connected switch driver"
22 depends on NET_DSA_MICROCHIP_KSZ9477 && SPI
25 Select to enable support for registering switches configured through SPI.
35 tristate "KSZ8795 series SPI connected switch driver"
36 depends on NET_DSA_MICROCHIP_KSZ8795 && SPI
39 This driver accesses KSZ8795 chip through SPI.
42 is through SPI.
|
| /OK3568_Linux_fs/kernel/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
31 This module adds support for the SPI interface of adapters using
33 Interface (SPI) that operates as a SPI slave. This SPI interface can
34 be used for control and for serial I/O of 802.11 data. The SPI is a
37 VDDIO. Select this if your platform is using the SPI bus.
|