From: Krzysztof Kozlowski <krzk@kernel.org>
To: matthew.gerlach@linux.intel.com
Cc: lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
bhelgaas@google.com, krzk+dt@kernel.org, conor+dt@kernel.org,
dinguyen@kernel.org, joyce.ooi@intel.com,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, matthew.gerlach@altera.com,
peter.colberg@altera.com
Subject: Re: [PATCH v7 2/7] dt-bindings: intel: document Agilex PCIe Root Port
Date: Tue, 18 Feb 2025 08:25:39 +0100 [thread overview]
Message-ID: <3894efe9-fb8a-4a6f-bc50-ed54b6f7614d@kernel.org> (raw)
In-Reply-To: <dcd28035-6ba8-5d67-daa3-26812c4fc99d@linux.intel.com>
On 17/02/2025 16:47, matthew.gerlach@linux.intel.com wrote:
>
>
> On Sun, 16 Feb 2025, Krzysztof Kozlowski wrote:
>
>> On Sat, Feb 15, 2025 at 09:53:54AM -0600, Matthew Gerlach wrote:
>>> The Agilex7f devkit can support PCIe End Points with the appropriate
>>> daughter card.
>>>
>>> Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
>>> ---
>>> v7:
>>> - New patch to series.
>>> ---
>>> Documentation/devicetree/bindings/arm/intel,socfpga.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/intel,socfpga.yaml b/Documentation/devicetree/bindings/arm/intel,socfpga.yaml
>>> index 2ee0c740eb56..0da5810c9510 100644
>>> --- a/Documentation/devicetree/bindings/arm/intel,socfpga.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/intel,socfpga.yaml
>>> @@ -20,6 +20,7 @@ properties:
>>> - intel,n5x-socdk
>>> - intel,socfpga-agilex-n6000
>>> - intel,socfpga-agilex-socdk
>>> + - intel,socfpga-agilex7f-socdk-pcie-root-port
>>
>> Compatible should represent the board, so what is here exactly the
>> board? 7f? Agilex7f? socdk? Or is it standard agilex-socdk but with some
>> things attached?
>
> The board is the Agilex 7 FPGA F-Series Transceiver-Soc Development Kit:
> https://www.intel.com/content/www/us/en/products/details/fpga/development-kits/agilex/si-agf014.html
Isn't Agilex7 a SoC? I don't see it in the list of compatibles.
>
> There is not a single, standard agilex-socdk board. There are currently
> three variants. In addition to the F-Series socdk, there are I-Series and
> M-Series devkits:
> https://www.intel.com/content/www/us/en/products/details/fpga/development-kits/agilex/si-agi027.html
> https://www.intel.com/content/www/us/en/products/details/fpga/development-kits/agilex/agm039.html
Pages above show distinctive names for the boards, so I am confused why
they are not used.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-18 7:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 15:53 [PATCH v7 0/7] Add PCIe Root Port support for Agilex family of chips Matthew Gerlach
2025-02-15 15:53 ` [PATCH v7 1/7] dt-bindings: PCI: altera: Add binding for Agilex Matthew Gerlach
2025-02-15 15:53 ` [PATCH v7 2/7] dt-bindings: intel: document Agilex PCIe Root Port Matthew Gerlach
2025-02-16 11:56 ` Krzysztof Kozlowski
2025-02-17 15:47 ` matthew.gerlach
2025-02-18 7:25 ` Krzysztof Kozlowski [this message]
2025-02-18 22:51 ` matthew.gerlach
2025-02-15 15:53 ` [PATCH v7 3/7] arm64: dts: agilex: Fix fixed-clock schema warnings Matthew Gerlach
2025-02-16 11:58 ` Krzysztof Kozlowski
2025-02-18 21:44 ` matthew.gerlach
2025-02-19 23:53 ` matthew.gerlach
2025-02-15 15:53 ` [PATCH v7 4/7] arm64: dts: agilex: move bus@80000000 to socfpga_agilex.dtsi Matthew Gerlach
2025-02-15 15:53 ` [PATCH v7 5/7] arm64: dts: agilex: add dtsi for PCIe Root Port Matthew Gerlach
2025-02-15 15:53 ` [PATCH v7 6/7] arm64: dts: agilex: add dts enabling " Matthew Gerlach
2025-02-16 12:00 ` Krzysztof Kozlowski
2025-02-18 22:40 ` matthew.gerlach
2025-02-15 15:53 ` [PATCH v7 7/7] PCI: altera: Add Agilex support Matthew Gerlach
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=3894efe9-fb8a-4a6f-bc50-ed54b6f7614d@kernel.org \
--to=krzk@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=joyce.ooi@intel.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=matthew.gerlach@altera.com \
--cc=matthew.gerlach@linux.intel.com \
--cc=peter.colberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.