[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <615ac44b-fd9b-332c-5ea0-8775cda8cb00@linaro.org>
Date: Mon, 30 May 2022 20:58:19 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Paweł Anikiel <pan@...ihalf.com>, soc@...nel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: arnd@...db.de, olof@...om.net, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, dinguyen@...nel.org
Subject: Re: [PATCH 3/3] dt-bindings: altera: Update Arria 10 boards
Subject is too generic, please describe what are you doing. Anything
could be an "update".
On 30/05/2022 15:08, Paweł Anikiel wrote:
> The Mercury+ AA1 is not a standalone board, rather it's a module with
> an Arria 10 SoC and some peripherals on it.
>
> The Google Chameleon v3 is a base board for the Mercury+ AA1.
>
> Signed-off-by: Paweł Anikiel <pan@...ihalf.com>
> ---
> Documentation/devicetree/bindings/arm/altera.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/altera.yaml b/Documentation/devicetree/bindings/arm/altera.yaml
> index 5e2017c0a051..c6e198bb5b29 100644
> --- a/Documentation/devicetree/bindings/arm/altera.yaml
> +++ b/Documentation/devicetree/bindings/arm/altera.yaml
> @@ -25,7 +25,7 @@ properties:
> items:
> - enum:
> - altr,socfpga-arria10-socdk
> - - enclustra,mercury-aa1
> + - google,chameleon-v3
As mentioned in patch 2, I would expect to have still enclustra
compatible. It's a SoM, so as usual it goes with its own binding, even
if not used standalone.
Best regards,
Krzysztof
Powered by blists - more mailing lists