devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Stefan Wahren" <stefan.wahren@i2se.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
	"Fabio Estevam" <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Fix bindings for APF28Dev board
Date: Sat, 21 Jan 2023 20:54:03 +0100	[thread overview]
Message-ID: <25a3eb81-dd0d-5c52-7f7a-a052d8ba46b4@linaro.org> (raw)
In-Reply-To: <20230121140053.10242-1-stefan.wahren@i2se.com>

On 21/01/2023 15:00, Stefan Wahren wrote:
> Adjust the compatibles for the APF28Dev board in order to fix the
> dtbs_check warning:
> 
>   DTC_CHK arch/arm/boot/dts/imx28-apf28dev.dtb
> /home/stefanw/torvalds/arch/arm/boot/dts/imx28-apf28dev.dtb: /: compatible:
>   oneOf' conditional failed, one must be fixed:
>   ['armadeus,imx28-apf28dev', 'armadeus,imx28-apf28', 'fsl,imx28'] is too long
>   ['armadeus,imx28-apf28dev', 'armadeus,imx28-apf28', 'fsl,imx28'] is too short
>   ...
> 
> Fixes: 3d735471d066 ("dt-bindings: arm: Document Armadeus SoM and Dev boards devicetree binding")
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
>  Documentation/devicetree/bindings/arm/fsl.yaml | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 3ba354578e8f..599e8fcec6bc 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -88,12 +88,18 @@ properties:
>          items:
>            - enum:
>                - armadeus,imx28-apf28      # APF28 SoM

Not related to your patch, but this looks odd. This is SoM, so even if
it was made a DTS, it cannot be standalone board. The DTS or the
compatible or both are misleading/incorrect.

For the patch:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

> -              - armadeus,imx28-apf28dev   # APF28 SoM on APF28Dev board
>                - fsl,imx28-evk
>                - i2se,duckbill
>                - i2se,duckbill-2
>                - technologic,imx28-ts4600
>            - const: fsl,imx28
Best regards,
Krzysztof


  parent reply	other threads:[~2023-01-21 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 14:00 [PATCH 1/2] dt-bindings: arm: fsl: Fix bindings for APF28Dev board Stefan Wahren
2023-01-21 14:00 ` [PATCH 2/2] dt-bindings: arm: Document the rest of i.MX28 based boards Stefan Wahren
2023-01-21 19:55   ` Krzysztof Kozlowski
2023-01-21 19:54 ` Krzysztof Kozlowski [this message]
2023-01-26  9:49 ` [PATCH 1/2] dt-bindings: arm: fsl: Fix bindings for APF28Dev board Shawn Guo

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=25a3eb81-dd0d-5c52-7f7a-a052d8ba46b4@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastien.szymanski@armadeus.com \
    --cc=shawnguo@kernel.org \
    --cc=stefan.wahren@i2se.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).