From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Josua Mayer <josua@solid-run.com>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 03/11] dt-bindings: marvell: a38x: add solidrun armada 388 clearfog boards
Date: Thu, 4 Jan 2024 09:41:58 +0100 [thread overview]
Message-ID: <099f3dfb-0557-4c8e-9e69-abc76463f659@linaro.org> (raw)
In-Reply-To: <20231230-support-clearfog-gtr-l8-sfp-v4-3-1d7f0e2c7128@solid-run.com>
On 30/12/2023 16:44, Josua Mayer wrote:
> Add DT compatible for SolidRun Armada-388 based Clearfog Base and Pro
> boards, which are already in place in-tree.
>
> There are already 3 distinct dts in tree for these *two* boards,
> declaring particular compatible strings:
> - armada-388-clearfog.dts:
> compatible = "solidrun,clearfog-a1", "marvell,armada388",
> "marvell,armada385, "marvell,armada380";
> - armada-388-clearfog-base.dts:
> compatible = "solidrun,clearfog-base-a1", "solidrun,clearfog-a1",
> "marvell,armada388", "marvell,armada385,
> "marvell,armada380";
> - armada-388-clearfog-pro.dts:
> compatible = "solidrun,clearfog-base-a1", "solidrun,clearfog-a1",
> "marvell,armada388", "marvell,armada385,
> "marvell,armada380";
Drop code from commit msg. Commit msg should explain why and what, not
copy the code.
>
> This has historic reasons, the first entry is a legacy name for the
> "pro" version, old versions of u-boot built when only one variant
> existed explicitly boot by this name.
>
> Note that both compatibles and model field include the string "A1".
> At least up to revision 2.0 of the board, this had been printed
> on the pcb. However in marketing material and conversations it is
> usually omitted. "Clearfog Pro" and "Clearfog Pro A1" always mean
> exactly the same product.
>
> Technically Base and Pro variants are similar enough that they can
> successfully boot with each other's dts. Hence it makes (some)
> sense for them to share the "clearfog-a1" compatible.
>
> Add bindings for the explicit variants including base / pro suffix.
> The legacy "armada-388-clearfog.dts" is not supported by these
> bindings" as it does not make sense having two bindings for one board.
>
> Signed-off-by: Josua Mayer <josua@solid-run.com>
> ---
> .../devicetree/bindings/arm/marvell/armada-38x.yaml | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml b/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml
> index 5af222e6db18..4950b840bf1c 100644
> --- a/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml
> +++ b/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml
> @@ -15,17 +15,14 @@ properties:
> compatible:
> oneOf:
>
> - - description: Armada 380 SoC
> - items:
> - - const: marvell,armada380
> -
> - - description: Armada 385 SoC
You just added these lines. It does not make sense to add them and
immediately remove. It's a noop.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-04 8:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 15:44 [PATCH v4 00/11] dt-bindings: marvell: a38x: add solidrun armada 388 clearfog boards Josua Mayer
2023-12-30 15:44 ` [PATCH v4 01/11] dt-bindings: marvell: a38x: remove invalid txt bindings for armada 38x SoCs Josua Mayer
2024-01-04 8:39 ` Krzysztof Kozlowski
2023-12-30 15:44 ` [PATCH v4 02/11] dt-bindings: marvell: a38x: convert the soc compatibles description to yaml Josua Mayer
2024-01-04 8:39 ` Krzysztof Kozlowski
2024-01-04 12:14 ` Josua Mayer
2023-12-30 15:44 ` [PATCH v4 03/11] dt-bindings: marvell: a38x: add solidrun armada 388 clearfog boards Josua Mayer
2024-01-04 8:41 ` Krzysztof Kozlowski [this message]
2023-12-30 15:44 ` [PATCH v4 04/11] dt-bindings: marvell: a38x: add kobol helios-4 board Josua Mayer
2024-01-04 8:43 ` Krzysztof Kozlowski
2024-01-04 12:28 ` Josua Mayer
2023-12-30 15:44 ` [PATCH v4 05/11] dt-bindings: marvell: a38x: add solidrun armada 385 clearfog gtr boards Josua Mayer
2024-01-04 8:43 ` Krzysztof Kozlowski
2023-12-30 15:44 ` [PATCH v4 06/11] arm: dts: marvell: clearfog: add pro variant compatible in legacy dts Josua Mayer
2023-12-30 15:44 ` [PATCH v4 07/11] arm: dts: marvell: clearfog-gtr: add board-specific compatible strings Josua Mayer
2023-12-30 15:44 ` [PATCH v4 08/11] arm: dts: marvell: clearfog-gtr: sort pinctrl nodes alphabetically Josua Mayer
2023-12-30 15:44 ` [PATCH v4 09/11] arm: dts: marvell: clearfog-gtr: add missing pinctrl for all used gpios Josua Mayer
2023-12-30 15:44 ` [PATCH v4 10/11] arm: dts: marvell: clearfog-gtr-l8: add support for second sfp connector Josua Mayer
2023-12-30 15:44 ` [PATCH v4 11/11] arm: dts: marvell: clearfog-gtr-l8: align port numbers with enclosure Josua Mayer
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=099f3dfb-0557-4c8e-9e69-abc76463f659@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=josua@solid-run.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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).