mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Marek Vasut" <marex@denx.de>, linux-arm-kernel@lists.infradead.org
Cc: kernel@dh-electronics.com,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Jeff Johnson" <quic_jjohnson@quicinc.com>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Saravana Kannan" <saravanak@google.com>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Shawn Guo" <shawnguo@kernel.org>,
	imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: imx8m: Probe the SoC driver late
Date: Wed, 25 Sep 2024 16:04:54 +0000	[thread overview]
Message-ID: <486054ad-20c2-45f4-a457-c9334afb53ed@app.fastmail.com> (raw)
In-Reply-To: <20240925160026.84091-1-marex@denx.de>

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

  reply	other threads:[~2024-09-25 16:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 16:00 Marek Vasut
2024-09-25 16:04 ` Arnd Bergmann [this message]
2024-09-25 16:09   ` Marek Vasut
2024-09-25 16:31     ` Arnd Bergmann
2024-09-25 17:07       ` Marek Vasut
2024-09-25 18:48         ` Saravana Kannan
2024-09-25 20:00           ` Arnd Bergmann
2024-09-25 20:04             ` Saravana Kannan
2024-09-25 22:11           ` Marek Vasut

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=486054ad-20c2-45f4-a457-c9334afb53ed@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@dh-electronics.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_jjohnson@quicinc.com \
    --cc=s.hauer@pengutronix.de \
    --cc=saravanak@google.com \
    --cc=shawnguo@kernel.org \
    /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

all inboxes | Powered by JetHome®