Bindings patch sent but not yet integrated: https://lore.kernel.org/linux-spi/20240216070555.2483977-2-tudor.ambarus@xxxxxxxxxx/ Up to now the SPI alias was used as an index into an array defined in the SPI driver to determine the SPI FIFO depth. Drop the dependency on the SPI alias and specify the SPI FIFO depth directly into the SPI node. Update all the device trees that have instances of the SPI IP with different FIFO depths. For the SoCs where all the SPI instances have the same FIFO depth (like gs101 and exynos850), the FIFO depth is inferred from the compatible. Similar SoCs shall do the same. v2: - use "fifo-depth" property (instead of "samsung,spi-fifosize") - update commit messages - reorder patches. Last is using common sense for determining the FIFO depth. The nodes are not enabled in any device tree, thus upstream will be fine even if comon sense fails. I guess we can update the device tree later on if needed. Or we can just drop the last patch. v1: https://lore.kernel.org/linux-spi/20240125151630.753318-1-tudor.ambarus@xxxxxxxxxx/ Tudor Ambarus (7): ARM: dts: samsung: exynos3250: specify the SPI FIFO depth ARM: dts: samsung: exynos4: specify the SPI FIFO depth ARM: dts: samsung: exynos5250: specify the SPI FIFO depth ARM: dts: samsung: exynos5420: specify the SPI FIFO depth ARM: dts: samsung: exynos5433: specify the SPI FIFO depth ARM: dts: samsung: exynosautov9: specify the SPI FIFO depth ARM: dts: samsung: s5pv210: specify the SPI FIFO depth arch/arm/boot/dts/samsung/exynos3250.dtsi | 2 ++ arch/arm/boot/dts/samsung/exynos4.dtsi | 3 +++ arch/arm/boot/dts/samsung/exynos5250.dtsi | 3 +++ arch/arm/boot/dts/samsung/exynos5420.dtsi | 3 +++ arch/arm/boot/dts/samsung/s5pv210.dtsi | 2 ++ arch/arm64/boot/dts/exynos/exynos5433.dtsi | 5 +++++ arch/arm64/boot/dts/exynos/exynosautov9.dtsi | 12 ++++++++++++ 7 files changed, 30 insertions(+) -- 2.44.0.rc0.258.g7320e95886-goog
