From: Dinh Nguyen <dinguyen@kernel.org>
To: Petko Manolov <petko.manolov@konsulko.com>, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, arnemaximilian.richter@draeger.com,
martynas.grybauskas@draeger.com
Subject: Re: [PATCH v2 2/2] arm: dts: nxp: imx: Add devicetree files for M48
Date: Mon, 28 Sep 2026 09:31:56 -0500 [thread overview]
Message-ID: <ba275cd1-2d86-4ab1-a6e7-6758ddbc31c9@kernel.org> (raw)
In-Reply-To: <20260924183855.1393302-3-petko.manolov@konsulko.com>
Hi Petko,
On 9/24/26 13:38, Petko Manolov wrote:
> M48 is a heterogeneous board made by Draeger that is based on two
> independent cpus, that are monitoring each other. One of them is
> imx6, the other is Altera SoCFPGA Cyclone 5. The latter is booting
> independently off qspi.
>
> This one adds the DT for the two variants of M48 that are based on
> imx6q and imx6dl.
>
> Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> ---
> arch/arm/boot/dts/nxp/imx/Makefile | 2 +
> .../boot/dts/nxp/imx/imx6dl-draeger-m48.dts | 23 ++
> .../boot/dts/nxp/imx/imx6q-draeger-m48.dts | 23 ++
> .../boot/dts/nxp/imx/imx6qdl-draeger-m48.dtsi | 369 ++++++++++++++++++
> .../boot/dts/nxp/imx/imx6qp-draeger-m48.dts | 78 ++++
> 5 files changed, 495 insertions(+)
> create mode 100644 arch/arm/boot/dts/nxp/imx/imx6dl-draeger-m48.dts
> create mode 100644 arch/arm/boot/dts/nxp/imx/imx6q-draeger-m48.dts
> create mode 100644 arch/arm/boot/dts/nxp/imx/imx6qdl-draeger-m48.dtsi
> create mode 100644 arch/arm/boot/dts/nxp/imx/imx6qp-draeger-m48.dts
>
> diff --git a/arch/arm/boot/dts/nxp/imx/Makefile b/arch/arm/boot/dts/nxp/imx/Makefile
> index 1a2539fa19b4..44b393256235 100644
> --- a/arch/arm/boot/dts/nxp/imx/Makefile
> +++ b/arch/arm/boot/dts/nxp/imx/Makefile
> @@ -220,6 +220,8 @@ dtb-$(CONFIG_SOC_IMX6Q) += \
> imx6q-dmo-edmqmx6.dtb \
> imx6q-dms-ba16.dtb \
> imx6q-ds.dtb \
> + imx6q-draeger-m48.dtb \
> + imx6dl-draeger-m48.dtb \
> imx6q-emcon-avari.dtb \
Please remember to run get_maintainer on the file that you're
submitting. For this case, for the arch/arm/boot/dts/nxp, you need to
also Cc'd :
Frank Li <Frank.Li@nxp.com> (maintainer:ARM/FREESCALE IMX / MXC /
LAYERSCAPE ARM ARCHIT...)
Sascha Hauer <s.hauer@pengutronix.de> (maintainer:ARM/FREESCALE IMX /
MXC / LAYERSCAPE ARM ARCHIT...)
Pengutronix Kernel Team <kernel@pengutronix.de> (reviewer:ARM/FREESCALE
IMX / MXC / LAYERSCAPE ARM ARCHIT...)
Fabio Estevam <festevam@gmail.com> (reviewer:ARM/FREESCALE IMX / MXC /
LAYERSCAPE ARM ARCHIT...)
Dinh
prev parent reply other threads:[~2026-09-28 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 18:38 [PATCH v2 0/2] arm: dts: nxp: imx: add Draeger M48 CPU board Petko Manolov
2026-09-24 18:38 ` [PATCH v2 1/2] dt-bindings: arm: fsl: add Draeger M48 dual-cpu board Petko Manolov
2026-09-24 18:38 ` [PATCH v2 2/2] arm: dts: nxp: imx: Add devicetree files for M48 Petko Manolov
2026-09-28 14:31 ` Dinh Nguyen [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=ba275cd1-2d86-4ab1-a6e7-6758ddbc31c9@kernel.org \
--to=dinguyen@kernel.org \
--cc=arnemaximilian.richter@draeger.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martynas.grybauskas@draeger.com \
--cc=petko.manolov@konsulko.com \
--cc=robh@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®