[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <486054ad-20c2-45f4-a457-c9334afb53ed@app.fastmail.com>
Date: Wed, 25 Sep 2024 16:04:54 +0000
From: "Arnd Bergmann" <arnd@...db.de>
To: "Marek Vasut" <marex@...x.de>, linux-arm-kernel@...ts.infradead.org
Cc: kernel@...electronics.com,
"AngeloGioacchino Del Regno" <angelogioacchino.delregno@...labora.com>,
"Fabio Estevam" <festevam@...il.com>,
"Jeff Johnson" <quic_jjohnson@...cinc.com>,
"Neil Armstrong" <neil.armstrong@...aro.org>,
"Pengutronix Kernel Team" <kernel@...gutronix.de>,
"Saravana Kannan" <saravanak@...gle.com>,
"Sascha Hauer" <s.hauer@...gutronix.de>, "Shawn Guo" <shawnguo@...nel.org>,
imx@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] soc: imx8m: Probe the SoC driver late
On Wed, Sep 25, 2024, at 16:00, Marek Vasut wrote:
> With driver_async_probe=* on kernel command line, the following trace is
> produced because on i.MX8M Plus hardware because the soc-imx8m.c driver
> calls of_clk_get_by_name() which returns -EPROBE_DEFER because the clock
> driver is not yet probed. This was not detected during regular testing
> without driver_async_probe.
>
> Attempt to fix it by probing the SoC driver late, but I don't think that
> is the correct approach here.
I think the correct fix would be to propagate the -EPROBE_DEFER
and return that from imx8_soc_init(), so it gets retried again
after the clock driver.
Arnd
Powered by blists - more mailing lists