From: Xu Yilun <yilun.xu@linux.intel.com>
To: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
Cc: Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
Tom Rix <trix@redhat.com>, Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mahesh Rao <mahesh.rao@altera.com>,
Ho Yin <adrian.ho.yin.ng@altera.com>,
Niravkumar L Rabara <nirav.rabara@altera.com>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Enable FPGA Manager support for Agilex5
Date: Thu, 13 Nov 2025 14:01:52 +0800 [thread overview]
Message-ID: <aRV0UCZD6fwnfWUE@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <cover.1763008269.git.khairul.anuar.romli@altera.com>
On Thu, Nov 13, 2025 at 12:43:54PM +0800, Khairul Anuar Romli wrote:
> This patch series adds device tree bindings, driver support, and DTS
> updates to enable FPGA Manager functionality for Intel Agilex5 SoC.
>
> These changes are intended to enable FPGA programming and management
> capabilities on Agilex5-based platforms.
>
> ---
> Notes:
> Patch #3 depends on "arm64: dts: intel: Add Agilex5 SVC node with memory
There is no patch #3 now. Should be Patch #2 ?
> region" from
> https://lore.kernel.org/all/3381ef56c1ff34a0b54cf76010889b5523ead825.1762387665.git.khairul.anuar.romli@altera.com/
>
> This patch series is applied on socfpga maintainer's tree
> https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/log/?h=socfpga_dts_for_v6.19
Given that, @Dinh Nguyen could you take the series if you are good?
Thanks,
Yilun
>
> Changes in v2:
> - Drop "fpga: stratix10-soc: Add support for Agilex5"
> - Add fallback compatible in DT
> ---
> Khairul Anuar Romli (2):
> dt-bindings: fpga: stratix10: add support for Agilex5
> arm64: dts: agilex5: add fpga-region and fpga-mgr nodes
>
> .../bindings/fpga/intel,stratix10-soc-fpga-mgr.yaml | 1 +
> arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 12 ++++++++++++
> 2 files changed, 13 insertions(+)
>
> --
> 2.43.7
>
>
next prev parent reply other threads:[~2025-11-13 6:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 4:43 [PATCH v2 0/2] Enable FPGA Manager support for Agilex5 Khairul Anuar Romli
2025-11-13 4:43 ` [PATCH v2 1/2] dt-bindings: fpga: stratix10: add " Khairul Anuar Romli
2025-11-13 5:51 ` Xu Yilun
2025-11-13 15:18 ` Conor Dooley
2025-11-14 1:31 ` Romli, Khairul Anuar
2025-11-13 4:43 ` [PATCH v2 2/2] arm64: dts: agilex5: add fpga-region and fpga-mgr nodes Khairul Anuar Romli
2025-11-13 5:55 ` Xu Yilun
2025-11-13 7:12 ` Krzysztof Kozlowski
2025-11-13 9:09 ` Romli, Khairul Anuar
2025-11-13 9:11 ` Krzysztof Kozlowski
2025-11-14 9:37 ` Xu Yilun
2025-11-13 7:11 ` Krzysztof Kozlowski
2025-11-13 6:01 ` Xu Yilun [this message]
2025-11-13 7:13 ` [PATCH v2 0/2] Enable FPGA Manager support for Agilex5 Krzysztof Kozlowski
2025-11-13 9:07 ` Romli, Khairul Anuar
2025-11-13 9:10 ` Krzysztof Kozlowski
2025-11-13 9:38 ` Romli, Khairul Anuar
2025-11-13 13:41 ` 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=aRV0UCZD6fwnfWUE@yilunxu-OptiPlex-7050 \
--to=yilun.xu@linux.intel.com \
--cc=adrian.ho.yin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=khairul.anuar.romli@altera.com \
--cc=krzk+dt@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh.rao@altera.com \
--cc=mdf@kernel.org \
--cc=nirav.rabara@altera.com \
--cc=robh@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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