From: Michal Simek <michal.simek@amd.com>
To: Conor Dooley <conor@kernel.org>, linux-spi@vger.kernel.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Jun Guo <Jun.Guo@cixtech.com>, Mark Brown <broonie@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] arm64: dts: xilinx: add soc-specific spi compatibles for zynqmp/versal-net
Date: Thu, 2 Oct 2025 08:06:47 +0200 [thread overview]
Message-ID: <101a83ba-cd2b-4080-aaa3-630652c33786@amd.com> (raw)
In-Reply-To: <20251001-cheesy-shucking-c55431bbcae3@spud>
On 10/1/25 20:31, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Unlike zynq, which has a specific compatible for the Cadence spi
> controller, zynqmp and versal-net do not have specific compatibles.
> In order to "encourage" people to use soc-specific compatibles for new
> devices using this IP, add specific compatibles for these devices, with
> a fallback to the existing compatible for the r1p6 version of the IP so
> that there will be no functional change.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> CC: Jun Guo <Jun.Guo@cixtech.com>
> CC: Mark Brown <broonie@kernel.org>
> CC: Rob Herring <robh@kernel.org>
> CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
> CC: Conor Dooley <conor+dt@kernel.org>
> CC: Michal Simek <michal.simek@amd.com>
> CC: linux-spi@vger.kernel.org
> CC: devicetree@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: linux-arm-kernel@lists.infradead.org
> ---
> arch/arm64/boot/dts/xilinx/versal-net.dtsi | 4 ++--
> arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/xilinx/versal-net.dtsi b/arch/arm64/boot/dts/xilinx/versal-net.dtsi
> index fc9f49e57385..38af1a4e34f7 100644
> --- a/arch/arm64/boot/dts/xilinx/versal-net.dtsi
> +++ b/arch/arm64/boot/dts/xilinx/versal-net.dtsi
> @@ -610,7 +610,7 @@ smmu: iommu@ec000000 {
> };
>
> spi0: spi@f1960000 {
> - compatible = "cdns,spi-r1p6";
> + compatible = "xlnx,versal-net-spi-r1p6", "cdns,spi-r1p6";
> status = "disabled";
> interrupts = <0 23 4>;
> reg = <0 0xf1960000 0 0x1000>;
> @@ -618,7 +618,7 @@ spi0: spi@f1960000 {
> };
>
> spi1: spi@f1970000 {
> - compatible = "cdns,spi-r1p6";
> + compatible = "xlnx,versal-net-spi-r1p6", "cdns,spi-r1p6";
> status = "disabled";
> interrupts = <0 24 4>;
> reg = <0 0xf1970000 0 0x1000>;
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> index e11d282462bd..89c565bef274 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> @@ -1076,7 +1076,7 @@ smmu: iommu@fd800000 {
> };
>
> spi0: spi@ff040000 {
> - compatible = "cdns,spi-r1p6";
> + compatible = "xlnx,zynqmp-spi-r1p6", "cdns,spi-r1p6";
> status = "disabled";
> interrupt-parent = <&gic>;
> interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>;
> @@ -1088,7 +1088,7 @@ spi0: spi@ff040000 {
> };
>
> spi1: spi@ff050000 {
> - compatible = "cdns,spi-r1p6";
> + compatible = "xlnx,zynqmp-spi-r1p6", "cdns,spi-r1p6";
> status = "disabled";
> interrupt-parent = <&gic>;
> interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>;
Acked-by: Michal Simek <michal.simek@amd.com>
Do you expect to go via SPI tree or via SOC tree?
Thanks,
Michal
next prev parent reply other threads:[~2025-10-02 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 18:31 [PATCH v1 1/2] spi: dt-bindings: cadence: add soc-specific compatible strings for zynqmp and versal-net Conor Dooley
2025-10-01 18:31 ` [PATCH v1 2/2] arm64: dts: xilinx: add soc-specific spi compatibles for zynqmp/versal-net Conor Dooley
2025-10-02 6:06 ` Michal Simek [this message]
2025-10-02 9:44 ` Conor Dooley
2025-10-13 6:36 ` Michal Simek
2025-10-02 6:05 ` [PATCH v1 1/2] spi: dt-bindings: cadence: add soc-specific compatible strings for zynqmp and versal-net Michal Simek
2025-10-02 15:44 ` (subset) " Mark Brown
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=101a83ba-cd2b-4080-aaa3-630652c33786@amd.com \
--to=michal.simek@amd.com \
--cc=Jun.Guo@cixtech.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
/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