From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Niko Pasaloukos <nikolaos.pasaloukos@blaize.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "soc@kernel.org" <soc@kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"olof@lixom.net" <olof@lixom.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"sboyd@kernel.org" <sboyd@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>
Subject: Re: [PATCH 2/5] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC
Date: Thu, 6 Apr 2023 19:22:55 +0200 [thread overview]
Message-ID: <3381fecd-9b83-627f-c408-76fe387a9b5e@linaro.org> (raw)
In-Reply-To: <20230406102149.729726-3-nikolaos.pasaloukos@blaize.com>
On 06/04/2023 12:22, Niko Pasaloukos wrote:
> Add device tree bindings for the Blaize BLZP1600 CB2
> development board.
>
> Co-developed-by: James Cowgill <james.cowgill@blaize.com>
> Signed-off-by: James Cowgill <james.cowgill@blaize.com>
> Co-developed-by: Matt Redfearn <matt.redfearn@blaize.com>
> Signed-off-by: Matt Redfearn <matt.redfearn@blaize.com>
> Co-developed-by: Neil Jones <neil.jones@blaize.com>
> Signed-off-by: Neil Jones <neil.jones@blaize.com>
> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
> ---
> .../devicetree/bindings/arm/blaize.yaml | 28 +++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/blaize.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/blaize.yaml b/Documentation/devicetree/bindings/arm/blaize.yaml
> new file mode 100644
> index 000000000000..739115ba1fec
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/blaize.yaml
> @@ -0,0 +1,28 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/blaize.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Blaize Platforms Device Tree Bindings
If four of people were working on this, I would expect that at least one
person would point that it's not correct name. Start from recent
bindings. Drop Device Tree Bindings.
> +
> +maintainers:
> + - James Cowgill <james.cowgill@blaize.com>
> + - Matt Redfearn <matt.redfearn@blaize.com>
> + - Neil Jones <neil.jones@blaize.com>
> + - Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + oneOf:
> + - description: Blaize BLZP1600 based Boards
> + items:
> + - enum:
> + - blaize,blzp1600-som-cb2
som is not a board. You miss board compatible or this is a bit misleading.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-06 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 10:22 [PATCH 0/5] Add support for " Niko Pasaloukos
2023-04-06 10:22 ` [PATCH 1/5] dt-bindings: Add Blaize vendor prefix Niko Pasaloukos
2023-04-06 17:21 ` Krzysztof Kozlowski
2023-04-06 10:22 ` [PATCH 3/5] dt-bindings: reset: Add binding constants for BLZP1600 Niko Pasaloukos
2023-04-06 17:23 ` Krzysztof Kozlowski
2023-04-06 10:22 ` [PATCH 2/5] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Niko Pasaloukos
2023-04-06 17:22 ` Krzysztof Kozlowski [this message]
2023-04-06 10:22 ` [PATCH 4/5] dt-bindings: clock: Add binding constants for BLZP1600 Niko Pasaloukos
2023-04-06 17:24 ` Krzysztof Kozlowski
2023-04-06 10:22 ` [PATCH 5/5] arm64: Add initial support for Blaize BLZP1600 CB2 Niko Pasaloukos
2023-04-06 17:31 ` Krzysztof Kozlowski
2023-04-12 14:03 ` Rob Herring
2023-04-06 17:34 ` [PATCH 0/5] Add support for Blaize BLZP1600 SoC 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=3381fecd-9b83-627f-c408-76fe387a9b5e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=olof@lixom.net \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@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
all inboxes | Powered by JetHome®