Based on kernel version 6.14
. Page generated on 2025-04-02 08:20 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 | # SPDX-License-Identifier: GPL-2.0 %YAML 1.2 --- $id: http://devicetree.org/schemas/spi/spi-controller.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: SPI Controller Common Properties maintainers: - Mark Brown <broonie@kernel.org> description: | SPI busses can be described with a node for the SPI controller device and a set of child nodes for each SPI slave on the bus. The system SPI controller may be described for use in SPI master mode or in SPI slave mode, but not for both at the same time. properties: $nodename: pattern: "^spi(@.*|-([0-9]|[1-9][0-9]+))?$" "#address-cells": enum: [0, 1] "#size-cells": const: 0 cs-gpios: description: | GPIOs used as chip selects. If that property is used, the number of chip selects will be increased automatically with max(cs-gpios, hardware chip selects). So if, for example, the controller has 4 CS lines, and the cs-gpios looks like this cs-gpios = <&gpio1 0 0>, <0>, <&gpio1 1 0>, <&gpio1 2 0>; Then it should be configured so that num_chipselect = 4, with the following mapping cs0 : &gpio1 0 0 cs1 : native cs2 : &gpio1 1 0 cs3 : &gpio1 2 0 The second flag of a gpio descriptor can be GPIO_ACTIVE_HIGH (0) or GPIO_ACTIVE_LOW(1). Legacy device trees often use 0. There is a special rule set for combining the second flag of an cs-gpio with the optional spi-cs-high flag for SPI slaves. Each table entry defines how the CS pin is to be physically driven (not considering potential gpio inversions by pinmux): device node | cs-gpio | CS pin state active | Note ================+===============+=====================+===== spi-cs-high | - | H | - | - | L | spi-cs-high | ACTIVE_HIGH | H | - | ACTIVE_HIGH | L | 1 spi-cs-high | ACTIVE_LOW | H | 2 - | ACTIVE_LOW | L | Notes: 1) Should print a warning about polarity inversion. Here it would be wise to avoid and define the gpio as ACTIVE_LOW. 2) Should print a warning about polarity inversion because ACTIVE_LOW is overridden by spi-cs-high. Should be generally avoided and be replaced by spi-cs-high + ACTIVE_HIGH. The simplest way to obtain an active-high CS signal is to configure the controller's cs-gpio property with the ACTIVE_HIGH flag and set the peripheral's spi-cs-high property. See example below for a better understanding. fifo-depth: $ref: /schemas/types.yaml#/definitions/uint32 description: Size of the RX and TX data FIFOs in bytes. rx-fifo-depth: $ref: /schemas/types.yaml#/definitions/uint32 description: Size of the RX data FIFO in bytes. tx-fifo-depth: $ref: /schemas/types.yaml#/definitions/uint32 description: Size of the TX data FIFO in bytes. num-cs: $ref: /schemas/types.yaml#/definitions/uint32 description: Total number of chip selects. spi-slave: $ref: /schemas/types.yaml#/definitions/flag description: The SPI controller acts as a slave, instead of a master. slave: type: object properties: compatible: description: Compatible of the SPI device. required: - compatible patternProperties: "^.*@[0-9a-f]+$": type: object $ref: spi-peripheral-props.yaml additionalProperties: true properties: spi-3wire: $ref: /schemas/types.yaml#/definitions/flag description: The device requires 3-wire mode. spi-cpha: $ref: /schemas/types.yaml#/definitions/flag description: The device requires shifted clock phase (CPHA) mode. spi-cpol: $ref: /schemas/types.yaml#/definitions/flag description: The device requires inverse clock polarity (CPOL) mode. required: - compatible - reg dependencies: rx-fifo-depth: [ tx-fifo-depth ] tx-fifo-depth: [ rx-fifo-depth ] allOf: - if: not: required: - spi-slave then: properties: "#address-cells": const: 1 else: properties: "#address-cells": const: 0 - not: required: - fifo-depth - rx-fifo-depth - not: required: - fifo-depth - tx-fifo-depth additionalProperties: true examples: - | spi@80010000 { #address-cells = <1>; #size-cells = <0>; compatible = "fsl,imx28-spi"; reg = <0x80010000 0x2000>; interrupts = <96>; dmas = <&dma_apbh 0>; dma-names = "rx-tx"; display@0 { compatible = "lg,lg4573"; spi-max-frequency = <1000000>; reg = <0>; }; sensor@1 { compatible = "bosch,bme680"; spi-max-frequency = <100000>; reg = <1>; }; flash@2 { compatible = "jedec,spi-nor"; spi-max-frequency = <50000000>; reg = <2>, <3>; stacked-memories = /bits/ 64 <0x10000000 0x10000000>; }; }; - | #include <dt-bindings/gpio/gpio.h> spi@20204000 { #address-cells = <1>; #size-cells = <0>; compatible = "brcm,bcm2835-spi"; reg = <0x7e204000 0x1000>; interrupts = <2 22>; clocks = <&clk_spi>; cs-gpios = <&gpio 8 GPIO_ACTIVE_HIGH>; display@0 { compatible = "lg,lg4573"; spi-max-frequency = <1000000>; reg = <0>; spi-cs-high; }; }; |