[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d9f160f-e155-4d2b-b598-d1dc76e49110@linaro.org>
Date: Mon, 25 Mar 2024 12:13:36 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tudor Ambarus <tudor.ambarus@...aro.org>,
krzysztof.kozlowski+dt@...aro.org, robh@...nel.org, conor+dt@...nel.org
Cc: alim.akhtar@...sung.com, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-kernel@...r.kernel.org, broonie@...nel.org, andi.shyti@...nel.org,
semen.protsenko@...aro.org, kernel-team@...roid.com,
willmcvicker@...gle.com, andre.draszik@...aro.org, peter.griffin@...aro.org
Subject: Re: [PATCH v2 5/7] ARM: dts: samsung: exynos5433: specify the SPI
FIFO depth
On 16/02/2024 15:04, Tudor Ambarus wrote:
> 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: Tudor Ambarus <tudor.ambarus@...aro.org>
> ---
> arch/arm64/boot/dts/exynos/exynos5433.dtsi | 5 +++++
This and next one has wrong subject prefix. I fixed it.
Best regards,
Krzysztof
Powered by blists - more mailing lists