[PATCH] ARM: dts: i.MX8MP FRDM: remove memory node

[PATCH] ARM: dts: i.MX8MP FRDM: remove memory node

[Bastian Krause]

Since f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles") the esdctl
driver is used. This causes the errors below since barebox tries to add
the memory twice:

  imx-esdctl 3d400000.memory-controller@3d400000.of: probe failed: Device or resource busy
  initcall imx_esdctl_driver_init+0x0/0x2c failed: No such device

Remove the memory node to fix this.

604c974c968 ("ARM: dts: i.MX8MP: remove memory node") already fixed this
for the i.MX8MP EVK and the TQMa8MPxL on the MBa8MPxL.

Fixes: f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles")
Signed-off-by: Bastian Krause <bst@pengutronix.de>
---
 arch/arm/dts/imx8mp-frdm.dts | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/dts/imx8mp-frdm.dts b/arch/arm/dts/imx8mp-frdm.dts
index b1870213baf..7d770c3e456 100644
--- a/arch/arm/dts/imx8mp-frdm.dts
+++ b/arch/arm/dts/imx8mp-frdm.dts
@@ -11,3 +11,5 @@
 / {
 	barebox,deep-probe;
 };
+
+/delete-node/ &{/memory@40000000};
-- 
2.47.3

Re: [PATCH] ARM: dts: i.MX8MP FRDM: remove memory node

[Marco Felsch]

On 26-06-12, Bastian Krause wrote:
> Since f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles") the esdctl
> driver is used. This causes the errors below since barebox tries to add
> the memory twice:
> 
>   imx-esdctl 3d400000.memory-controller@3d400000.of: probe failed: Device or resource busy
>   initcall imx_esdctl_driver_init+0x0/0x2c failed: No such device
> 
> Remove the memory node to fix this.
> 
> 604c974c968 ("ARM: dts: i.MX8MP: remove memory node") already fixed this
> for the i.MX8MP EVK and the TQMa8MPxL on the MBa8MPxL.
> 
> Fixes: f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles")
> Signed-off-by: Bastian Krause <bst@pengutronix.de>

Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>

Re: [PATCH] ARM: dts: i.MX8MP FRDM: remove memory node

[Ahmad Fatoum]

Hello,

On 6/12/26 13:58, Bastian Krause wrote:
> Since f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles") the esdctl
> driver is used. This causes the errors below since barebox tries to add
> the memory twice:
> 
>   imx-esdctl 3d400000.memory-controller@3d400000.of: probe failed: Device or resource busy
>   initcall imx_esdctl_driver_init+0x0/0x2c failed: No such device

Can you share the full output? -EBUSY here is not expected for
the issues you describe. barebox has been tolerant of the same
memory bank being registered by different means for a number
of years now.

> Remove the memory node to fix this.
> 
> 604c974c968 ("ARM: dts: i.MX8MP: remove memory node") already fixed this
> for the i.MX8MP EVK and the TQMa8MPxL on the MBa8MPxL.

This commit doesn't exist upstream.

> 
> Fixes: f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles")

This commit is 3 years old and the FRDM was only added this year.
Was the error message there all the time..?

Thanks,
Ahmad


> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> ---
>  arch/arm/dts/imx8mp-frdm.dts | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/dts/imx8mp-frdm.dts b/arch/arm/dts/imx8mp-frdm.dts
> index b1870213baf..7d770c3e456 100644
> --- a/arch/arm/dts/imx8mp-frdm.dts
> +++ b/arch/arm/dts/imx8mp-frdm.dts
> @@ -11,3 +11,5 @@
>  / {
>  	barebox,deep-probe;
>  };
> +
> +/delete-node/ &{/memory@40000000};


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Re: [PATCH] ARM: dts: i.MX8MP FRDM: remove memory node

[Sascha Hauer]

On 2026-06-12 16:15, Ahmad Fatoum wrote:
> Hello,
> 
> On 6/12/26 13:58, Bastian Krause wrote:
> > Since f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles") the esdctl
> > driver is used. This causes the errors below since barebox tries to add
> > the memory twice:
> > 
> >   imx-esdctl 3d400000.memory-controller@3d400000.of: probe failed: Device or resource busy
> >   initcall imx_esdctl_driver_init+0x0/0x2c failed: No such device
> 
> Can you share the full output? -EBUSY here is not expected for
> the issues you describe. barebox has been tolerant of the same
> memory bank being registered by different means for a number
> of years now.

They are likely not recognized as the same memory bank. The frdm board
has:

        memory@40000000 {
                device_type = "memory";
                reg = <0x0 0x40000000 0 0xc0000000>,
                      <0x1 0x00000000 0 0x40000000>;
        };

Whereas the esdctl driver will register only a single region.

Sascha

--
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |