mbox series

[v2,0/7] ARM: dts: samsung: specify the SPI FIFO depth

Message ID 20240216140449.2564625-1-tudor.ambarus@linaro.org
Headers
Series ARM: dts: samsung: specify the SPI FIFO depth |

Message

Tudor Ambarus Feb. 16, 2024, 2:04 p.m. UTC 
  Bindings patch sent but not yet integrated:
https://lore.kernel.org/linux-spi/20240216070555.2483977-2-tudor.ambarus@linaro.org/

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@linaro.org/

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(+)

Comments

Krzysztof Kozlowski Feb. 22, 2024, 8:49 a.m. UTC | #1 
On 16/02/2024 15:04, Tudor Ambarus wrote:
> Bindings patch sent but not yet integrated:
> https://lore.kernel.org/linux-spi/20240216070555.2483977-2-tudor.ambarus@linaro.org/

I still wait for bindings to be applied. This means it might be too late
to apply it for this cycle. Just letting you know, that I did not forget
about this patchset.

Best regards,
Krzysztof
Tudor Ambarus Feb. 23, 2024, 5:37 a.m. UTC | #2 
On 2/22/24 08:49, Krzysztof Kozlowski wrote:
> On 16/02/2024 15:04, Tudor Ambarus wrote:
>> Bindings patch sent but not yet integrated:
>> https://lore.kernel.org/linux-spi/20240216070555.2483977-2-tudor.ambarus@linaro.org/
> 
> I still wait for bindings to be applied. This means it might be too late
> to apply it for this cycle. Just letting you know, that I did not forget
> about this patchset.
> 

Thanks, Krzysztof, no worries. I'll reply here once Mark queues the
bindings.

Cheers,
ta