From: "Łukasz Majewski" <lukma@nabladev.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
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] arm64: dts: freescale: Add device tree definition for Cloos CBASE with i.MX8MM
Date: Wed, 11 Nov 2026 09:26:53 +0100 [thread overview]
Message-ID: <20261111092653.0df91d0d@wsk> (raw)
In-Reply-To: <CAOMZO5D0Eq0FDJq00x1aitQe1HoSzXk+DEfMo2Qv=nJB=Njdkg@mail.gmail.com>
Hi Fabio,
> Hi Lukasz,
>
> On Tue, Nov 10, 2026 at 12:06 PM Lukasz Majewski <lukma@nabladev.com>
> wrote:
> >
> > This commit adds support for CBASE board, which incorporates the
> > TQMa8MQML module.
> >
> > Signed-off-by: Lukasz Majewski <lukma@nabladev.com>
> > ---
> > .../arm64/boot/dts/freescale/imx8mm-cbase.dts | 577
> > ++++++++++++++++++
>
> You also need to document the board in
> Documentation/devicetree/bindings/arm/fsl.yaml
>
I've sent a separate patch for it (the same as in PHG).
> Make sure you run 'make dtbs_check' and that your patch does not
> introduce any warnings.
Yes, this shows no error (at least for the board, which I do add).
However, there are some issues found by AI review regarding the DTS
description.
--
Best regards,
Lukasz Majewski
--
Nabla Software Engineering GmbH
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Managing Director : Stefano Babic
next prev parent reply other threads:[~2026-11-11 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:05 [PATCH] arm64: dts: freescale: Add device tree definition for Cloos CBASE with i.MX8MM Lukasz Majewski
2026-11-10 15:27 ` sashiko-bot
2026-11-10 18:41 ` Fabio Estevam
2026-11-11 8:26 ` Łukasz Majewski [this message]
2026-11-11 8:54 ` Daniel Baluta
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=20261111092653.0df91d0d@wsk \
--to=lukma@nabladev.com \
--cc=Frank.Li@nxp.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.