From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: devicetree@vger.kernel.org,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
soc@kernel.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>,
"Marek Vasut" <marex@denx.de>,
"Frieder Schrempf" <frieder.schrempf@kontron.de>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>,
"Andreas Kemnade" <andreas@kemnade.info>,
"Michal Vokáč" <michal.vokac@ysoft.com>,
"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
"Jesse Taube" <mr.bossman075@gmail.com>,
"Li Yang" <leoyang.li@nxp.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: dts: imx6q: Add Variscite MX6 Custom board support
Date: Thu, 20 Jul 2023 14:36:38 +0200 [thread overview]
Message-ID: <f67d710c-bacc-8480-a918-db84b82885e1@linaro.org> (raw)
In-Reply-To: <CADvTj4p72nh5umeSRw2OhjA5NyyZY_BkMhzJBn4Y2AHZHA3+dw@mail.gmail.com>
On 20/07/2023 14:22, James Hilliard wrote:
>> Take a look at IMX8 Variscite SoMs.
>
> Oh, I see what you mean now, so it looks like this is missing for the dart-mx6
> device tree.
>
> imx8mm-var-som.dtsi: compatible = "variscite,var-som-mx8mm", "fsl,imx8mm";
> imx8mm-var-som-symphony.dts: compatible =
> "variscite,var-som-mx8mm-symphony", "variscite,var-som-mx8mm",
> "fsl,imx8mm";
>
> imx6q-var-dt6customboard.dts: compatible =
> "variscite,dt6customboard", "fsl,imx6q";
>
> So the DART-MX6 is missing a compatible along the lines of
> "variscite,dart-imx6q"
> for the dart SoM I guess?
It's different topic whether it is worth to fix DART-MX6. In general it
misses its compatible, but it might be not worth to fix.
>
> And for VAR-SOM-MX6 I guess I should use something like
> "variscite,var-som-imx6q"
> for the SoM right?
Yes.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-07-20 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 22:41 [PATCH v2 1/2] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support James Hilliard
2023-07-19 22:41 ` [PATCH v2 2/2] ARM: dts: imx6q: Add Variscite MX6 Custom board support James Hilliard
2023-07-20 6:15 ` Krzysztof Kozlowski
2023-07-20 10:49 ` James Hilliard
2023-07-20 11:39 ` Krzysztof Kozlowski
2023-07-20 12:22 ` James Hilliard
2023-07-20 12:36 ` Krzysztof Kozlowski [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=f67d710c-bacc-8480-a918-db84b82885e1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=gregory.clement@bootlin.com \
--cc=james.hilliard1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=michal.vokac@ysoft.com \
--cc=mr.bossman075@gmail.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
--cc=stefan.wahren@chargebyte.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).