From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH v2] ARM: dts: imx51: Remove invalid sahara compatible
Date: Mon, 9 Oct 2023 21:21:28 +0800 [thread overview]
Message-ID: <20231009132128.GC733979@dragon> (raw)
In-Reply-To: <20230925132220.955722-1-festevam@gmail.com>
On Mon, Sep 25, 2023 at 10:22:20AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Per fsl-imx-sahara.yaml, there shold not be a 'fsl,imx51-sahara'
s/shold/should
Fixed it up and applied, thanks!
Shawn
> compatible.
>
> Remove it to fix the following schema warning:
>
> imx51-apf51.dtb: crypto@83ff8000: compatible: ['fsl,imx53-sahara', 'fsl,imx51-sahara'] is too long
> from schema $id: http://devicetree.org/schemas/crypto/fsl-imx-sahara.yaml#
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> Changes since v1:
> - Fix the Subject line.
>
> arch/arm/boot/dts/nxp/imx/imx51.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/nxp/imx/imx51.dtsi b/arch/arm/boot/dts/nxp/imx/imx51.dtsi
> index 2b3195f5e32c..c96d6311dfa7 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx51.dtsi
> +++ b/arch/arm/boot/dts/nxp/imx/imx51.dtsi
> @@ -651,7 +651,7 @@ vpu: vpu@83ff4000 {
> };
>
> sahara: crypto@83ff8000 {
> - compatible = "fsl,imx53-sahara", "fsl,imx51-sahara";
> + compatible = "fsl,imx53-sahara";
> reg = <0x83ff8000 0x4000>;
> interrupts = <19 20>;
> clocks = <&clks IMX5_CLK_SAHARA_IPG_GATE>,
> --
> 2.34.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-10-09 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 13:22 [PATCH v2] ARM: dts: imx51: Remove invalid sahara compatible Fabio Estevam
2023-10-09 13:21 ` Shawn Guo [this message]
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=20231009132128.GC733979@dragon \
--to=shawnguo@kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).