From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
conor+dt@kernel.org
Cc: alim.akhtar@samsung.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
broonie@kernel.org, andi.shyti@kernel.org,
semen.protsenko@linaro.org, kernel-team@android.com,
willmcvicker@google.com, andre.draszik@linaro.org,
peter.griffin@linaro.org
Subject: Re: [PATCH v2 5/7] ARM: dts: samsung: exynos5433: specify the SPI FIFO depth
Date: Mon, 25 Mar 2024 12:13:36 +0100 [thread overview]
Message-ID: <1d9f160f-e155-4d2b-b598-d1dc76e49110@linaro.org> (raw)
In-Reply-To: <20240216140449.2564625-6-tudor.ambarus@linaro.org>
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@linaro.org>
> ---
> arch/arm64/boot/dts/exynos/exynos5433.dtsi | 5 +++++
This and next one has wrong subject prefix. I fixed it.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-25 11:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 14:04 [PATCH v2 0/7] ARM: dts: samsung: specify the SPI FIFO depth Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 1/7] ARM: dts: samsung: exynos3250: " Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 2/7] ARM: dts: samsung: exynos4: " Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 3/7] ARM: dts: samsung: exynos5250: " Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 4/7] ARM: dts: samsung: exynos5420: " Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 5/7] ARM: dts: samsung: exynos5433: " Tudor Ambarus
2024-03-25 11:13 ` Krzysztof Kozlowski [this message]
2024-03-25 12:45 ` Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 6/7] ARM: dts: samsung: exynosautov9: " Tudor Ambarus
2024-02-16 14:04 ` [PATCH v2 7/7] ARM: dts: samsung: s5pv210: " Tudor Ambarus
2024-02-22 8:49 ` [PATCH v2 0/7] ARM: dts: samsung: " Krzysztof Kozlowski
2024-02-23 5:37 ` Tudor Ambarus
2024-03-25 11:13 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d9f160f-e155-4d2b-b598-d1dc76e49110@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox