From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>,
tsbogend@alpha.franken.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mips: lantiq: Document Lantiq SoC dt bindings
Date: Sun, 26 Mar 2023 16:54:24 +0200 [thread overview]
Message-ID: <3871e958-79aa-2b4c-3300-270a2eb8f8e8@linaro.org> (raw)
In-Reply-To: <20230326122942.870990-1-olek2@wp.pl>
On 26/03/2023 14:29, Aleksander Jan Bajkowski wrote:
> Document the legacy Lantiq device tree bindings.
This suggests you are documenting existing compatibles, but I do not see
them at all. Confusing.
> Compatible strings for xRX100 (ar9) and newer SoCs
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v5.18-rc4/source/Documentation/process/submitting-patches.rst#L586
> should be renamed and will be added later.
Subject: drop second/last, redundant "dt bindings". The "dt-bindings"
prefix is already stating that these are bindings.
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
> .../devicetree/bindings/mips/lantiq/soc.yaml | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mips/lantiq/soc.yaml
>
> diff --git a/Documentation/devicetree/bindings/mips/lantiq/soc.yaml b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> new file mode 100644
> index 000000000000..90e8148b111b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/lantiq/soc.yaml
> @@ -0,0 +1,38 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mips/lantiq/soc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Lantiq SoC based Platform
> +
> +maintainers:
> + - Aleksander Jan Bajkowski <olek2@wp.pl>
> +
> +description:
> + Devices with a Lantiq CPU shall have the following properties.
> +
> +properties:
> + $nodename:
> + const: "/"
> + compatible:
> + oneOf:
> + - description: Boards with Lantiq Amazon-SE SoC
> + items:
> + - const: lantiq,ase
This does not look like proper board compatible. Boards have almost
always minimum two compatibles - one for SoC and one for board. With
commit msg this just adds to confusion...
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-26 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 12:29 Aleksander Jan Bajkowski
2023-03-26 14:54 ` Krzysztof Kozlowski [this message]
2023-03-27 21:21 ` Aleksander Bajkowski
2023-03-28 6:32 ` 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=3871e958-79aa-2b4c-3300-270a2eb8f8e8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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®