Home
last modified time | relevance | path

Searched full:spi (Results 1 – 25 of 422) sorted by relevance

12345678910>>...17

/Documentation/devicetree/bindings/spi/
Dqcom,spi-qup.txt1 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
11 "qcom,spi-qup-v1.1.1" for 8660, 8960 and 8064.
12 "qcom,spi-qup-v2.1.1" for 8974 and later
13 "qcom,spi-qup-v2.2.1" for 8974 v2 and later.
23 address on the SPI bus. Should be set to 1.
27 - spi-max-frequency: Specifies maximum SPI clock frequency,
29 Documentation/devicetree/bindings/spi/spi-bus.txt
32 The gpios will be referred to as reg = <index> in the SPI child
[all …]
Dspi-mt65xx.txt1 Binding for MTK SPI controller
5 - mediatek,mt2701-spi: for mt2701 platforms
6 - mediatek,mt2712-spi: for mt2712 platforms
7 - mediatek,mt6589-spi: for mt6589 platforms
8 - mediatek,mt6765-spi: for mt6765 platforms
9 - mediatek,mt7622-spi: for mt7622 platforms
10 - "mediatek,mt7629-spi", "mediatek,mt7622-spi": for mt7629 platforms
11 - mediatek,mt8135-spi: for mt8135 platforms
12 - mediatek,mt8173-spi: for mt8173 platforms
13 - mediatek,mt8183-spi: for mt8183 platforms
[all …]
Dnvidia,tegra114-spi.txt1 NVIDIA Tegra114 SPI controller.
4 - compatible : For Tegra114, must contain "nvidia,tegra114-spi".
5 Otherwise, must contain '"nvidia,<chip>-spi", "nvidia,tegra114-spi"' where
7 - reg: Should contain SPI registers location and length.
8 - interrupts: Should contain SPI interrupts.
10 - spi
14 - spi
24 - spi-max-frequency: Definition as per
25 Documentation/devicetree/bindings/spi/spi-bus.txt
29 Tegra SPI master with respect to outgoing Tegra SPI master clock.
[all …]
Dspi-controller.yaml4 $id: http://devicetree.org/schemas/spi/spi-controller.yaml#
7 title: SPI Controller Generic Binding
13 SPI busses can be described with a node for the SPI controller device
14 and a set of child nodes for each SPI slave on the bus. The system SPI
15 controller may be described for use in SPI master mode or in SPI slave mode,
20 pattern: "^spi(@.*|-[0-9a-f])*$"
50 spi-slave:
53 The SPI controller acts as a slave, instead of a master.
62 Compatible of the SPI device.
73 Compatible of the SPI device.
[all …]
Dbrcm,spi-bcm-qspi.txt1 Broadcom SPI controller
3 The Broadcom SPI controller is a SPI master found on various SOCs, including
4 BRCMSTB (BCM7XXX), Cygnus, NSP and NS2. The Broadcom Master SPI hw IP consits
6 MSPI : SPI master controller can read and write to a SPI slave device
7 BSPI : Broadcom SPI in combination with the MSPI hw IP provides acceleration
14 use SPI protocol.
19 Must be <1>, as required by generic SPI binding.
22 Must be <0>, also as required by generic SPI binding.
26 "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-qspi" : MSPI+BSPI on BRCMSTB SoCs
27 "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
[all …]
Dspi-samsung.txt1 * Samsung SPI Controller
3 The Samsung SPI controller is used to interface with various devices such as flash
4 and display controllers using the SPI communication interface.
9 - samsung,s3c2443-spi: for s3c2443, s3c2416 and s3c2450 platforms
10 - samsung,s3c6410-spi: for s3c6410 platforms
11 - samsung,s5pv210-spi: for s5pv210 and s5pc110 platforms
12 - samsung,exynos5433-spi: for exynos5433 compatible controllers
13 - samsung,exynos7-spi: for exynos7 platforms <DEPRECATED>
27 - clocks: specifies the clock IDs provided to the SPI controller; they are
32 the devices the names must be "spi", "spi_busclkN" (where N is determined by
[all …]
Dspi-bcm63xx.txt1 Binding for Broadcom BCM6348/BCM6358 SPI controller
4 - compatible: must contain one of "brcm,bcm6348-spi", "brcm,bcm6358-spi".
6 - interrupts: Interrupt for the SPI block.
7 - clocks: phandle of the SPI clock.
8 - clock-names: has to be "spi".
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.
20 spi@10000800 {
21 compatible = "brcm,bcm6368-spi", "brcm,bcm6358-spi";
[all …]
Dspi-lantiq-ssc.txt1 Lantiq Synchronous Serial Controller (SSC) SPI master driver
4 - compatible: "lantiq,ase-spi", "lantiq,falcon-spi", "lantiq,xrx100-spi"
5 - #address-cells: see spi-bus.txt
6 - #size-cells: see spi-bus.txt
7 - reg: address and length of the spi master registers
12 - clocks: spi clock phandle
13 - num-cs: see spi-bus.txt, set to 8 if unset
19 spi: spi@e100800 {
20 compatible = "lantiq,xrx200-spi", "lantiq,xrx100-spi";
Dicpdas-lp8841-spi-rtc.txt1 * ICP DAS LP-8841 SPI Controller for RTC
4 memory register, which acts as an SPI master device.
17 - compatible: should be "icpdas,lp8841-spi-rtc"
21 Requirements to SPI slave nodes:
25 - The spi slave node should claim the following flags which are
26 required by the spi controller.
28 - spi-3wire: The master itself has only 3 wire. It cannor work in
31 - spi-cs-high: DS-1302 has active high chip select line. The master
34 - spi-lsb-first: DS-1302 requires least significant bit first
40 spi@901c {
[all …]
Dqcom,spi-geni-qcom.txt1 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
11 - compatible: Must contain "qcom,geni-spi".
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
25 binding as described in Documentation/devicetree/bindings/spi/spi-bus.txt.
[all …]
Dspi-dw.txt1 Synopsys DesignWare SPI master
4 - compatible: should be "snps,designware-spi"
5 - #address-cells: see spi-bus.txt
6 - #size-cells: see spi-bus.txt
7 - reg: address and length of the spi master registers
9 - clocks: spi clock phandle
10 - num-cs: see spi-bus.txt
13 - cs-gpios: see spi-bus.txt
17 spi: spi@4020a000 {
18 compatible = "snps,designware-spi";
Dspi-sprd.txt1 Spreadtrum SPI Controller
4 - compatible: Should be "sprd,sc9860-spi".
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
[all …]
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
26 - clocks: spi clk phandle
35 and an args specifier containing the SPI device id
45 SPI slave nodes can contain the following properties.
[all …]
Dspi-pxa2xx.txt1 PXA2xx SSP SPI Controller
12 - cs-gpios: list of GPIO chip selects. See the SPI bus bindings,
13 Documentation/devicetree/bindings/spi/spi-bus.txt
14 - spi-slave: Empty property indicating the SPI controller is used in slave mode.
15 - ready-gpios: GPIO used to signal a SPI master that the FIFO is filled
18 Child nodes represent devices on the SPI bus
19 See ../spi/spi-bus.txt
22 ssp1: spi@d4035000 {
Dspi-stm32.txt1 STMicroelectronics STM32 SPI Controller
3 The STM32 SPI controller is used to communicate with external devices using
11 "st,stm32h7-spi"
12 "st,stm32f4-spi"
23 operation for SPI transfer.
27 - cs-gpios: list of GPIO chip selects. See the SPI bus bindings,
28 Documentation/devicetree/bindings/spi/spi-bus.txt
31 Child nodes represent devices on the SPI bus
32 See ../spi/spi-bus.txt
35 - st,spi-midi-ns: Only for STM32H7, (Master Inter-Data Idleness) minimum time
[all …]
Dspi-xlp.txt1 SPI Master controller for Netlogic XLP MIPS64 SOCs
4 Currently this SPI controller driver is supported for the following
9 - compatible : Should be "netlogic,xlp832-spi".
11 on the SPI bus.
14 - clocks : Phandle of the spi clock
17 SPI slave nodes must be children of the SPI master node and can contain
18 properties described in Documentation/devicetree/bindings/spi/spi-bus.txt.
22 spi: xlp_spi@3a100 {
23 compatible = "netlogic,xlp832-spi";
36 spi-max-frequency = <40000000>;
/Documentation/devicetree/bindings/mtd/
Daspeed-smc.txt2 * 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
28 property as specified in bindings/mtd/jedec,spi-nor.txt
30 Optionally, the child node can contain properties for SPI mode (may be
32 - spi-max-frequency - max frequency of spi bus
[all …]
Dnxp-spifi.txt1 * NXP SPI Flash Interface (SPIFI)
3 NXP SPIFI is a specialized SPI interface for serial Flash devices.
4 It supports one Flash device with 1-, 2- and 4-bits width in SPI
21 The SPI Flash must be a child of the SPIFI node and must have a
22 compatible property as specified in bindings/mtd/jedec,spi-nor.txt
25 - spi-cpol : Controller only supports mode 0 and 3 so either
26 both spi-cpol and spi-cpha should be present or
28 - spi-cpha : See above
29 - spi-rx-bus-width : Used to select how many pins that are used
32 See bindings/spi/spi-bus.txt for more information.
[all …]
/Documentation/devicetree/bindings/net/
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
18 - spi-cpha : Must be set
19 - spi-cpol : Must be set
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.
[all …]
/Documentation/devicetree/bindings/iio/adc/
Dti-adc084s021.txt5 - reg : SPI chip select number for the device
7 - spi-cpol : Per spi-bus bindings
8 - spi-cpha : Per spi-bus bindings
9 - spi-max-frequency : Per spi-bus bindings
16 spi-cpol;
17 spi-cpha;
18 spi-max-frequency = <16000000>;
/Documentation/devicetree/bindings/iio/resolver/
Dad2s90.txt7 - reg: SPI chip select number for the device
8 - spi-max-frequency: set maximum clock frequency, must be 830000
9 - spi-cpol and spi-cpha:
10 Either SPI mode (0,0) or (1,1) must be used, so specify none or both of
11 spi-cpha, spi-cpol.
14 Documentation/devicetree/bindings/spi/spi-bus.txt
20 implemented in the spi code, to satisfy it, SCLK's period should be at most
28 spi-max-frequency = <830000>;
29 spi-cpol;
30 spi-cpha;
/Documentation/networking/caif/
Dspi_porting.txt1 - CAIF SPI porting -
3 - CAIF SPI basics:
5 Running CAIF over SPI needs some extra setup, owing to the nature of SPI.
8 CAIF over SPI is a SPI slave chip and two GPIOs (more details below).
12 - CAIF SPI framework:
14 To make porting as easy as possible, the CAIF SPI has been divided in
16 generic functionality such as length framing, SPI frame negotiation
17 and SPI frame delivery and transmission. The other part is the CAIF
18 SPI slave device part, which is the module that you have to write if
19 you want to run SPI CAIF on a new hardware. This part takes care of
[all …]
/Documentation/driver-api/
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.)
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 …]
/Documentation/driver-api/mtd/
Dspi-nor.rst2 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 …]
/Documentation/devicetree/bindings/eeprom/
Dat25.txt1 EEPROMs (SPI) compatible with Atmel at25.
12 - spi-max-frequency : max spi frequency to use
20 - spi-cpha : SPI shifted clock phase, as per spi-bus bindings.
21 - spi-cpol : SPI inverse clock polarity, as per spi-bus bindings.
27 - at25,addr-mode : addr-mode flags, as defined in include/linux/spi/eeprom.h
36 spi-max-frequency = <5000000>;
37 spi-cpha;
38 spi-cpol;

12345678910>>...17