dt-bindings: arm: fsl: Document Data Modul i.MX95 eDM SBC
Subsystems (3)
PATCH v7 1/2 dt-bindings: arm: fsl: Document Data Modul i.MX95 eDM SBC
Document Data Modul i.MX95 eDM SBC board. This is an evaluation board for various custom display units. Currently supported are serial console, ethernet, eMMC, SD, SPI NOR, USB host and PCIe.
---
Cc: Aswath Govindraju <[email protected]>
Cc: Conor Dooley <[email protected]>
Cc: Fabio Estevam <[email protected]>
Cc: Frank Li <[email protected]>
Cc: Krzysztof Kozlowski <[email protected]>
Cc: Marc Kleine-Budde <[email protected]>
Cc: Rob Herring <[email protected]>
Cc: Vinod Koul <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
---
V2: No change
V3: No change
V4: No change
V5: Add AB from Krzysztof
V6: No change
V7: No change
--- Documentation/devicetree/bindings/arm/fsl.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/arm/fsl.yaml +1 -0
@@ -1579,6 +1579,7 @@ properties: - description: i.MX95 based Boards items: - enum: + - dmo,imx95-data-modul-edm-sbc # i.MX95 eDM SBC - fsl,imx95-15x15-ab2 # i.MX95 15x15 Audio Board V2 - fsl,imx95-15x15-evk # i.MX95 15x15 EVK Board - fsl,imx95-15x15-frdm # i.MX95 15x15 FRDM Board
Signature · 1 line
2.53.0
PATCH v7 2/2 arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
Add support for Data Modul i.MX95 eDM SBC board. This is an evaluation board for various custom display units. Currently supported are serial console, ethernet, eMMC, SD, SPI NOR, USB host and PCIe.
---
Cc: Aswath Govindraju <[email protected]>
Cc: Conor Dooley <[email protected]>
Cc: Fabio Estevam <[email protected]>
Cc: Frank Li <[email protected]>
Cc: Krzysztof Kozlowski <[email protected]>
Cc: Marc Kleine-Budde <[email protected]>
Cc: Rob Herring <[email protected]>
Cc: Vinod Koul <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
---
V2: - Rename PCIE_M2-E_EN to PCIE_M2-M_EN
- Fix the PCAL expander GPIO reset
V3: - Fix regulator-5p0v node name
- Use reset-gpios consistently
V4: - Replace gpio with gpios DT property
V5: - Rebase on next-20260928
V6: - Remove backlight supply nodes
V7: - Rebase on next-20261113 which contains trivial Makefile change
that made V6 no longer apply
--- arch/arm64/boot/dts/freescale/Makefile | 1 + .../freescale/imx95-data-modul-edm-sbc.dts | 1079 +++++++++++++++++ 2 files changed, 1080 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts
arch/arm64/boot/dts/freescale/Makefile +1 -0
@@ -980,6 +980,7 @@ dtb-$(CONFIG_ARCH_MXC) += imx95-19x19-frdm-pro.dtb dtb-$(CONFIG_ARCH_MXC) += imx95-aquila-clover.dtb dtb-$(CONFIG_ARCH_MXC) += imx95-aquila-dev-uart4-mcu.dtb dtb-$(CONFIG_ARCH_MXC) += imx95-aquila-dev.dtb +dtb-$(CONFIG_ARCH_MXC) += imx95-data-modul-edm-sbc.dtb dtb-$(CONFIG_ARCH_MXC) += imx95-navq.dtb dtb-$(CONFIG_ARCH_MXC) += imx95-toradex-osm-dev.dtb dtb-$(CONFIG_ARCH_MXC) += imx95-toradex-smarc-dev-ser0-mcu.dtb
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +1079 -0
1,079 lines not on this page · raw message
Signature · 1 line
2.53.0
[email protected]
AI reviewRe: [PATCH v7 2/2] arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
Thank you for your contribution! Sashiko AI review found 2 potential issues to consider: - [Medium] arm64: dts: imx95: missing pinmux for Ethernet PHY IRQ on GPIO1_IO10 - [Low] arm64: dts: imx95…
Thank you for your contribution! Sashiko AI review found 2 potential issues to consider:
- [Medium] arm64: dts: imx95: missing pinmux for Ethernet PHY IRQ on GPIO1_IO10
- [Low] arm64: dts: imx95: unused backlight pinctrl node and header includes
--
commit 08308b97a054b075daa4e1d5655d37470b104a88
Author: Marek Vasut <[email protected]>
arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
This commit adds a device tree for the Data Modul i.MX95 eDM SBC board.
Quoted 18 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +12
-0@@ -0,0 +1,1079 @@ +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) +/* + * Copyright (C) 2025-2026 Marek Vasut <[email protected]> + */ + +/dts-v1/; + +#include <dt-bindings/i3c/i3c.h> +#include <dt-bindings/leds/common.h> +#include <dt-bindings/pwm/pwm.h> +#include <dt-bindings/usb/pd.h> +#include "imx95.dtsi"
[ ... ]
Quoted 25 lines
+&netc_emdio {
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +24
-0+ pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_emdio>; + status = "okay"; + + ethphy0: ethernet-phy@1 { /* KSZ9131RNXI U20 */ + compatible = "ethernet-phy-id0022.1640"; + reg = <1>; + interrupts-extended = <&gpio1 10 IRQ_TYPE_LEVEL_LOW>; + reset-assert-us = <1000>; + /* RESET_N signal rise time ~100ms */ + reset-deassert-us = <120000>; + reset-gpios = <&i2c2_gpio_expander_22 4 GPIO_ACTIVE_HIGH>; + }; + + ethphy1: ethernet-phy@2 { /* KSZ9131RNXI U22 */ + compatible = "ethernet-phy-id0022.1640"; + reg = <2>; + interrupts-extended = <&gpio1 10 IRQ_TYPE_LEVEL_LOW>; + reset-assert-us = <1000>; + /* RESET_N signal rise time ~100ms */ + reset-deassert-us = <120000>; + reset-gpios = <&i2c2_gpio_expander_22 5 GPIO_ACTIVE_HIGH>; + }; +};
[ ... ]
Quoted 15 lines
+&scmi_iomuxc {
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +14
-0+ pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_hog>; + + pinctrl_hog: hoggrp { + fsl,pins = < + /* PCIe 0 PEWAKE */ + IMX95_PAD_GPIO_IO34__GPIO5_IO_BIT14 0x4000031e + /* PCIe 1 PEWAKE */ + IMX95_PAD_GPIO_IO37__GPIO5_IO_BIT17 0x4000031e + /* BOOT_MODE2 */ + IMX95_PAD_SAI1_TXFS__AONMIX_TOP_GPIO1_IO_BIT11 0x4000031e + /* IO_XPNDR_RST_1V8 shared by multiple expanders */ + IMX95_PAD_XSPI1_SS0_B__GPIO5_IO_BIT10 0x40000b9e + /* IO_XPNDR_INT_1V8 shared by multiple expanders */
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 753
Quoted 10 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +10
-0+ IMX95_PAD_XSPI1_SS1_B__GPIO5_IO_BIT11 0x40000b9e + >; + }; + + pinctrl_emdio: emdiogrp { + fsl,pins = < + IMX95_PAD_ENET2_MDC__NETCMIX_TOP_NETC_MDC 0x50e + IMX95_PAD_ENET2_MDIO__NETCMIX_TOP_NETC_MDIO 0x90e + >; + };
[Severity: Medium]
Should pinctrl_hog or pinctrl_emdio mux IMX95_PAD_PDM_BIT_STREAM1__AONMIX_TOP_GPIO1_IO_BIT10 for the shared PHY interrupt line on <&gpio1 10>?
Both ethphy0 and ethphy1 use <&gpio1 10> as their interrupt, and pinctrl-imx-scmi does not implement .gpio_request_enable, so requesting the line as an interrupt will not switch the pad from its default PDM_BIT_STREAM_BIT1 mux mode. Unless firmware pre-configures this pad as a GPIO, PHY interrupts will not reach gpio1.
[ ... ]
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 867
Quoted 5 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +5
-0+ pinctrl_panel_backlight_lvds: backlightlvdsgrp { + fsl,pins = < + IMX95_PAD_GPIO_IO27__GPIO2_IO_BIT27 0x31e + >; + };
[Severity: Low]
This isn't a bug, but pinctrl_panel_backlight_lvds is unreferenced now that the backlight nodes have been removed. Also, the dt-bindings/i3c/i3c.h, dt-bindings/pwm/pwm.h, and dt-bindings/usb/pd.h includes at the top of the file are unused.
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
[email protected]
AI reviewRe: [PATCH v7 2/2] arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
In reply to Marek VasutThank you for your contribution! Sashiko AI review found 7 potential issue(s) to consider.
Thank you for your contribution! Sashiko AI review found 7 potential issue(s) to consider.
Critical: 0 · High: 0 · Medium: 3 · Low: 4
If you believe none of the issues are legitimate, please reply to each issue of Medium severity or higher and explain why the AI is wrong. If any of them are legitimate and you plan to respin, please let patchwork know by including "pw-bot: cr" as a separate line at the end of your reply (one such reply per series is enough).
- [Medium] All three PCAL6524 expanders, U12 (gpio@20), U14 (gpio@21) and U13 (gpio@22), share the IO_XPNDR_INT_1V8 line on gpio5 11 and each…
- [Medium] Both KSZ9131 PHYs (ethphy0 at line 493, ethphy1 at line 503) take their interrupt from <&gpio1 10 IRQ_TYPE_LEVEL_LOW>.
- [Medium] The &usdhc3 (M.2 Key-E SDIO) node is enabled, but the slot's power enable VDD_3V3_M2-E_EN (U12 pin 5) and its reset M2-E_SDIO_RESET…
- [Low] The new board puts PERST# and slot power on the host-bridge nodes (`&pcie0 { reset-gpios = <&gpio5 13 ...>; vpcie-supply = <®_pcie0>;…
- [Low] The comment on &lpuart8 says "M7 Debug", but the node is status = "okay" with uart-has-rtscts and RTS/CTS pins muxed, so Linux owns…
- [Low] The V6 changelog says "Remove backlight supply nodes", but the pinctrl_panel_backlight_lvds: backlightlvdsgrp group…
- [Low] The commit message says "Currently supported are serial console, ethernet, eMMC, SD, SPI NOR, USB host and PCIe".
--
arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
This commit adds a device tree for the Data Modul i.MX95 eDM SBC, an evaluation board for custom display units. It also adds the new dtb to the freescale Makefile.
Quoted 4 lines
Add support for Data Modul i.MX95 eDM SBC board. This is an evaluation board for various custom display units. Currently supported are serial console, ethernet, eMMC, SD, SPI NOR, USB host and PCIe.
[Severity: Low]
This isn't a bug, but the list above covers less than the DTS enables.
Beyond the listed items, the DTS also enables:
- FlexCAN3/FlexCAN5 with ATA6563 PHYs
- three sound cards (BT-SCO on SAI5, MICFIL, TAS2552 on SAI3)
- SAI4
- an EMC2301 fan controller and a TMP110 sensor
- PMIC thermal zones, including a 140C passive trip on pf53arm that throttles all six A55 cores
- GPIO LEDs, I3C2 and TPM3/TPM4
- wdog3 with fsl,ext-reset-output
Could the commit message mention these too?
Quoted 6 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +0
-0@@ -0,0 +1,1079 @@
[ ... ]
Quoted 4 lines
+&lpi2c2 {
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +3
-0+ clock-frequency = <400000>; + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_lpi2c2>;
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 279
Quoted 10 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +10
-0+ status = "okay"; + + i2c2_gpio_expander_20: gpio@20 { /* U12 */ + compatible = "nxp,pcal6524"; + reg = <0x20>; + #gpio-cells = <2>; + gpio-controller; + #interrupt-cells = <2>; + interrupt-controller; + interrupts-extended = <&gpio5 11 IRQ_TYPE_LEVEL_HIGH>;
[Severity: Medium]
Is IRQ_TYPE_LEVEL_HIGH the right polarity for the shared IO_XPNDR_INT_1V8 line?
All three PCAL6524 expanders (U12 gpio@20, U14 gpio@21 and U13 gpio@22) share gpio5 11, and all three use IRQ_TYPE_LEVEL_HIGH. The other in-tree PCAL6524 users (imx91-11x11-evk, imx91-11x11-frdm, imx91-9x9-qsb and imx93-11x11-evk-common) use active-low, for example:
arch/arm64/boot/dts/freescale/imx93-11x11-evk-common.dtsi:
interrupts = <27 IRQ_TYPE_LEVEL_LOW>;
In pinctrl_hog, the pad for this line has the same setting as the open-drain, pulled-up LPI2C pads, so the line idles high:
IMX95_PAD_XSPI1_SS1_B__GPIO5_IO_BIT11 0x40000b9e
pca953x_irq_setup() in drivers/gpio/gpio-pca953x.c requests the parent IRQ at probe without overriding the trigger:
ret = devm_request_threaded_irq(dev, client->irq, NULL, pca953x_irq_handler, IRQF_ONESHOT | IRQF_SHARED, dev_name(dev), chip);
So gpio5 is programmed with the LEVEL_HIGH type from DT.
With the line idling high, would this IRQ fire nonstop, with each handler returning IRQ_NONE, until the spurious IRQ detector disables gpio5 11? After that, no expander interrupt (V_12V0_PG, USB2_PWR_OC#, TOUCH_INT, WDOG_IRQ#, TPM_IRQ, FAN_ALERT, ...) would be delivered.
This happens on every boot with CONFIG_GPIO_PCA953X_IRQ, even with no consumers, because interrupt-controller and interrupts-extended are present.
LEVEL_HIGH is only correct if the 3.3V to 1.8V translation on this line inverts the signal. Does the board have an inverting stage there? If so, could a comment say so?
Quoted 1 line
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +1
-0+ vcc-supply = <®_3p3v>;
[ ... ]
Quoted 5 lines
+&lpuart2 { /* M33 Debug */
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +4
-0+ pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_uart2>; + status = "reserved"; +};
[ ... ]
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 438
Quoted 6 lines
+&lpuart8 { /* M7 Debug */
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +5
-0+ pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_uart8>; + uart-has-rtscts; + status = "okay"; +};
[Severity: Low]
The comment says this is the M7 debug port, but Linux owns the node:
it is enabled with uart-has-rtscts and the RTS/CTS pins are muxed. The M33 debug port (&lpuart2 above) uses status = "reserved".
Expander U12 also names "UART8_RS232-485_MODE0/1", "UART8_RS232-485_Term_TX/RX" and "UART8_RS232-485_EN". That looks like a user RS232/RS485 port.
Is the comment stale? Or should this node be status = "reserved", so that Linux and the M7 firmware don't both drive LPUART8?
[ ... ]
Quoted 9 lines
+&netc_emdio {
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +8
-0+ pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_emdio>; + status = "okay"; + + ethphy0: ethernet-phy@1 { /* KSZ9131RNXI U20 */ + compatible = "ethernet-phy-id0022.1640"; + reg = <1>; + interrupts-extended = <&gpio1 10 IRQ_TYPE_LEVEL_LOW>;
[ ... ]
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 503
Quoted 4 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +4
-0+ ethphy1: ethernet-phy@2 { /* KSZ9131RNXI U22 */ + compatible = "ethernet-phy-id0022.1640"; + reg = <2>; + interrupts-extended = <&gpio1 10 IRQ_TYPE_LEVEL_LOW>;
[Severity: Medium]
Is the GPIO1_IO10 pad muxed to GPIO anywhere?
GPIO1_IO10 is ALT5 on the PDM_BIT_STREAM1 pad; ALT0 there is PDM_BIT_STREAM_BIT1. From imx95-pinfunc.h:
#define IMX95_PAD_PDM_BIT_STREAM1__AONMIX_TOP_GPIO1_IO_BIT10 0x01E8 0x03EC 0x0000 0x05 0x00
None of the fsl,pins entries in this file select that function:
- pinctrl_hog muxes the neighbouring GPIO1_IO11 (BOOT_MODE2) but not
GPIO1_IO10.
- The ethphy nodes have no pinctrl of their own.
- pinctrl_pdm uses GPIO_IO05/06, not this pad.
Unless the System Manager or bootloader happens to set this pad to ALT5, does the KSZ9131 INT_N signal ever reach gpio1? An IRQ is declared, so phylib won't poll. Link up/down changes on both ENETC ports could then go unnoticed.
The pad also gets no pull-up, which a shared active-low IRQ line would need.
Every other GPIO this board uses (LEDs, SPI CS, SD CD, PCIe PERST#, expander INT/RST, PEWAKE) is muxed explicitly in this file.
[ ... ]
Quoted 5 lines
+&pcie0 { /* M.2 Key-B */
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +4
-0+ pinctrl-0 = <&pinctrl_pcie0>; + pinctrl-names = "default"; + reset-gpios = <&gpio5 13 GPIO_ACTIVE_LOW>; + vpcie-supply = <®_pcie0>;
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 533
Quoted 10 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +10
-0+ status = "okay"; +}; + +&pcie1 { /* M.2 Key-M */ + pinctrl-0 = <&pinctrl_pcie1>; + pinctrl-names = "default"; + reset-gpios = <&gpio5 16 GPIO_ACTIVE_LOW>; + vpcie-supply = <®_pcie1>; + status = "okay"; +};
[Severity: Low]
This isn't a bug, but should PERST# and the slot supply go on the root port nodes instead of the host bridge?
imx95.dtsi provides pcie0_port0 and pcie1_port0 (pcie@0, "pciclass,0604"). fsl,imx6q-pcie.yaml says:
This property is deprecated, instead of referencing this property from the host bridge node, use the reset-gpios property from the root port node.
In pci-imx6.c, imx_pcie_host_init() parses the host-level reset only as a fallback:
/* Fall back to legacy binding for DT backwards compatibility */
if (!imx_pcie_perst_found(bridge)) {
ret = imx_pcie_parse_legacy_binding(imx_pcie);The vpcie supply is also handled under "Legacy regulator handling for DT backward compatibility".
The other i.MX95 boards (imx95-15x15-evk, imx95-15x15-frdm, imx95-19x19-evk, imx95-19x19-frdm-pro) use this form instead:
&pcie0_port0 {
reset-gpios = <...>;
vpcie3v3-supply = <...>;
};[ ... ]
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 722
Quoted 9 lines
+&usdhc3 { /* M.2 Key-E */
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +8
-0+ pinctrl-names = "default", "state_100mhz", "state_200mhz", "sleep"; + pinctrl-0 = <&pinctrl_usdhc3>; + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; + pinctrl-3 = <&pinctrl_usdhc3>; + bus-width = <4>; + status = "okay"; +};
[Severity: Medium]
How does the M.2 Key-E slot get powered and released from reset?
The slot's power enable and SDIO reset are U12 pins, but they appear only in gpio-line-names:
"UART8_RS232-485_EN", "VDD_3V3_M2-E_EN", ... "M2-E_SDIO_RESET", "CAN3_STBY",
&usdhc3 has no vmmc-supply, mmc-pwrseq, non-removable or cd-gpios.
The Key-B and Key-M slots are different: their VDD_3V3_M2-x_EN pins are wrapped in reg_pcie0 and reg_pcie1. Nothing references VDD_3V3_M2-E_EN or M2-E_SDIO_RESET.
After the expander comes out of reset with all pins as inputs, Linux never drives these two pins. Does the Key-E 3.3V rail and SDIO reset then depend only on pull resistors or bootloader setup? It also seems the MMC core could not power-cycle or reset the module during suspend/resume or error recovery.
Boards such as imx91-11x11-evk and imx91-11x11-frdm describe this kind of slot with a reg_usdhc3_vmmc regulator on an expander GPIO, plus mmc-pwrseq-simple with reset-gpios. Would something similar work here?
[ ... ]
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts line 867
Quoted 5 lines
arch/arm64/boot/dts/freescale/imx95-data-modul-edm-sbc.dts new file +5
-0+ pinctrl_panel_backlight_lvds: backlightlvdsgrp { + fsl,pins = < + IMX95_PAD_GPIO_IO27__GPIO2_IO_BIT27 0x31e + >; + };
[Severity: Low]
This isn't a bug, but the v6 changelog says "Remove backlight supply nodes", and this group is still defined with nothing referencing it. Can it be dropped?
Similarly, &sai4 is enabled with pinctrl and assigned audio PLL clocks, but no sound card uses it. sound-bt-sco uses &sai5, sound-micfil uses &micfil and sound-tas2552 uses &sai3. Is &sai4 meant to be in this patch?
[ ... ]
Signature · 1 line
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261114001844.30606-1-marex%40nabladev.com
[email protected]
AppliedFrom: Frank Li <[email protected]>
Quoted 3 lines · Marek Vasut
Document Data Modul i.MX95 eDM SBC board. This is an evaluation board for various custom display units. Currently supported are serial console, ethernet, eMMC, SD, SPI NOR, USB host and PCIe.
Applied, thanks!
[1/2] dt-bindings: arm: fsl: Document Data Modul i.MX95 eDM SBC
commit: cf999fbdafefe98a1959f60e6dd5b047c1fe9714
[2/2] arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
(no commit info)
Fix typo Modul
Best regards,
--
Frank Li <[email protected]>