From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: krzysztof.kozlowski+dt@linaro.org, broonie@kernel.org
Cc: robh+dt@kernel.org, conor+dt@kernel.org, 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,
linux-spi@vger.kernel.org, andre.draszik@linaro.org,
peter.griffin@linaro.org, semen.protsenko@linaro.org,
kernel-team@android.com, willmcvicker@google.com,
Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH 4/7] ARM: dts: samsung: exynos5250: specify the SPI fifosize
Date: Thu, 25 Jan 2024 15:16:27 +0000 [thread overview]
Message-ID: <20240125151630.753318-5-tudor.ambarus@linaro.org> (raw)
In-Reply-To: <20240125151630.753318-1-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 size. Drop the dependency on
the SPI alias and specify the SPI FIFO size directly into the SPI node.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
---
arch/arm/boot/dts/samsung/exynos5250.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/samsung/exynos5250.dtsi b/arch/arm/boot/dts/samsung/exynos5250.dtsi
index 99c84bebf25a..8e81d49622b7 100644
--- a/arch/arm/boot/dts/samsung/exynos5250.dtsi
+++ b/arch/arm/boot/dts/samsung/exynos5250.dtsi
@@ -511,6 +511,7 @@ spi_0: spi@12d20000 {
clock-names = "spi", "spi_busclk0";
pinctrl-names = "default";
pinctrl-0 = <&spi0_bus>;
+ samsung,spi-fifosize = <256>;
};
spi_1: spi@12d30000 {
@@ -526,6 +527,7 @@ spi_1: spi@12d30000 {
clock-names = "spi", "spi_busclk0";
pinctrl-names = "default";
pinctrl-0 = <&spi1_bus>;
+ samsung,spi-fifosize = <64>;
};
spi_2: spi@12d40000 {
@@ -541,6 +543,7 @@ spi_2: spi@12d40000 {
clock-names = "spi", "spi_busclk0";
pinctrl-names = "default";
pinctrl-0 = <&spi2_bus>;
+ samsung,spi-fifosize = <64>;
};
mmc_0: mmc@12200000 {
--
2.43.0.429.g432eaa2c6b-goog
next prev parent reply other threads:[~2024-01-25 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:16 [PATCH 0/7] ARM: dts: samsung: specify the SPI fifosize Tudor Ambarus
2024-01-25 15:16 ` [PATCH 1/7] ARM: dts: samsung: s5pv210: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 2/7] ARM: dts: samsung: exynos3250: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 3/7] ARM: dts: samsung: exynos4: " Tudor Ambarus
2024-01-25 15:16 ` Tudor Ambarus [this message]
2024-01-25 15:16 ` [PATCH 5/7] ARM: dts: samsung: exynos5450: " Tudor Ambarus
2024-01-30 17:08 ` Henrik Grimler
2024-01-25 15:16 ` [PATCH 6/7] ARM: dts: samsung: exynos5433: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 7/7] ARM: dts: samsung: exynosautov9: " Tudor Ambarus
2024-01-25 15:53 ` [PATCH 0/7] ARM: dts: samsung: " Mark Brown
2024-01-25 15:56 ` Krzysztof Kozlowski
2024-02-01 10:33 ` 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=20240125151630.753318-5-tudor.ambarus@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--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=linux-spi@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@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;
as well as URLs for NNTP newsgroup(s).