From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: 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,
Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH v2 0/7] ARM: dts: samsung: specify the SPI FIFO depth
Date: Fri, 16 Feb 2024 14:04:42 +0000 [thread overview]
Message-ID: <20240216140449.2564625-1-tudor.ambarus@linaro.org> (raw)
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(+)
--
2.44.0.rc0.258.g7320e95886-goog
next reply other threads:[~2024-02-16 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 14:04 Tudor Ambarus [this message]
2024-02-16 14:04 ` [PATCH v2 1/7] ARM: dts: samsung: exynos3250: specify the SPI FIFO depth 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
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=20240216140449.2564625-1-tudor.ambarus@linaro.org \
--to=tudor.ambarus@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=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 read-only IMAP folder(s) and NNTP newsgroup(s).