| /kernel/linux/linux-5.10/drivers/spi/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/mtd/ |
| 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 …]
|
| D | intel-spi.rst | 5 Many Intel CPUs like Baytrail and Braswell include SPI serial flash host
7 Since contents of the SPI serial flash is crucial for machine to function,
11 Not all manufacturers protect the SPI serial flash, mainly because it
14 The intel-spi driver makes it possible to read and write the SPI serial
17 partial overwrites. By default the driver exposes SPI serial flash
21 Please keep in mind that overwriting the BIOS image on SPI serial flash
28 1) Download and extract the latest Minnowboard MAX BIOS SPI image
31 2) Install mtd-utils package [2]. We need this in order to erase the SPI
63 7) Erase the SPI serial flash. After this step, do not reboot the
73 9) Verify that the new content of the SPI serial flash matches the new
|
| /kernel/linux/linux-5.10/drivers/media/spi/ |
| 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
22 if SPI
23 menu "Media SPI Adapters"
26 tristate "Sony CXD2880 SPI support"
27 depends on DVB_CORE && SPI
30 Choose if you would like to have SPI interface support for Sony CXD2880.
|
| /kernel/linux/linux-5.10/drivers/mtd/spi-nor/controllers/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| 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
|
| 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
|
| 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 …]
|
| D | spi-bcm63xx-hsspi.txt | 1 Binding for Broadcom BCM6328 High Speed SPI controller
6 - interrupts: Interrupt for the SPI block.
7 - clocks: phandles of the SPI clock and the PLL clock.
9 - #address-cells: <1>, as required by generic SPI binding.
10 - #size-cells: <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | spi-bcm63xx.txt | 1 Binding for Broadcom BCM6348/BCM6358 SPI controller
6 - interrupts: Interrupt for the SPI block.
7 - clocks: phandle of the SPI clock.
9 - #address-cells: <1>, as required by generic SPI binding.
10 - #size-cells: <0>, also as required by generic SPI binding.
16 Child nodes as per the generic SPI binding.
|
| D | nvidia,tegra114-spi.txt | 1 NVIDIA Tegra114 SPI controller.
7 - reg: Should contain SPI registers location and length.
8 - interrupts: Should contain SPI interrupts.
29 Tegra SPI master with respect to outgoing Tegra SPI master clock.
30 Tap values vary based on the platform design trace lengths from Tegra SPI
33 with this tap value. This property is used to adjust the Tegra SPI master
34 clock with respect to the data from the SPI slave device.
35 Tap values vary based on the platform design trace lengths from Tegra SPI
|
| D | qcom,spi-qup.txt | 1 Qualcomm Universal Peripheral (QUP) Serial Peripheral Interface (SPI)
4 and an input FIFO) for serial peripheral interface (SPI) mini-core.
6 SPI in master mode supports up to 50MHz, up to four chip selects, programmable
23 address on the SPI bus. Should be set to 1.
27 - spi-max-frequency: Specifies maximum SPI clock frequency,
32 The gpios will be referred to as reg = <index> in the SPI child
33 nodes. If unspecified, a single SPI device without a chip
42 SPI slave nodes must be children of the SPI master node and can contain
|
| /kernel/linux/linux-5.10/drivers/net/can/spi/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/spi/ |
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/pinctrl/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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:
|
| /kernel/linux/linux-5.10/drivers/net/dsa/microchip/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/iio/gyro/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/microchip/wilc1000/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/nfc/ |
| D | st95hf.txt | 3 ST NFC Transceiver is required to attach with SPI bus.
4 ST95HF node should be defined in DT as SPI slave device of SPI
11 - reg: Address of SPI slave "ST95HF transceiver" on SPI master bus.
15 - spi-max-frequency: Max. operating SPI frequency for ST95HF
|
| /kernel/linux/linux-5.10/drivers/net/ieee802154/ |
| D | Kconfig | 27 depends on SPI
30 Say Y here to enable the at86rf230/231/233/212 SPI 802.15.4 wireless
46 depends on SPI
49 Say Y here to enable the MRF24J20 SPI 802.15.4 wireless
58 depends on SPI
60 Say Y here to enable the CC2520 SPI 802.15.4 wireless
79 depends on SPI
81 Say Y here to enable the ADF7242 SPI 802.15.4 wireless
91 depends on SPI
93 Say Y here to enable the CA8210 SPI 802.15.4 wireless
[all …]
|