From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: jaswinder.singh@linaro.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
ilias.apalodimas@linaro.org, masahisa.kojima@linaro.org
Subject: Re: [PATCHv2] dt-bindings: arm: socionext: add Synquacer platforms
Date: Tue, 20 Jun 2023 19:16:25 +0200 [thread overview]
Message-ID: <5ae8c143-64cf-469d-b4f2-bed5bd9ee87b@linaro.org> (raw)
In-Reply-To: <20230620170725.13794-1-jaswinder.singh@linaro.org>
On 20/06/2023 19:07, jaswinder.singh@linaro.org wrote:
> From: Jassi Brar <jaswinder.singh@linaro.org>
>
> Socionext's DeveloperBox is based on the SC2A11B SoC (Synquacer).
> Specify bindings for the platform and boards based on that.
>
> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
> ---
Attach changelog after ---.
> .../bindings/arm/socionext/synquacer.yaml | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/socionext/synquacer.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/socionext/synquacer.yaml b/Documentation/devicetree/bindings/arm/socionext/synquacer.yaml
> new file mode 100644
> index 000000000000..c582d9c31213
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/socionext/synquacer.yaml
> @@ -0,0 +1,29 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/socionext/synquacer.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Socionext Synquacer platform
> +
> +maintainers:
> + - Masahisa Kojima <masahisa.kojima@linaro.org>
> + - Jassi Brar <jaswinder.singh@linaro.org>
> +
> +description:
> + Socionext SC2A11B (Synquacer) SoC based boards
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatible:
> + oneOf:
> + - items:
> + - enum:
> + - socionext,developer-box
> + - socionext,synquacer
> + - const: socionext,sc2a11b
That's quite different change. What is synquacer in this case? You claim
now it is a board, but based on previous discussions and U-Boot source
it does not look like such. What's more, it does not match U-Boot
sources and there is no Linux user of this, so it contradicts points of
our previous discussion.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-20 17:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 3:58 [PATCH] dt-bindings: arm: socionext: add bindings for the Synquacer platform jaswinder.singh
2023-06-16 10:15 ` Krzysztof Kozlowski
2023-06-16 13:12 ` Jassi Brar
2023-06-16 10:15 ` Krzysztof Kozlowski
2023-06-16 16:23 ` Jassi Brar
2023-06-16 16:47 ` Krzysztof Kozlowski
2023-06-16 20:06 ` Jassi Brar
2023-06-16 20:34 ` Krzysztof Kozlowski
2023-06-16 23:18 ` Jassi Brar
2023-06-17 7:18 ` Krzysztof Kozlowski
2023-06-19 19:17 ` Jassi Brar
2023-06-20 6:27 ` Krzysztof Kozlowski
2023-06-20 16:50 ` Rob Herring
2023-06-20 17:08 ` Jassi Brar
2023-06-20 17:07 ` [PATCHv2] dt-bindings: arm: socionext: add Synquacer platforms jaswinder.singh
2023-06-20 17:16 ` Krzysztof Kozlowski [this message]
2023-06-20 17:24 ` Jassi Brar
2023-06-20 17:54 ` Krzysztof Kozlowski
2023-06-20 18:21 ` Jassi Brar
2023-06-21 15:36 ` [PATCHv3] " jaswinder.singh
2023-06-22 2:01 ` 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=5ae8c143-64cf-469d-b4f2-bed5bd9ee87b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahisa.kojima@linaro.org \
--cc=robh@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®