mirror of
https://github.com/u-boot/u-boot.git
synced 2025-05-03 02:03:01 +00:00
3d7f194597
Some boards don't have chipselect lines for leds so cs-gpios is not specified in the dts leading to probing error. Fix it by making behavior similar to the one in Linux, parse num-chipselects and if it is zero, ignore cs-gpios. Signed-off-by: Michael Polyntsov <michael.polyntsov@iopsys.eu> Signed-off-by: Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>
39 lines
1.2 KiB
Text
39 lines
1.2 KiB
Text
Soft SPI
|
|
|
|
The soft SPI bus implementation allows the use of GPIO pins to simulate a
|
|
SPI bus. No SPI host is required for this to work. The down-side is that the
|
|
performance will typically be much lower than a real SPI bus.
|
|
|
|
The soft SPI node requires the following properties:
|
|
|
|
Mandatory properties:
|
|
compatible: "spi-gpio"
|
|
cs-gpios: GPIOs to use for SPI chip select (output), not required if num-chipselects = <0>
|
|
sck-gpios: GPIO to use for SPI clock (output)
|
|
And at least one of:
|
|
mosi-gpios: GPIO to use for SPI MOSI line (output)
|
|
miso-gpios: GPIO to use for SPI MISO line (input)
|
|
|
|
Optional properties:
|
|
spi-delay-us: Number of microseconds of delay between each CS transition
|
|
num-chipselects: Number of chipselect lines
|
|
|
|
The GPIOs should be specified as required by the GPIO controller referenced.
|
|
The first cell holds the phandle of the controller and the second cell
|
|
typically holds the GPIO number.
|
|
|
|
|
|
Example:
|
|
|
|
soft-spi {
|
|
compatible = "spi-gpio";
|
|
cs-gpios = <&gpio 235 0>; /* Y43 */
|
|
sck-gpios = <&gpio 225 0>; /* Y31 */
|
|
mosi-gpios = <&gpio 227 0>; /* Y33 */
|
|
miso-gpios = <&gpio 224 0>; /* Y30 */
|
|
spi-delay-us = <1>;
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
cs@0 {
|
|
};
|
|
};
|