[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221222185822.GB1897073-robh@kernel.org>
Date: Thu, 22 Dec 2022 12:58:22 -0600
From: Rob Herring <robh@...nel.org>
To: Emekcan Aras <emekcan.aras@....com>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
Liviu Dudau <liviu.dudau@....com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Sudeep Holla <sudeep.holla@....com>,
Miguel Silva <rui.silva@...aro.org>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] adds corstone500 device tree
On Thu, Dec 22, 2022 at 12:32:42PM +0000, Emekcan Aras wrote:
> Adds device tree and correspondent binding for ARM Corstone500 reference
> solution.
>
> Thanks for the comments, and sorry for the late reply. Most of the comments are
> addressed except one.
>
> @Krzysztof Kozlowski: Thanks a lot for the comments. I've tried to fixed all of
> them. Just have one question regarding having no dtsi or compatible platform.
> Corstone500 is a reference hardware design, however there is no silicon solution
> from it yet. And from device tree perspective, both FPGA and FVP (virtual
> platform) implementations are identical(same addresses and same nodes, etc.).
Does the FVP support virtio devices? Other FVP models do.
> So we didn't want to create a seperate dtsi file. What would you recommend here
> ? Can you point me to a device tree from a similar platform?
>
> Cheers,
> Emek
>
> Emekcan Aras (2):
> arm: dts: arm: add arm corstone500 device tree
> dt-bindings: Add Arm corstone500 platform
>
> .../bindings/arm/arm,corstone500.yaml | 30 +++
> arch/arm/boot/dts/Makefile | 3 +-
> arch/arm/boot/dts/corstone500.dts | 182 ++++++++++++++++++
> 3 files changed, 214 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone500.yaml
> create mode 100644 arch/arm/boot/dts/corstone500.dts
>
> --
> 2.25.1
>
>
Powered by blists - more mailing lists