From: Kuldeep Singh <kuldeep.singh@nxp.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>, Kuldeep Singh <kuldeep.singh@nxp.com>
Subject: [PATCH 0/2] Resolve NXP flexspi bindings compatibility warnings
Date: Tue, 9 Mar 2021 16:44:23 +0530 [thread overview]
Message-ID: <20210309111425.3539755-1-kuldeep.singh@nxp.com> (raw)
This patches series aim is to resolve NXP flexspi bindings compatibility
warnings which were observed after running 'make dtbs_check' with
https://lore.kernel.org/linux-devicetree/20210309103528.3538910-1-kuldeep.singh@nxp.com/
patch applied.
Below error was observed:
/opt/samba/nxf51654/spi/arch/arm64/boot/dts/freescale/imx8mm-beacon-kit.dt.yaml: spi@30bb0000: clock-names:0: 'fspi_en' was expected
From schema: /opt/samba/nxf51654/spi/Documentation/devicetree/bindings/spi/nxp,spi-nxp-fspi.yaml
/opt/samba/nxf51654/spi/arch/arm64/boot/dts/freescale/imx8mm-beacon-kit.dt.yaml: spi@30bb0000: clock-names:1: 'fspi' was expected
From schema: /opt/samba/nxf51654/spi/Documentation/devicetree/bindings/spi/nxp,spi-nxp-fspi.yaml
Resolving above error may require reordering of flexspi clock-names entry.
Kuldeep Singh (2):
arm64: dts: imx8mm: Reorder flexspi clock-names entry
arm64: dts: imx8mn: Reorder flexspi clock-names entry
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 2 +-
arch/arm64/boot/dts/freescale/imx8mn.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2021-03-09 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 11:14 Kuldeep Singh [this message]
2021-03-09 11:14 ` [PATCH 1/2] arm64: dts: imx8mm: Reorder flexspi clock-names entry Kuldeep Singh
2021-03-09 11:14 ` [PATCH 2/2] arm64: dts: imx8mn: " Kuldeep Singh
2021-03-15 6:54 ` [PATCH 0/2] Resolve NXP flexspi bindings compatibility warnings 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=20210309111425.3539755-1-kuldeep.singh@nxp.com \
--to=kuldeep.singh@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.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