From: Dinh Nguyen <dinguyen@kernel.org>
To: niravkumarlaxmidas.rabara@altera.com,
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
Subject: Re: [PATCH 2/2] arm64: dts: socfpga: agilex5: add support for modular board
Date: Mon, 8 Dec 2025 20:47:06 -0600 [thread overview]
Message-ID: <8c394b32-b0b1-4096-a149-bc8923506549@kernel.org> (raw)
In-Reply-To: <20251202101652.2317844-3-niravkumarlaxmidas.rabara@altera.com>
On 12/2/25 04:16, niravkumarlaxmidas.rabara@altera.com wrote:
> From: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
>
> The Agilex5 Modular board consists of a compute module (Agilex5 SoCFPGA)
> attached to a carrier board that provides PCIe and additional system
> interfaces.
>
> Signed-off-by: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
> ---
> Note: This patch is based on socfpga maintainer's tree
> https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/log/?h=socfpga_dts_for_v6.19
>
> arch/arm64/boot/dts/intel/Makefile | 1 +
> .../intel/socfpga_agilex5_socdk_modular.dts | 109 ++++++++++++++++++
> 2 files changed, 110 insertions(+)
> create mode 100644 arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_modular.dts
>
> diff --git a/arch/arm64/boot/dts/intel/Makefile b/arch/arm64/boot/dts/intel/Makefile
> index a117268267ee..b15e9c5083b6 100644
> --- a/arch/arm64/boot/dts/intel/Makefile
> +++ b/arch/arm64/boot/dts/intel/Makefile
> @@ -5,6 +5,7 @@ dtb-$(CONFIG_ARCH_INTEL_SOCFPGA) += socfpga_agilex_n6000.dtb \
> socfpga_agilex3_socdk.dtb \
> socfpga_agilex5_socdk.dtb \
> socfpga_agilex5_socdk_013b.dtb \
> + socfpga_agilex5_socdk_modular.dtb \
> socfpga_agilex5_socdk_nand.dtb \
> socfpga_n5x_socdk.dtb
> dtb-$(CONFIG_ARCH_KEEMBAY) += keembay-evm.dtb
> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_modular.dts b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_modular.dts
> new file mode 100644
> index 000000000000..1831402d8808
> --- /dev/null
> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_modular.dts
> @@ -0,0 +1,109 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2025, Altera Corporation
> + */
> +#include "socfpga_agilex5.dtsi"
> +
> +/ {
> + model = "SoCFPGA Agilex5 SoCDK - Modular development kit";
> + compatible = "intel,socfpga-agilex5-socdk-modular", "intel,socfpga-agilex5";
> +
> + aliases {
> + serial0 = &uart0;
> + ethernet2 = &gmac2;
If gmac2 is the only active ethernet port, then use ethernet0.
Dinh
prev parent reply other threads:[~2025-12-09 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 10:16 [PATCH 0/2] Add support for Agilex5 SoCFPGA modular board niravkumarlaxmidas.rabara
2025-12-02 10:16 ` [PATCH 1/2] dt-bindings: intel: Add " niravkumarlaxmidas.rabara
2025-12-05 8:47 ` Krzysztof Kozlowski
2025-12-02 10:16 ` [PATCH 2/2] arm64: dts: socfpga: agilex5: add support for " niravkumarlaxmidas.rabara
2025-12-09 2:47 ` Dinh Nguyen [this message]
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=8c394b32-b0b1-4096-a149-bc8923506549@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niravkumarlaxmidas.rabara@altera.com \
--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