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 v5 3/5] arm64: dts: agilex: add dtsi for PCIe Root Port
Date: Sun, 2 Feb 2025 20:02:19 +0100 [thread overview]
Message-ID: <2323e446-14fd-462e-9fd2-d707f7d3802d@kernel.org> (raw)
In-Reply-To: <56486d91-5ca-d85-eca1-1ce2df25238@linux.intel.com>
On 02/02/2025 19:49, matthew.gerlach@linux.intel.com wrote:
>
>
> On Sun, 2 Feb 2025, Krzysztof Kozlowski wrote:
>
>> On 01/02/2025 20:12, matthew.gerlach@linux.intel.com wrote:
>>>>
>>>>> they are also referenced in the following:
>>>>> Documentation/devicetree/bindings/soc/intel/intel,hps-copy-engine.yaml
>>>>> arch/arm64/boot/dts/intel/socfpga_agilex_n6000.dts
>>>>> I am not exactly sure where the right place is to define them, maybe
>>>>> Documentation/devicetree/bindings/arm/intel,socfpga.yaml. On the other
>>>>> hand, no code references these names; so it might make sense to just
>>>>> remove them.
>>>>
>>>> In general: nowhere, because simple bus does not have such properties.
>>>> It's not about reg-names only - you cannot have reg. You just did not
>>>> define here simple-bus.
>>>
>>> I understand. I will remove reg and reg-names.
>>
>> If you have there IO address space, then removal does not sound right,
>> either. You just need to come with the bindings for this dedicated
>> device, whatever this is. There is no description here, not much in
>> commit msg, so I don't know what is the device you are adding. PCI has
>> several bindings, so is this just host bridge?
>
> The device associated with two address ranges may be best described as a
> simple-bus. It is a bus between the CPU and the directly connected FPGA in
> the same package as the SOC. The design programmed into the FPGA
> determines the device(s) connected to the bus. The hardware implementing
So it is part of FPGA?
> this bus does have reset lines which allow for safely reprogramming the
Then it is not simple-bus. Simple-bus is our construct for simple
devices. You cannot have something a bit more complex and call it
simple-bus.
> FPGA while the SOC is running, which implies appropriate bindings as you
> suggest. Something like the following might make sense:
>
> aglx_hps_bridges: fpga-bus@80000000 {
> compatible = "altr,agilex-hps-fpga-bridge", "simple-bus";
FPGA bridge maybe, but not simple-bus. It does not look like a simple
bus if you have here some resources.
> reg = <0x80000000 0x20200000>,
> <0xf9000000 0x00100000>;
> reg-names = "axi_h2f", "axi_h2f_lw";
> #address-cells = <0x2>;
> #size-cells = <0x1>;
> ranges = <0x00000000 0x00000000 0x80000000 0x00040000>,
> <0x00000000 0x10000000 0x90100000 0x0ff00000>,
> <0x00000000 0x20000000 0xa0000000 0x00200000>,
> <0x00000001 0x00010000 0xf9010000 0x00008000>,
> <0x00000001 0x00018000 0xf9018000 0x00000080>,
> <0x00000001 0x00018080 0xf9018080 0x00000010>;
> reset = <&rst SOC2FPGA_RESET>, <&rst LWHPS2FPGA_RESET>;
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-02 19:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 17:35 [PATCH v5 0/5] Add PCIe Root Port support for Agilex family of chips Matthew Gerlach
2025-01-27 17:35 ` [PATCH v5 1/5] dt-bindings: PCI: altera: Add binding for Agilex Matthew Gerlach
2025-01-30 7:34 ` Krzysztof Kozlowski
2025-02-01 18:11 ` matthew.gerlach
2025-01-27 17:35 ` [PATCH v5 2/5] arm64: dts: agilex: add soc0 label Matthew Gerlach
2025-01-29 9:45 ` Krzysztof Kozlowski
2025-01-29 19:10 ` matthew.gerlach
2025-01-27 17:35 ` [PATCH v5 3/5] arm64: dts: agilex: add dtsi for PCIe Root Port Matthew Gerlach
2025-01-29 9:47 ` Krzysztof Kozlowski
2025-01-29 19:42 ` matthew.gerlach
2025-01-30 7:26 ` Krzysztof Kozlowski
2025-02-01 19:12 ` matthew.gerlach
2025-02-02 14:17 ` Krzysztof Kozlowski
2025-02-02 18:49 ` matthew.gerlach
2025-02-02 19:02 ` Krzysztof Kozlowski [this message]
2025-02-04 17:15 ` matthew.gerlach
2025-01-29 20:43 ` Frank Li
2025-02-01 18:07 ` matthew.gerlach
2025-01-27 17:35 ` [PATCH v5 4/5] arm64: dts: agilex: add dts enabling " Matthew Gerlach
2025-01-29 9:49 ` Krzysztof Kozlowski
2025-01-29 22:54 ` matthew.gerlach
2025-01-30 7:31 ` Krzysztof Kozlowski
2025-02-04 16:57 ` matthew.gerlach
2025-02-05 7:32 ` Krzysztof Kozlowski
2025-01-27 17:35 ` [PATCH v5 5/5] PCI: altera: Add Agilex support Matthew Gerlach
2025-01-29 9:50 ` Krzysztof Kozlowski
2025-01-29 23:03 ` matthew.gerlach
2025-02-03 14:18 ` Manivannan Sadhasivam
2025-02-03 14:42 ` 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=2323e446-14fd-462e-9fd2-d707f7d3802d@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 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).