From: Conor Dooley <conor@kernel.org>
To: "Romli, Khairul Anuar" <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>,
"Rao, Mahesh" <mahesh.rao@altera.com>,
"Ng, Adrian Ho Yin" <adrian.ho.yin.ng@altera.com>,
"Rabara, Niravkumar Laxmidas" <nirav.rabara@altera.com>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: fpga: stratix10: add support for Agilex5
Date: Mon, 17 Nov 2025 14:32:16 +0000 [thread overview]
Message-ID: <20251117-imprison-upstream-5c80b3a55169@spud> (raw)
In-Reply-To: <56a3a993-9e54-4468-8774-5ed350948ab5@altera.com>
[-- Attachment #1: Type: text/plain, Size: 3791 bytes --]
On Mon, Nov 17, 2025 at 03:02:11AM +0000, Romli, Khairul Anuar wrote:
> On 15/11/2025 1:59 am, Conor Dooley wrote:
> > On Fri, Nov 14, 2025 at 02:27:41PM +0800, Khairul Anuar Romli wrote:
> >> Agilex5 introduces changes in how reserved memory is mapped and accessed
> >> compared to previous SoC generations. Agilex5 compatible allows stratix10-
> >> FPGA manager driver to handle these changes.
> >>
> >> Fallback is added for driver probe and init that rely on matching of table
> >> and DT node.
> >>
> >> Reviewed-by: Xu Yilun <yilun.xu@intel.com>
> >> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
> >> ---
> >> Changes in v3:
> >> - Add description for Agilex5 Device
> >> - Add and define fallback to "intel,agilex-soc-fpga-mgr"
> >> - Validate against Agilex and Stratix10 (non-fallback) and Agilex5
> >> (fallback)
> >> Changes in v2:
> >> - No changes in this patch
> >> ---
> >> .../fpga/intel,stratix10-soc-fpga-mgr.yaml | 14 +++++++++++---
> >> 1 file changed, 11 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/fpga/intel,stratix10-soc-fpga-mgr.yaml b/Documentation/devicetree/bindings/fpga/intel,stratix10-soc-fpga-mgr.yaml
> >> index 6e536d6b28a9..8eb414163d08 100644
> >> --- a/Documentation/devicetree/bindings/fpga/intel,stratix10-soc-fpga-mgr.yaml
> >> +++ b/Documentation/devicetree/bindings/fpga/intel,stratix10-soc-fpga-mgr.yaml
> >> @@ -20,9 +20,17 @@ description:
> >>
> >> properties:
> >> compatible:
> >> - enum:
> >> - - intel,stratix10-soc-fpga-mgr
> >> - - intel,agilex-soc-fpga-mgr
> >> + oneOf:
> >> + - items:
> >> + - enum:
> >
> > This construct is redundant, "items: - enum" is the same as just having
> > "enum".
> > pw-bot: changes-requested
> >
> I've tried to look for some of the already merged bindings i.e
> arm/qcom.yaml (although all the properties has enum - constant
> combination), it is using items with enum. I tried to keep the enum without
> items but I keep getting error while validating the changes.
I literally told you what to change, so I don't know why you didn't just
do that. Replacing "items: - enum" with "enum" is what you need to do.
You didn't even include the error you got, so I cannot help you with
that at all, nor even if you did what I told you to do.
> Another option that I've validated is using the following changes.
>
> - enum:
> - - intel,stratix10-soc-fpga-mgr
> - - intel,agilex-soc-fpga-mgr
> + oneOf:
> + - description: Intel Stratix10 Devices
> + items:
> + - const: intel,stratix10-soc-fpga-mgr
These just have the same problem as your original patch.
"items: - const" is just the same as "const".
Since item "items" properties do not do anything other than bloat the
schema.
> + - description: Intel Agilex Devices
> + items:
> + - const: intel,agilex-soc-fpga-mgr
> + - description: Intel Agilex5 Devices
> + items:
> + - const: intel,agilex5-soc-fpga-mgr
> + - const: intel,agilex-soc-fpga-mgr
>
> The drawback of this is we will need to implement enum instead of
> constant for first element if we need to add new devices under "Intel
> Agilex5 Devices" in the future.
>
> Thanks.
>
> Best Regards,
> Khairul
>
> >> + - intel,stratix10-soc-fpga-mgr
> >> + - intel,agilex-soc-fpga-mgr
> >> +
> >> + - description: Agilex5 Device
> >> + items:
> >> + - enum:
> >> + - intel,agilex5-soc-fpga-mgr
> >> + - const: intel,agilex-soc-fpga-mgr
> >>
> >> required:
> >> - compatible
> >> --
> >> 2.43.7
> >>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-17 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:27 [PATCH v3 0/2] Enable FPGA Manager support for Agilex5 Khairul Anuar Romli
2025-11-14 6:27 ` [PATCH v3 1/2] dt-bindings: fpga: stratix10: add " Khairul Anuar Romli
2025-11-14 17:59 ` Conor Dooley
2025-11-17 3:02 ` Romli, Khairul Anuar
2025-11-17 14:32 ` Conor Dooley [this message]
2025-11-17 14:34 ` Conor Dooley
2025-11-18 0:07 ` Romli, Khairul Anuar
2025-11-18 0:51 ` Romli, Khairul Anuar
2025-11-14 6:27 ` [PATCH v3 2/2] arm64: dts: agilex5: add fpga-region and fpga-mgr nodes Khairul Anuar Romli
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=20251117-imprison-upstream-5c80b3a55169@spud \
--to=conor@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).