From: Martyn Welch <martyn.welch@collabora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Cc: kernel@collabora.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 2/2] arm64: dts: imx8mp-msc-sm2s: Add device trees for MSC SM2S-IMX8PLUS SoM and carrier board
Date: Fri, 12 Aug 2022 12:35:09 +0100 [thread overview]
Message-ID: <65a094d5d03ad8f7b35196c9dff6ffc6cf0ea151.camel@collabora.com> (raw)
In-Reply-To: <8962b7ed-a21c-0b7f-7a6d-5db3db84e4cb@linaro.org>
On Fri, 2022-08-12 at 12:47 +0300, Krzysztof Kozlowski wrote:
> On 12/08/2022 11:41, Martyn Welch wrote:
> > Add device trees for one of a number of MSC's (parent company,
> > Avnet)
> > variants of the SM2S-IMX8PLUS system on module along with the
> > compatible
> > SM2S-SK-AL-EP1 carrier board. As the name suggests, this family of
> > SoMs use
> > the NXP i.MX8MP SoC and provide the SMARC module interface.
> >
> > Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
> > ---
> >
> > Changes in v2
> > - Added compatibles
> > - Removed underscores from node names
> > - Make node names more generic
> > - Reorder properties
> > - Fix issues found by dtbs_check in these files
> >
> > Changes in v3:
> > - Switched to avnet vendor string in compatibles
> > - Corrected patch description
> >
> > Changes in v4:
> > - Switched from phy-reset-gpios to reset-gpios, removing
> > duplication
> > - Removed unneeded sdma1 node
> >
> > arch/arm64/boot/dts/freescale/Makefile | 1 +
> > .../freescale/imx8mp-msc-sm2s-14N0600E.dts | 72 ++
> > .../dts/freescale/imx8mp-msc-sm2s-ep1.dts | 53 ++
> > .../boot/dts/freescale/imx8mp-msc-sm2s.dtsi | 812
> > ++++++++++++++++++
> > 4 files changed, 938 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-
> > 14N0600E.dts
> > create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-
> > ep1.dts
> > create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-msc-
> > sm2s.dtsi
> >
> > diff --git a/arch/arm64/boot/dts/freescale/Makefile
> > b/arch/arm64/boot/dts/freescale/Makefile
> > index 8bf7f7ecebaa..139c8b95c9c9 100644
> > --- a/arch/arm64/boot/dts/freescale/Makefile
> > +++ b/arch/arm64/boot/dts/freescale/Makefile
> > @@ -83,6 +83,7 @@ dtb-$(CONFIG_ARCH_MXC) += imx8mn-venice-
> > gw7902.dtb
> > dtb-$(CONFIG_ARCH_MXC) += imx8mp-dhcom-pdk2.dtb
> > dtb-$(CONFIG_ARCH_MXC) += imx8mp-evk.dtb
> > dtb-$(CONFIG_ARCH_MXC) += imx8mp-icore-mx8mp-edimm2.2.dtb
> > +dtb-$(CONFIG_ARCH_MXC) += imx8mp-msc-sm2s-ep1.dtb
> > dtb-$(CONFIG_ARCH_MXC) += imx8mp-phyboard-pollux-rdk.dtb
> > dtb-$(CONFIG_ARCH_MXC) += imx8mp-tqma8mpql-mba8mpxl.dtb
> > dtb-$(CONFIG_ARCH_MXC) += imx8mp-venice-gw74xx.dtb
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-
> > 14N0600E.dts b/arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-
> > 14N0600E.dts
> > new file mode 100644
> > index 000000000000..9e976e8baaee
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-14N0600E.dts
> > @@ -0,0 +1,72 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright (C) 2022 Avnet Embedded GmbH
> > + */
> > +/dts-v1/;
> > +
> > +#include "imx8mp-msc-sm2s.dtsi"
> > +
> > +/ {
> > + model = "MSC SM2S-IMX8PLUS-QC6-14N0600E SoM";
> > + compatible = "avnet,sm2s-imx8mp-14N0600E", "avnet,sm2s-
> > imx8mp",
> > + "fsl,imx8mp";
>
> This does not match your bindings. Please test your DTS.
>
Hi Krzysztof,
I'm not sure I follow. This is the DTS for the SoM. The only way I can
test the SoM at the moment is on combination with the "EP1" carrier
board. That has been tested. The strings match those specified in the
bindings unless I'm being blind to something.
I guess I can build the DTB for just the SoM and boot with that or
thinking about it, rename this as a .dtsi, given that it's unlikely
that anyone is going to have a carrier barebones enough that it could
be considered just the SoM?
Martyn
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-08-12 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 8:41 [PATCH v4 1/2] dt-bindings: arm: fsl: Add MSC SM2S-IMX8PLUS SoM and SM2-MB-EP1 Carrier Martyn Welch
2022-08-12 8:41 ` [PATCH v4 2/2] arm64: dts: imx8mp-msc-sm2s: Add device trees for MSC SM2S-IMX8PLUS SoM and carrier board Martyn Welch
2022-08-12 9:47 ` Krzysztof Kozlowski
2022-08-12 11:35 ` Martyn Welch [this message]
2022-08-12 13:42 ` Krzysztof Kozlowski
2022-08-12 15:03 ` Martyn Welch
2022-08-12 17:31 ` Krzysztof Kozlowski
2022-08-15 7:45 ` Martyn Welch
2022-08-16 10:11 ` Krzysztof Kozlowski
2022-08-12 9:45 ` [PATCH v4 1/2] dt-bindings: arm: fsl: Add MSC SM2S-IMX8PLUS SoM and SM2-MB-EP1 Carrier Krzysztof Kozlowski
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=65a094d5d03ad8f7b35196c9dff6ffc6cf0ea151.camel@collabora.com \
--to=martyn.welch@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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
all inboxes | Powered by JetHome®