From: Dinh Nguyen <dinguyen@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: socfpga: Add the Agilex7 series SoC's
Date: Thu, 16 Apr 2026 10:20:22 -0500 [thread overview]
Message-ID: <a75e4553-3db3-491c-a5af-a539e9c8da82@kernel.org> (raw)
In-Reply-To: <321be4a9-2633-403b-ac44-4ec9102f7d14@kernel.org>
On 4/14/26 07:55, Krzysztof Kozlowski wrote:
> On 14/04/2026 14:53, Dinh Nguyen wrote:
>>
>>
>> On 4/14/26 02:17, Krzysztof Kozlowski wrote:
>>> On Mon, Apr 13, 2026 at 09:45:52AM -0500, Dinh Nguyen wrote:
>>>> The Agilex7 is a series of devices from Altera that are derived from
>>>> the Agilex family.
>>>>
>>>> The Agilex7F device supports PCIE 4.0 and DDR4. The Agilex7I device supports
>>>> PCIE 5.0 and DDR4, while the Agilex7M device supports DDR4, DDR5, LPDDR5
>>>> and PCIE 5.0.
>>>>
>>>> All other peripherals from these devices are the same as the Agilex
>>>> device.
>>>>
>>>> Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
>>>> ---
>>>> Documentation/devicetree/bindings/arm/altera.yaml | 10 ++++++++++
>>>> 1 file changed, 10 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/arm/altera.yaml b/Documentation/devicetree/bindings/arm/altera.yaml
>>>> index 206686f3eebc..5ee09f8d4698 100644
>>>> --- a/Documentation/devicetree/bindings/arm/altera.yaml
>>>> +++ b/Documentation/devicetree/bindings/arm/altera.yaml
>>>> @@ -115,6 +115,16 @@ properties:
>>>> - intel,socfpga-agilex5-socdk-nand
>>>> - const: intel,socfpga-agilex5
>>>>
>>>> + - description: Agilex7 series F, I and M boards
>>>> + items:
>>>> + - enum:
>>>> + - intel,socfpga-agilex7m-socdk
>>>> + - enum:
>>>> + - intel,socfpga-agilex7f
>>>> + - intel,socfpga-agilex7i
>>>> + - intel,socfpga-agilex7m
>>>> + - const: intel,socfpga-agilex
>>>
>>> And separate question - why previous soc "agilex" is used as fallback?
>>> Even more confusing.
>>>
>>
>> You're right. Sorry for the confusion. The Agilex7M, I, F devices are
>> basically "agilex" devices with some few additions (PCIE, DDR5). Maybe I
>> should place the Agilex7M/I/F devices into the "agilex" boards area?
>
> Compatibles should be specific and not based on families, thus what is
> "intel,socfpga-agilex"? SoC, right?
>
> Then "intel,socfpgaa-agilex7f" is a new SoC, no?
>
The Agilex7 is re-branded name for the original Agilex soc,
"intel, socfga-agilex". From a software perspective, they are the same
device. I looked over the commits to see how I could handle a
rebranding, but couldn't come up with a conclusion.
I could create a new SoC like you've suggested:
+ - description: Agilex7m boards
+ items:
+ - enum:
+ - altr,socfpga-agilex7m-socdk
+ - const: altr,socfpga-agilex7m
+ - const: altr,socfpga-agilex7
Or I can use the original "intel,socfpga-agilex"?
+ - description: Agilex7m boards
+ items:
+ - enum:
+ - altr,socfpga-agilex7m-socdk
+ - const: altr,socfpga-agilex7m
+ - const: altr,socfpga-agilex
If I create a new "altr,socfpga-agilex7" binding, then I would have to
add the new binding to a few drivers. But if I use the original
"intel,socfpga-agilex", then no drivers will need to be updated.
Thanks,
Dinh
next prev parent reply other threads:[~2026-04-16 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 14:45 [PATCH 1/2] dt-bindings: socfpga: Add the Agilex7 series SoC's Dinh Nguyen
2026-04-13 14:45 ` [PATCH 2/2] arm64: dts: Add SoCFPGA Agilex7M devkit Dinh Nguyen
2026-04-14 7:16 ` [PATCH 1/2] dt-bindings: socfpga: Add the Agilex7 series SoC's Krzysztof Kozlowski
2026-04-14 7:17 ` Krzysztof Kozlowski
2026-04-14 12:53 ` Dinh Nguyen
2026-04-14 12:55 ` Krzysztof Kozlowski
2026-04-16 15:20 ` Dinh Nguyen [this message]
2026-04-17 6:43 ` 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=a75e4553-3db3-491c-a5af-a539e9c8da82@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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