Commit 65993c76 authored by Tudor Ambarus's avatar Tudor Ambarus Committed by Krzysztof Kozlowski

arm64: dts: exynos5433: specify the SPI FIFO depth

Up to now the SPI alias was used as an index into an array defined in
the SPI driver to determine the SPI FIFO depthj Drop the dependency on
the SPI alias and specify the SPI FIFO depth directly into the SPI node.

The FIFO depth were determined based on the SPI aliases that are defined
in exynos5433-tm2-common.dtsi:
	spi0 = &spi_0;
	spi1 = &spi_1;
	spi2 = &spi_2;
	spi3 = &spi_3;
	spi4 = &spi_4;
spi-s3c64xx.c driver defines the following fifo_lvl_mask for the
"samsung,exynos5433-spi" compatible:
	.fifo_lvl_mask  = { 0x1ff, 0x7f, 0x7f, 0x7f, 0x7f, 0x1ff},
Thus spi{0, 4} were considered having 256 byte FIFO depths, and
spi{1, 2, 3} having 64 byte FIFO depths. Update device tree with these
FIFO depths. No functional change expected.
Signed-off-by: default avatarTudor Ambarus <tudor.ambarus@linaro.org>
Link: https://lore.kernel.org/r/20240216140449.2564625-6-tudor.ambarus@linaro.orgSigned-off-by: default avatarKrzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
parent 4cece764
......@@ -1468,6 +1468,7 @@ spi_0: spi@14d20000 {
pinctrl-names = "default";
pinctrl-0 = <&spi0_bus>;
num-cs = <1>;
fifo-depth = <256>;
status = "disabled";
};
......@@ -1487,6 +1488,7 @@ spi_1: spi@14d30000 {
pinctrl-names = "default";
pinctrl-0 = <&spi1_bus>;
num-cs = <1>;
fifo-depth = <64>;
status = "disabled";
};
......@@ -1506,6 +1508,7 @@ spi_2: spi@14d40000 {
pinctrl-names = "default";
pinctrl-0 = <&spi2_bus>;
num-cs = <1>;
fifo-depth = <64>;
status = "disabled";
};
......@@ -1525,6 +1528,7 @@ spi_3: spi@14d50000 {
pinctrl-names = "default";
pinctrl-0 = <&spi3_bus>;
num-cs = <1>;
fifo-depth = <64>;
status = "disabled";
};
......@@ -1544,6 +1548,7 @@ spi_4: spi@14d00000 {
pinctrl-names = "default";
pinctrl-0 = <&spi4_bus>;
num-cs = <1>;
fifo-depth = <64>;
status = "disabled";
};
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment