From: Lucas Stach <l.stach@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: i.MX8MP: remove memory node
Date: Mon, 13 Mar 2023 14:03:41 +0100 [thread overview]
Message-ID: <0fa19455f9f6473c263eced4e5d0f672e9fe135a.camel@pengutronix.de> (raw)
In-Reply-To: <20230312162928.2110697-1-m.felsch@pengutronix.de>
Am Sonntag, dem 12.03.2023 um 17:29 +0100 schrieb Marco Felsch:
> since commit f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles") we
> make use of the esdctl driver. This cause the below error since barebox
> try 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
>
I wonder why I didn't hit this. Probably some probe order thing.
> Remove the memory node to fix this.
>
> This behaviour was seen on a i.mx8mp-evk but the
> imx8mp-tqma8mpql-mba8mpxl also has a memory node and includes the
> barebox.dtsi.
>
> Fixes: f083fffe52 ("ARM: dts: i.MX8MP: add DDRC compatibles")
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> arch/arm/dts/imx8mp-evk.dts | 2 ++
> arch/arm/dts/imx8mp-tqma8mpql-mba8mpxl.dts | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/arch/arm/dts/imx8mp-evk.dts b/arch/arm/dts/imx8mp-evk.dts
> index 0acc3731d5..c7e1f35d2d 100644
> --- a/arch/arm/dts/imx8mp-evk.dts
> +++ b/arch/arm/dts/imx8mp-evk.dts
> @@ -30,6 +30,8 @@
> };
> };
>
> +/delete-node/ &{/memory@40000000};
> +
Why not add this to arch/arm/dts/imx8mp.dtsi?
Regards,
Lucas
> ðphy1 {
> reset-assert-us = <15000>;
> reset-deassert-us = <100000>;
> diff --git a/arch/arm/dts/imx8mp-tqma8mpql-mba8mpxl.dts b/arch/arm/dts/imx8mp-tqma8mpql-mba8mpxl.dts
> index 6e81f58e27..bf23e40489 100644
> --- a/arch/arm/dts/imx8mp-tqma8mpql-mba8mpxl.dts
> +++ b/arch/arm/dts/imx8mp-tqma8mpql-mba8mpxl.dts
> @@ -24,6 +24,8 @@
> };
> };
>
> +/delete-node/ &{/memory@40000000};
> +
> &usdhc2 {
> #address-cells = <1>;
> #size-cells = <1>;
next prev parent reply other threads:[~2023-03-13 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 16:29 Marco Felsch
2023-03-13 13:03 ` Lucas Stach [this message]
2023-03-13 13:46 ` Marco Felsch
2023-03-13 13:16 ` Ahmad Fatoum
2023-03-13 13:49 ` Marco Felsch
2023-03-13 13:58 ` Ahmad Fatoum
2023-03-13 14:02 ` Ahmad Fatoum
2023-03-13 16:08 ` Marco Felsch
2023-03-14 14:08 ` Sascha Hauer
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=0fa19455f9f6473c263eced4e5d0f672e9fe135a.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@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