From: Lukasz Majewski <lukma@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dts: nxp: mxs: Add descriptions for imx287 based btt3-[012] devices
Date: Thu, 29 Aug 2024 11:17:02 +0200 [thread overview]
Message-ID: <20240829111702.7ee999b6@wsk> (raw)
In-Reply-To: <CAOMZO5BOCOuf9t5uH1TfcWyoi-ECrw=3HztRVVXi0WR4K6EqZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Hi Fabio,
> Hi Lukasz,
>
> On Wed, Aug 28, 2024 at 8:21 AM Lukasz Majewski <lukma@denx.de> wrote:
> >
> > The btt3 device' HW revisions from 0 to 2 use imx287 SoC and are to
> > some extend similar to already upstreamed XEA devices, hence are
> > using common imx28-lwe.dtsi file.
> >
> > New, btt3.dtsi has been added to embrace common DTS properties for
> > different HW revisions for this device.
> >
> > As a result - changes introduced in btt3-[012].dts are minimal.
> >
> > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > ---
> > arch/arm/boot/dts/nxp/mxs/Makefile | 3 +
> > arch/arm/boot/dts/nxp/mxs/btt3-0.dts | 12 +
> > arch/arm/boot/dts/nxp/mxs/btt3-1.dts | 8 +
> > arch/arm/boot/dts/nxp/mxs/btt3-2.dts | 12 +
> > arch/arm/boot/dts/nxp/mxs/btt3.dtsi | 320
> > +++++++++++++++++++++++++++
>
> All the i.MX devicetrees start with the SoC name.
>
> What about naming them imx28-btt3-0.dts, imx28-btt3-1.dts and so on?
+1
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-08-29 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 11:21 [PATCH] dts: nxp: mxs: Add descriptions for imx287 based btt3-[012] devices Lukasz Majewski
2024-08-28 12:51 ` Rob Herring (Arm)
2024-08-28 14:05 ` Lukasz Majewski
2024-08-28 16:11 ` Rob Herring
2024-08-29 10:02 ` Lukasz Majewski
2024-08-28 16:54 ` Fabio Estevam
2024-08-29 9:17 ` Lukasz Majewski [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=20240829111702.7ee999b6@wsk \
--to=lukma@denx.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).