From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Emekcan Aras <emekcan.aras@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Miguel Silva <rui.silva@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] adds corstone500 device tree
Date: Thu, 22 Dec 2022 15:06:53 +0100 [thread overview]
Message-ID: <9dec25fa-7bce-a715-b63e-0a71b5743e3d@linaro.org> (raw)
In-Reply-To: <20221222123244.147238-1-emekcan.aras@arm.com>
On 22/12/2022 13:32, 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.).
> 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?
Corstone1000 was accepted that way, so it is fine. I am just surprised
that if you are going to have silicons with it, there is no common
compatible and no shared DTSI.
What do you expect from customer? Re-implement and copy most of your DTS?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-22 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 12:32 [PATCH v3 0/2] adds corstone500 device tree Emekcan Aras
2022-12-22 12:32 ` [PATCH v3 1/2] arm: dts: arm: add arm " Emekcan Aras
2022-12-22 14:01 ` Krzysztof Kozlowski
[not found] ` <DBBPR08MB4838C52E20C5D6D0558FAA888EE89@DBBPR08MB4838.eurprd08.prod.outlook.com>
2022-12-22 15:24 ` Krzysztof Kozlowski
2022-12-22 22:20 ` kernel test robot
2022-12-23 0:01 ` kernel test robot
2022-12-23 8:26 ` Krzysztof Kozlowski
2022-12-23 11:14 ` Emekcan Aras
2022-12-30 23:24 ` kernel test robot
2022-12-22 12:32 ` [PATCH v3 2/2] dt-bindings: Add Arm corstone500 platform Emekcan Aras
2022-12-22 13:59 ` Krzysztof Kozlowski
2022-12-22 18:49 ` Rob Herring
2022-12-22 13:58 ` [PATCH v3 0/2] adds corstone500 device tree Krzysztof Kozlowski
2022-12-22 14:06 ` Krzysztof Kozlowski [this message]
2022-12-22 18:58 ` Rob Herring
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=9dec25fa-7bce-a715-b63e-0a71b5743e3d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=emekcan.aras@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.silva@linaro.org \
--cc=sudeep.holla@arm.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).