mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Ahmad Fatoum" <a.fatoum@pengutronix.de>
Cc: "Bastian Krause" <bst@pengutronix.de>,
	barebox@lists.infradead.org, "Marco Felsch" <mfe@pengutronix.de>
Subject: Re: [PATCH] ARM: dts: i.MX8MP FRDM: remove memory node
Date: Mon, 15 Jun 2026 06:44:57 +0000	[thread overview]
Message-ID: <E1wZ145-00000006Dfc-0ux4@pty.whiteo.stw.pengutronix.de> (raw)
In-Reply-To: <c3ffa653-e2e8-4b11-a5b4-4a9e1c60e2e9@pengutronix.de>

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 |



      reply	other threads:[~2026-06-15  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 11:58 Bastian Krause
2026-06-12 12:43 ` Marco Felsch
2026-06-12 14:15 ` Ahmad Fatoum
2026-06-15  6:44   ` Sascha Hauer [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=E1wZ145-00000006Dfc-0ux4@pty.whiteo.stw.pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=bst@pengutronix.de \
    --cc=mfe@pengutronix.de \
    /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