From: "Rob Herring (Arm)" <robh@kernel.org>
To: Bhavin Sharma <bhavin.sharma@siliconsignals.io>
Cc: shawnguo@kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
Peng Fan <peng.fan@nxp.com>,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
Hiago De Franco <hiago.franco@toradex.com>,
linux-arm-kernel@lists.infradead.org,
Max Merchel <Max.Merchel@ew.tq-group.com>,
Fabio Estevam <festevam@gmail.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Tim Harvey <tharvey@gateworks.com>,
Mathieu Othacehe <m.othacehe@gmail.com>,
Joao Paulo Goncalves <joao.goncalves@toradex.com>,
imx@lists.linux.dev, Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Michael Walle <mwalle@kernel.org>,
Gregor Herburger <gregor.herburger@ew.tq-group.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH 0/2] Add support Boundary Device Nitrogen8MP Universal SMARC Carrier Board
Date: Fri, 18 Oct 2024 07:52:27 -0500 [thread overview]
Message-ID: <172925539932.17706.4264141268818363923.robh@kernel.org> (raw)
In-Reply-To: <20241018091023.29286-1-bhavin.sharma@siliconsignals.io>
On Fri, 18 Oct 2024 14:39:26 +0530, Bhavin Sharma wrote:
> Add initial support for Nitrogen8MP Universal SMARC Carrier Board with
> Nitrogen8MP SMARC System on Module.
>
> Bhavin Sharma (2):
> arm64: dts: imx8mp: Add Boundary Device Nitrogen8MP Universal SMARC
> Carrier Board
> dt-bindings: arm: fsl: Add Boundary Device Nitrogen8MP Universal SMARC
> Carrier Board
>
> .../devicetree/bindings/arm/fsl.yaml | 6 +
> arch/arm64/boot/dts/freescale/Makefile | 1 +
> .../freescale/imx8mp-nitrogen-smarc-som.dtsi | 349 ++++++++++++++++++
> .../imx8mp-nitrogen-smarc-universal-board.dts | 17 +
> 4 files changed, 373 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-nitrogen-smarc-som.dtsi
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-nitrogen-smarc-universal-board.dts
>
> --
> 2.43.0
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y freescale/imx8mp-nitrogen-smarc-universal-board.dtb' for 20241018091023.29286-1-bhavin.sharma@siliconsignals.io:
arch/arm64/boot/dts/freescale/imx8mp-nitrogen-smarc-universal-board.dtb: /soc@0/bus@30800000/i2c@30ae0000/gpio@20: failed to match any schema with compatible: ['microchip,mcp23018']
prev parent reply other threads:[~2024-10-18 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 9:09 [PATCH 0/2] Add support Boundary Device Nitrogen8MP Universal SMARC Carrier Board Bhavin Sharma
2024-10-18 9:09 ` [PATCH 1/2] arm64: dts: imx8mp: Add " Bhavin Sharma
2024-10-22 6:10 ` Bhavin Sharma
2024-10-22 6:51 ` Shawn Guo
2024-10-18 9:09 ` [PATCH 2/2] dt-bindings: arm: fsl: " Bhavin Sharma
2024-10-18 13:45 ` Rob Herring (Arm)
2024-10-18 12:52 ` Rob Herring (Arm) [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=172925539932.17706.4264141268818363923.robh@kernel.org \
--to=robh@kernel.org \
--cc=Max.Merchel@ew.tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=bhavin.sharma@siliconsignals.io \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregor.herburger@ew.tq-group.com \
--cc=hiago.franco@toradex.com \
--cc=hvilleneuve@dimonoff.com \
--cc=imx@lists.linux.dev \
--cc=joao.goncalves@toradex.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=mwalle@kernel.org \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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