From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: Frank Li <Frank.Li@nxp.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: pierluigi.p@variscite.com,
Stefano Radaelli <stefano.r@variscite.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Mathieu Othacehe <othacehe@gnu.org>
Subject: [PATCH v4 0/3] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
Date: Fri, 20 Nov 2026 19:32:27 +0100 [thread overview]
Message-ID: <cover.1795197853.git.stefano.r@variscite.com> (raw)
This series adds Cortex-M33 overlays and combined DTBs for DART-MX93 on
Sonata and VAR-SOM-MX93 on Symphony.
The first patch corrects the Symphony resource table address. The second
moves the M33 reserved memory and remoteproc configuration into a common
include shared by both modules. The third adds the M33 overlays and
combined DTBs, and moves the common include from the module DTSI files to
the overlays. M33 memory is then reserved and remoteproc and MU1 are
enabled only in the M33 variants. The overlays also reserve the firmware's
peripherals and disable dependent devices.
Changes in v4:
- Add a separate fix for the Symphony resource table address, changing
it from 0x2021f000 to 0x2021e000 to match the firmware.
- Move all M33 reserved memory from both carrier DTS files into the
common include, using generic memory@ node names.
- Move memory-region-names into the common configuration extraction
patch and include the common file from both module DTSI files.
- Let the overlays provide the M33 memory reservations as well as the
remoteproc configuration by removing both module-level includes.
Changes in v3:
- Split the common configuration extraction and the M33 overlays into two
patches
- Use "reserved" for peripherals assigned to the M33 firmware; keep
"disabled" for dependent devices.
Changes in v2:
- Enable cm33 and MU1 only through the M33 overlay on DART-MX93.
Patch 2 uses the following binding and driver commits, already in
linux-next:
- ebb21cc5d1c0 ("dt-bindings: remoteproc: imx_rproc: Document
memory-region-names to avoid implicit ABI")
- 8396089f91fa ("remoteproc: imx_rpoc: Use memory-region-names to avoid
implicit ABI")
Stefano Radaelli (3):
arm64: dts: freescale: imx93-var-som: Fix resource table address
arm64: dts: freescale: imx93-var: Extract common Cortex-M33
configuration
arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
arch/arm64/boot/dts/freescale/Makefile | 9 +++
.../dts/freescale/imx93-var-common-m33.dtsi | 65 +++++++++++++++++++
.../freescale/imx93-var-dart-sonata-m33.dtso | 55 ++++++++++++++++
.../dts/freescale/imx93-var-dart-sonata.dts | 33 +---------
.../boot/dts/freescale/imx93-var-dart.dtsi | 14 ----
.../freescale/imx93-var-som-symphony-m33.dtso | 50 ++++++++++++++
.../dts/freescale/imx93-var-som-symphony.dts | 31 ---------
7 files changed, 180 insertions(+), 77 deletions(-)
create mode 100644 arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi
create mode 100644 arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso
create mode 100644 arch/arm64/boot/dts/freescale/imx93-var-som-symphony-m33.dtso
base-commit: 33adc96ac217d6e95b7c44ac383c19ca4ae2ff52
--
2.47.3
next reply other threads:[~2026-11-20 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 18:32 Stefano Radaelli [this message]
2026-11-20 18:32 ` [PATCH v4 1/3] arm64: dts: freescale: imx93-var-som: Fix resource table address Stefano Radaelli
2026-11-20 18:32 ` [PATCH v4 2/3] arm64: dts: freescale: imx93-var: Extract common Cortex-M33 configuration Stefano Radaelli
2026-11-20 18:32 ` [PATCH v4 3/3] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations Stefano Radaelli
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=cover.1795197853.git.stefano.r@variscite.com \
--to=stefano.radaelli21@gmail.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=othacehe@gnu.org \
--cc=pierluigi.p@variscite.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefano.r@variscite.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