From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rui Miguel Silva <rui.silva@linaro.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: add corstone1000 platform
Date: Mon, 28 Mar 2022 11:19:18 -0500 [thread overview]
Message-ID: <YkHgBshQv0w1YS0t@robh.at.kernel.org> (raw)
In-Reply-To: <5c00707d-4e15-ef6b-2916-8d5bde5498d8@kernel.org>
On Fri, Mar 25, 2022 at 06:29:05PM +0100, Krzysztof Kozlowski wrote:
> On 25/03/2022 14:36, Rui Miguel Silva wrote:
> > Add bindings to describe the FPGA in a prototyping board
> > (MPS3) implementation and the Fixed Virtual Platform
> > implementation of the ARM Corstone1000 platform.
> >
> > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
> > ---
> > .../bindings/arm/arm,corstone1000.yaml | 45 +++++++++++++++++++
> > 1 file changed, 45 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone1000.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml b/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml
> > new file mode 100644
> > index 000000000000..a77f88223801
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml
> > @@ -0,0 +1,45 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/arm/arm,corstone1000.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: ARM Corstone1000 Device Tree Bindings
> > +
> > +maintainers:
> > + - Vishnu Banavath <vishnu.banavath@arm.com>
> > + - Rui Miguel Silva <rui.silva@linaro.org>
> > +
> > +description: |+
> > + ARM's Corstone1000 includes pre-verified Corstone SSE-710 subsystem that
> > + provides a flexible compute architecture that combines Cortex‑A and Cortex‑M
> > + processors.
> > +
> > + Support for Cortex‑A32, Cortex‑A35 and Cortex‑A53 processors. Two expansion
> > + systems for M-Class (or other) processors for adding sensors, connectivity,
> > + video, audio and machine learning at the edge System and security IPs to build
> > + a secure SoC for a range of rich IoT applications, for example gateways, smart
> > + cameras and embedded systems.
> > +
> > + Integrated Secure Enclave providing hardware Root of Trust and supporting
> > + seamless integration of the optional CryptoCell™-312 cryptographic
> > + accelerator.
> > +
> > +properties:
> > + $nodename:
> > + const: '/'
> > + compatible:
> > + oneOf:
> > + - description: Corstone1000 MPS3 it has 1 Cortex-A35 CPU core in a FPGA
> > + implementation of the Corstone1000 in the MPS3 prototyping board. See
> > + ARM document DAI0550.
> > + items:
> > + - const: arm,corstone1000-mps3
>
> If I understood correctly your description and DAI0550, the MPS3 board
> is a board with Corstone 100, so you miss here compatible for the chip
> (e.g. arm,corstone1000).
>
> I guess similar pattern for the FVP, so both should be combined within
> an enum (skipping all this description).
Corstone1000 is a collection of IP that would be the basis for an SoC.
These 2 are FVP and FPGA implementations of corstone1000 with additional
IP to make them usable (e.g. USB and ethernet). Each one as a whole is
a one off AIUI. So I don't think they really fit into our board plus SoC
compatible patten and are fine as-is.
Rob
next prev parent reply other threads:[~2022-03-28 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 13:36 [PATCH 0/2] arm64: dts: add corstone1000 device tree Rui Miguel Silva
2022-03-25 13:36 ` [PATCH 1/2] dt-bindings: arm: add corstone1000 platform Rui Miguel Silva
2022-03-25 17:29 ` Krzysztof Kozlowski
2022-03-28 16:19 ` Rob Herring [this message]
2022-03-25 17:34 ` Krzysztof Kozlowski
2022-03-25 13:36 ` [PATCH 2/2] arm64: dts: arm: add corstone1000 device tree Rui Miguel Silva
2022-03-25 17:46 ` Rob Herring
2022-03-28 16:35 ` Marc Zyngier
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=YkHgBshQv0w1YS0t@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--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).