From: Krzysztof Kozlowski <krzk@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Adam Ford-BE <aford@beaconembedded.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: imx: Add Beacon i.MX8M Nano development kit
Date: Fri, 23 Oct 2020 13:16:32 +0200 [thread overview]
Message-ID: <20201023111632.GB48162@kozik-lap> (raw)
In-Reply-To: <CAHCN7xKLgNvMJP9YoP1eQa_f3-GLNj3ZSuvJA9RcF4OJufHhgg@mail.gmail.com>
On Fri, Oct 23, 2020 at 05:51:56AM -0500, Adam Ford wrote:
> > > diff --git a/arch/arm64/boot/dts/freescale/imx8mn-beacon-kit.dts b/arch/arm64/boot/dts/freescale/imx8mn-beacon-kit.dts
> > > new file mode 100644
> > > index 000000000000..faa55d888065
> > > --- /dev/null
> > > +++ b/arch/arm64/boot/dts/freescale/imx8mn-beacon-kit.dts
> > > @@ -0,0 +1,19 @@
> > > +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> > > +/*
> > > + * Copyright 2020 Compass Electronics Group, LLC
> > > + */
> > > +
> > > +/dts-v1/;
> > > +
> > > +#include "imx8mn.dtsi"
> > > +#include "imx8mn-beacon-som.dtsi"
> > > +#include "imx8mn-beacon-baseboard.dtsi"
> >
> > Why do you need baseboard as DTSI? Is is separate than kit? Judging by
> > contents look like just empty/fake DTS and the baseboard should be the
> > DTS.
> >
> > Another hint: Baseboard also does not have its compatible, so it cannot
> > exist in real life separate from the development kit...
>
> The baseboard can handle two separate, mutually exclusive video
> outputs. It has a LVDS bridge chip and an HDMI bridge chip, but
> without the DSI and LCDIF support, neither can function.
> Right now, that LVDS chip doesn't have an upstream driver, but I plan
> to introduce it once the LCDIF, and DSI interfaces are available and
> functional.
>
> Once there is video support, the kit-level DTS file will get support
> for one of the video outputs, and a second DTS file will get created
> to support the other. Both of these kit-level files would include the
> baseboard and SOM DTSI files since they would be common to both kits.
Sounds good.
>
> > > +
> > > +/ {
> > > + model = "Beacon EmbeddedWorks i.MX8M Mini Development Kit";
> > > + compatible = "beacon,imx8mn-beacon-kit", "fsl,imx8mn";
> >
> > Undocumented compatible.
>
> I am still trying to learn the YAML rules. Do I just add it to the
> fsl.yaml? 'beacon' is in the vendor-prefixes, but I looked and the
> 'imx8mm-beacon-kit' which is already in the kernel doesn't have a
> compatible either and they are virtually identical.
Enough will be adding it to the fsl.yaml. There is no strict need for
separate compatible for baseboard, although that's quite common practice
since you want to reuse it.
The beacon,imx8mm-beacon-kit is in fsl.yaml, so you can just duplicate
for imx8mn.
Best regards,
Krzysztof
_______________________________________________
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:[~2020-10-23 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 16:57 [PATCH] arm64: dts: imx: Add Beacon i.MX8M Nano development kit Adam Ford
2020-10-23 4:28 ` kernel test robot
2020-10-23 9:44 ` Krzysztof Kozlowski
2020-10-23 10:51 ` Adam Ford
2020-10-23 11:16 ` 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=20201023111632.GB48162@kozik-lap \
--to=krzk@kernel.org \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).