From: Rob Herring <robh@kernel.org>
To: Emekcan Aras <emekcan.aras@arm.com>
Cc: 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>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: Add Arm corstone500 platform
Date: Thu, 22 Dec 2022 12:49:29 -0600 [thread overview]
Message-ID: <20221222184929.GA1897073-robh@kernel.org> (raw)
In-Reply-To: <20221222123244.147238-3-emekcan.aras@arm.com>
On Thu, Dec 22, 2022 at 12:32:44PM +0000, Emekcan Aras wrote:
> Add bindings to describe implementation of
> the ARM Corstone500 platform.
>
> Signed-off-by: Emekcan Aras <emekcan.aras@arm.com>
> ---
> .../bindings/arm/arm,corstone500.yaml | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone500.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/arm,corstone500.yaml b/Documentation/devicetree/bindings/arm/arm,corstone500.yaml
> new file mode 100644
> index 000000000000..cfe41f7760fd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/arm,corstone500.yaml
> @@ -0,0 +1,30 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/arm,corstone500.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ARM Corstone500
It's 'Arm' now. :)
> +
> +maintainers:
> + - Emekcan Aras <emekcan.aras@arm.com>
> + - Rui Miguel Silva <rui.silva@linaro.org>
> +
> +description: |+
> + Corstone-500 is an ideal starting point for feature rich System on Chip
> + (SoC) designs based on the Cortex-A5 core. These designs can be used in
> + Internet of Things (IoT) and embedded products.
> +
> + Corstone-500 includes most of the Arm IP in the SSE-500 subsystem and
> + example integration layer, an FPGA, and access to modelling options.
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + items:
> + - const: arm,corstone500
> +
> +additionalProperties: true
> +
> +...
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2022-12-22 18:49 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 [this message]
2022-12-22 13:58 ` [PATCH v3 0/2] adds corstone500 device tree Krzysztof Kozlowski
2022-12-22 14:06 ` Krzysztof Kozlowski
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=20221222184929.GA1897073-robh@kernel.org \
--to=robh@kernel.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=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).