* [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
@ 2026-11-19 9:06 Stefano Radaelli
2026-11-19 9:18 ` Daniel Baluta
0 siblings, 1 reply; 5+ messages in thread
From: Stefano Radaelli @ 2026-11-19 9:06 UTC (permalink / raw)
To: Frank Li, linux-kernel, devicetree, imx, linux-arm-kernel
Cc: pierluigi.p, Stefano Radaelli, Sascha Hauer,
Pengutronix Kernel Team, Fabio Estevam, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
From: Stefano Radaelli <stefano.r@variscite.com>
Add Cortex-M33 overlays and combined DTBs for DART-MX93 on Sonata and
VAR-SOM-MX93 on Symphony.
Share the remoteproc and mailbox configuration through a common include.
Reuse the reserved memory from each carrier DTS, preserving the different
resource table addresses.
Move the existing DART-MX93 remoteproc and MU1 configuration out of the
module DTSI so that they are enabled only by the M33 overlay. Use the
-m33 DTB when remoteproc support is needed.
Reserve the peripherals used by the M33 firmware and disable Wi-Fi,
Bluetooth and the devices depending on GPIO4. On Sonata, also disable USB
OTG1 because its USB-C role controller is unavailable.
Signed-off-by: Stefano Radaelli <stefano.r@variscite.com>
---
Changes in v2:
- Remove the cm33 and mu1 overrides from imx93-var-dart.dtsi,
enabling them only through the M33 overlay.
This patch uses the memory-region-names binding and driver support from
the following commits, both 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")
For dtbs_check on older trees, commit cebd1c0961d8 ("dt-bindings: gpio:
vf610: fix clock requirements per SoC"), also in linux-next, fixes the
pre-existing GPIO clock validation errors.
arch/arm64/boot/dts/freescale/Makefile | 9 +++
.../dts/freescale/imx93-var-common-m33.dtsi | 24 ++++++++
.../freescale/imx93-var-dart-sonata-m33.dtso | 55 +++++++++++++++++++
.../dts/freescale/imx93-var-dart-sonata.dts | 2 +-
.../boot/dts/freescale/imx93-var-dart.dtsi | 14 -----
.../freescale/imx93-var-som-symphony-m33.dtso | 50 +++++++++++++++++
6 files changed, 139 insertions(+), 15 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
diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
index cfd548284358..05a7556e9de9 100644
--- a/arch/arm64/boot/dts/freescale/Makefile
+++ b/arch/arm64/boot/dts/freescale/Makefile
@@ -956,8 +956,17 @@ dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxca-lvds-tm070jvhg33.dtb
dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxla-lvds-tm070jvhg33.dtb
dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxla-mini-ezurio-wlan.dtb
dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxla-mini-lvds-tm070jvhg33.dtb
+
+imx93-var-dart-sonata-m33-dtbs := imx93-var-dart-sonata.dtb imx93-var-dart-sonata-m33.dtbo
dtb-$(CONFIG_ARCH_MXC) += imx93-var-dart-sonata.dtb
+dtb-$(CONFIG_ARCH_MXC) += imx93-var-dart-sonata-m33.dtb
+dtb-$(CONFIG_ARCH_MXC) += imx93-var-dart-sonata-m33.dtbo
+
+imx93-var-som-symphony-m33-dtbs := imx93-var-som-symphony.dtb imx93-var-som-symphony-m33.dtbo
dtb-$(CONFIG_ARCH_MXC) += imx93-var-som-symphony.dtb
+dtb-$(CONFIG_ARCH_MXC) += imx93-var-som-symphony-m33.dtb
+dtb-$(CONFIG_ARCH_MXC) += imx93-var-som-symphony-m33.dtbo
+
dtb-$(CONFIG_ARCH_MXC) += imx93w-evk.dtb
dtb-$(CONFIG_ARCH_MXC) += imx93w-frdm.dtb
dtb-$(CONFIG_ARCH_MXC) += imx943-evk.dtb
diff --git a/arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi b/arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi
new file mode 100644
index 000000000000..51b4cfe143d4
--- /dev/null
+++ b/arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi
@@ -0,0 +1,24 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Common Cortex-M33 configuration for Variscite i.MX93 modules
+ *
+ * Copyright (C) 2026 Variscite Ltd. - https://www.variscite.com/
+ *
+ */
+
+/* Use the reserved memory and resource table address from the carrier DTS. */
+&cm33 {
+ mbox-names = "tx", "rx", "rxdb";
+ mboxes = <&mu1 0 1
+ &mu1 1 1
+ &mu1 3 1>;
+ memory-region = <&vdevbuffer>, <&vdev0vring0>, <&vdev0vring1>,
+ <&vdev1vring0>, <&vdev1vring1>, <&rsc_table>;
+ memory-region-names = "vdev0buffer", "vdev0vring0", "vdev0vring1",
+ "vdev1vring0", "vdev1vring1", "rsc-table";
+ status = "okay";
+};
+
+&mu1 {
+ status = "okay";
+};
diff --git a/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso
new file mode 100644
index 000000000000..d97da9916ef4
--- /dev/null
+++ b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso
@@ -0,0 +1,55 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Cortex-M33 support for Variscite DART-MX93 on Sonata-Board
+ *
+ * Link: https://variscite.com/carrier-boards/sonata-board/
+ *
+ * Copyright (C) 2026 Variscite Ltd. - https://www.variscite.com/
+ *
+ */
+
+/dts-v1/;
+/plugin/;
+
+#include "imx93-var-common-m33.dtsi"
+
+/* Reserve the peripherals used by the Cortex-M33 firmware. */
+&flexcan1 {
+ status = "disabled";
+};
+
+&gpio4 {
+ status = "disabled";
+};
+
+&lpspi5 {
+ status = "disabled";
+};
+
+/* Disable Bluetooth along with Wi-Fi and release the JTAG pins. */
+&lpuart5 {
+ status = "disabled";
+};
+
+&lpuart7 {
+ status = "disabled";
+};
+
+/* The USB-C role controller uses an interrupt on GPIO4. */
+&ptn5150 {
+ status = "disabled";
+};
+
+/* The USB-C role controller is unavailable. */
+&usbotg1 {
+ status = "disabled";
+};
+
+/* Wi-Fi reset is connected to GPIO4. */
+&usdhc3 {
+ status = "disabled";
+};
+
+&wifi_pwrseq {
+ status = "disabled";
+};
diff --git a/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts
index 1ca3ec8330d0..e3afd0efe5c7 100644
--- a/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts
+++ b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts
@@ -291,7 +291,7 @@ ft5x06_ts: touchscreen@38 {
};
/* USB Type-C Controller */
- typec@3d {
+ ptn5150: typec@3d {
compatible = "nxp,ptn5150";
reg = <0x3d>;
interrupt-parent = <&gpio4>;
diff --git a/arch/arm64/boot/dts/freescale/imx93-var-dart.dtsi b/arch/arm64/boot/dts/freescale/imx93-var-dart.dtsi
index 69495bb7fc9f..6c596d61bd21 100644
--- a/arch/arm64/boot/dts/freescale/imx93-var-dart.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx93-var-dart.dtsi
@@ -54,16 +54,6 @@ wifi_pwrseq: wifi-pwrseq {
};
};
-&cm33 {
- mbox-names = "tx", "rx", "rxdb";
- mboxes = <&mu1 0 1>,
- <&mu1 1 1>,
- <&mu1 3 1>;
- memory-region = <&vdevbuffer>, <&vdev0vring0>, <&vdev0vring1>,
- <&vdev1vring0>, <&vdev1vring1>, <&rsc_table>;
- status = "okay";
-};
-
&eqos {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&pinctrl_eqos>;
@@ -221,10 +211,6 @@ bluetooth {
};
};
-&mu1 {
- status = "okay";
-};
-
&mu2 {
status = "okay";
};
diff --git a/arch/arm64/boot/dts/freescale/imx93-var-som-symphony-m33.dtso b/arch/arm64/boot/dts/freescale/imx93-var-som-symphony-m33.dtso
new file mode 100644
index 000000000000..96860a2dbf7c
--- /dev/null
+++ b/arch/arm64/boot/dts/freescale/imx93-var-som-symphony-m33.dtso
@@ -0,0 +1,50 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
+/*
+ * Cortex-M33 support for Variscite VAR-SOM-MX93 on Symphony-Board
+ *
+ * Link: https://variscite.com/carrier-boards/symphony-board/
+ *
+ * Copyright (C) 2026 Variscite Ltd. - https://www.variscite.com/
+ *
+ */
+
+/dts-v1/;
+/plugin/;
+
+#include "imx93-var-common-m33.dtsi"
+
+/* The resistive touchscreen uses GPIO4. */
+&ads7846 {
+ status = "disabled";
+};
+
+/* Reserve the peripherals used by the Cortex-M33 firmware. */
+&flexcan1 {
+ status = "disabled";
+};
+
+&gpio4 {
+ status = "disabled";
+};
+
+&lpspi6 {
+ status = "disabled";
+};
+
+/* Disable Bluetooth along with Wi-Fi and release the JTAG pins. */
+&lpuart5 {
+ status = "disabled";
+};
+
+&lpuart7 {
+ status = "disabled";
+};
+
+/* Wi-Fi reset is connected to GPIO4. */
+&usdhc3 {
+ status = "disabled";
+};
+
+&usdhc3_pwrseq {
+ status = "disabled";
+};
--
2.47.3
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
2026-11-19 9:06 [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations Stefano Radaelli
@ 2026-11-19 9:18 ` Daniel Baluta
2026-11-19 9:28 ` Stefano Radaelli
0 siblings, 1 reply; 5+ messages in thread
From: Daniel Baluta @ 2026-11-19 9:18 UTC (permalink / raw)
To: Stefano Radaelli, Frank Li, linux-kernel, devicetree, imx,
linux-arm-kernel
Cc: pierluigi.p, Stefano Radaelli, Sascha Hauer,
Pengutronix Kernel Team, Fabio Estevam, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
On 11/19/26 11:06, Stefano Radaelli wrote:
> From: Stefano Radaelli <stefano.r@variscite.com>
>
> Add Cortex-M33 overlays and combined DTBs for DART-MX93 on Sonata and
> VAR-SOM-MX93 on Symphony.
>
> Share the remoteproc and mailbox configuration through a common include.
> Reuse the reserved memory from each carrier DTS, preserving the different
> resource table addresses.
>
> Move the existing DART-MX93 remoteproc and MU1 configuration out of the
> module DTSI so that they are enabled only by the M33 overlay. Use the
> -m33 DTB when remoteproc support is needed.
>
> Reserve the peripherals used by the M33 firmware and disable Wi-Fi,
> Bluetooth and the devices depending on GPIO4. On Sonata, also disable USB
> OTG1 because its USB-C role controller is unavailable.
>
> Signed-off-by: Stefano Radaelli <stefano.r@variscite.com>
> ---
> Changes in v2:
> - Remove the cm33 and mu1 overrides from imx93-var-dart.dtsi,
> enabling them only through the M33 overlay.
>
> This patch uses the memory-region-names binding and driver support from
> the following commits, both 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")
>
> For dtbs_check on older trees, commit cebd1c0961d8 ("dt-bindings: gpio:
> vf610: fix clock requirements per SoC"), also in linux-next, fixes the
> pre-existing GPIO clock validation errors.
>
> arch/arm64/boot/dts/freescale/Makefile | 9 +++
> .../dts/freescale/imx93-var-common-m33.dtsi | 24 ++++++++
> .../freescale/imx93-var-dart-sonata-m33.dtso | 55 +++++++++++++++++++
> .../dts/freescale/imx93-var-dart-sonata.dts | 2 +-
> .../boot/dts/freescale/imx93-var-dart.dtsi | 14 -----
> .../freescale/imx93-var-som-symphony-m33.dtso | 50 +++++++++++++++++
> 6 files changed, 139 insertions(+), 15 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
>
> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
> index cfd548284358..05a7556e9de9 100644
> --- a/arch/arm64/boot/dts/freescale/Makefile
> +++ b/arch/arm64/boot/dts/freescale/Makefile
> @@ -956,8 +956,17 @@ dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxca-lvds-tm070jvhg33.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxla-lvds-tm070jvhg33.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxla-mini-ezurio-wlan.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx93-tqma9352-mba93xxla-mini-lvds-tm070jvhg33.dtb
> +
> +imx93-var-dart-sonata-m33-dtbs := imx93-var-dart-sonata.dtb imx93-var-dart-sonata-m33.dtbo
> dtb-$(CONFIG_ARCH_MXC) += imx93-var-dart-sonata.dtb
> +dtb-$(CONFIG_ARCH_MXC) += imx93-var-dart-sonata-m33.dtb
> +dtb-$(CONFIG_ARCH_MXC) += imx93-var-dart-sonata-m33.dtbo
> +
> +imx93-var-som-symphony-m33-dtbs := imx93-var-som-symphony.dtb imx93-var-som-symphony-m33.dtbo
> dtb-$(CONFIG_ARCH_MXC) += imx93-var-som-symphony.dtb
> +dtb-$(CONFIG_ARCH_MXC) += imx93-var-som-symphony-m33.dtb
> +dtb-$(CONFIG_ARCH_MXC) += imx93-var-som-symphony-m33.dtbo
> +
> dtb-$(CONFIG_ARCH_MXC) += imx93w-evk.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx93w-frdm.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx943-evk.dtb
> diff --git a/arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi b/arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi
> new file mode 100644
> index 000000000000..51b4cfe143d4
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx93-var-common-m33.dtsi
> @@ -0,0 +1,24 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Common Cortex-M33 configuration for Variscite i.MX93 modules
> + *
> + * Copyright (C) 2026 Variscite Ltd. - https://www.variscite.com/
> + *
> + */
> +
> +/* Use the reserved memory and resource table address from the carrier DTS. */
> +&cm33 {
> + mbox-names = "tx", "rx", "rxdb";
> + mboxes = <&mu1 0 1
> + &mu1 1 1
> + &mu1 3 1>;
> + memory-region = <&vdevbuffer>, <&vdev0vring0>, <&vdev0vring1>,
> + <&vdev1vring0>, <&vdev1vring1>, <&rsc_table>;
> + memory-region-names = "vdev0buffer", "vdev0vring0", "vdev0vring1",
> + "vdev1vring0", "vdev1vring1", "rsc-table";
> + status = "okay";
> +};
> +
> +&mu1 {
> + status = "okay";
> +};
> diff --git a/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso
> new file mode 100644
> index 000000000000..d97da9916ef4
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata-m33.dtso
> @@ -0,0 +1,55 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Cortex-M33 support for Variscite DART-MX93 on Sonata-Board
> + *
> + * Link: https://variscite.com/carrier-boards/sonata-board/
> + *
> + * Copyright (C) 2026 Variscite Ltd. - https://www.variscite.com/
> + *
> + */
> +
> +/dts-v1/;
> +/plugin/;
> +
> +#include "imx93-var-common-m33.dtsi"
> +
> +/* Reserve the peripherals used by the Cortex-M33 firmware. */
Use "reserved" instead of "disabled" for all the nodes that need not to probe
on the Application processor because they are used by the M33 FW.
Also, instead of disable in the commit message I think it is better to say "reserve".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
2026-11-19 9:18 ` Daniel Baluta
@ 2026-11-19 9:28 ` Stefano Radaelli
2026-11-19 9:42 ` Daniel Baluta
0 siblings, 1 reply; 5+ messages in thread
From: Stefano Radaelli @ 2026-11-19 9:28 UTC (permalink / raw)
To: Daniel Baluta
Cc: Frank Li, linux-kernel, devicetree, imx, linux-arm-kernel,
pierluigi.p, Stefano Radaelli, Sascha Hauer,
Pengutronix Kernel Team, Fabio Estevam, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
On Thu, Nov 19, 2026 at 11:18:45AM +0200, Daniel Baluta wrote:
>
> Use "reserved" instead of "disabled" for all the nodes that need not to probe
> on the Application processor because they are used by the M33 FW.
>
> Also, instead of disable in the commit message I think it is better to say "reserve".
>
Hi Daniel,
That makes sense, thank you for your review!
I'll use "reserved" for the peripherals used directly by the Cortex-M
firmware, and keep "disabled" for devices that become unavailable as a
consequence.
For example, Wi-Fi cannot use its reset GPIO because GPIO4 is reserved
for the M33.
Does that match what you had in mind?
Best regards,
Stefano
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
2026-11-19 9:28 ` Stefano Radaelli
@ 2026-11-19 9:42 ` Daniel Baluta
2026-11-19 9:58 ` Stefano Radaelli
0 siblings, 1 reply; 5+ messages in thread
From: Daniel Baluta @ 2026-11-19 9:42 UTC (permalink / raw)
To: Stefano Radaelli
Cc: Frank Li, linux-kernel, devicetree, imx, linux-arm-kernel,
pierluigi.p, Stefano Radaelli, Sascha Hauer,
Pengutronix Kernel Team, Fabio Estevam, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
On 11/19/26 11:28, Stefano Radaelli wrote:
> On Thu, Nov 19, 2026 at 11:18:45AM +0200, Daniel Baluta wrote:
>>
>> Use "reserved" instead of "disabled" for all the nodes that need not to probe
>> on the Application processor because they are used by the M33 FW.
>>
>> Also, instead of disable in the commit message I think it is better to say "reserve".
>>
>
> Hi Daniel,
>
> That makes sense, thank you for your review!
>
> I'll use "reserved" for the peripherals used directly by the Cortex-M
> firmware, and keep "disabled" for devices that become unavailable as a
> consequence.
> For example, Wi-Fi cannot use its reset GPIO because GPIO4 is reserved
> for the M33.
>
> Does that match what you had in mind?
Yes, that make sense. I wonder if it is a good idea to split this patch
into multiple patches each one representing a logical change.
The commit message suggests a lot of activities going on with the code which
makes it harder to understand. Either approach is fine tough, as the changes are not that big.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations
2026-11-19 9:42 ` Daniel Baluta
@ 2026-11-19 9:58 ` Stefano Radaelli
0 siblings, 0 replies; 5+ messages in thread
From: Stefano Radaelli @ 2026-11-19 9:58 UTC (permalink / raw)
To: Daniel Baluta
Cc: Frank Li, linux-kernel, devicetree, imx, linux-arm-kernel,
pierluigi.p, Stefano Radaelli, Sascha Hauer,
Pengutronix Kernel Team, Fabio Estevam, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
On Thu, Nov 19, 2026 at 11:42:54AM +0200, Daniel Baluta wrote:
> On 11/19/26 11:28, Stefano Radaelli wrote:
> > On Thu, Nov 19, 2026 at 11:18:45AM +0200, Daniel Baluta wrote:
> >>
> >> Use "reserved" instead of "disabled" for all the nodes that need not to probe
> >> on the Application processor because they are used by the M33 FW.
> >>
> >> Also, instead of disable in the commit message I think it is better to say "reserve".
> >>
> >
> > Hi Daniel,
> >
> > That makes sense, thank you for your review!
> >
> > I'll use "reserved" for the peripherals used directly by the Cortex-M
> > firmware, and keep "disabled" for devices that become unavailable as a
> > consequence.
> > For example, Wi-Fi cannot use its reset GPIO because GPIO4 is reserved
> > for the M33.
> >
> > Does that match what you had in mind?
> Yes, that make sense. I wonder if it is a good idea to split this patch
> into multiple patches each one representing a logical change.
>
> The commit message suggests a lot of activities going on with the code which
> makes it harder to understand. Either approach is fine tough, as the changes are not that big.
Thanks for the suggestion. I'll split this into two patches for v3:
- Extract the existing M33 configuration into a common include,
preserving the current behavior.
- Add the M33 overlays and combined DTBs, using "reserved" for the
peripherals assigned to the M33.
Best regards,
Stefano
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-11-19 9:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-19 9:06 [PATCH v2 1/1] arm64: dts: freescale: imx93-var: Add Cortex-M33 configurations Stefano Radaelli
2026-11-19 9:18 ` Daniel Baluta
2026-11-19 9:28 ` Stefano Radaelli
2026-11-19 9:42 ` Daniel Baluta
2026-11-19 9:58 ` Stefano Radaelli
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox