From: Peng Fan <peng.fan@nxp.com>
To: Diogo Manuel Pais Silva <diogo.pais@ttcontrol.com>
Cc: "abelvesa@kernel.org" <abelvesa@kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"EMC: linux-kernel@vger.kernel.org"
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] clk: imx8qxp: Defer instead of failing probe
Date: Tue, 2 Jul 2024 10:14:14 +0000 [thread overview]
Message-ID: <DB7PR04MB594880A7CE8BA67F493044B188DC2@DB7PR04MB5948.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DU0PR01MB9382F1AC496F22A20C074BDE9DDC2@DU0PR01MB9382.eurprd01.prod.exchangelabs.com>
> Subject: [PATCH v2] clk: imx8qxp: Defer instead of failing probe
>
> When of_clk_parent_fill is ran without all the parent clocks having
> been probed then the probe function will return -EINVAL, making it so
> that the probe isn't attempted again. As fw_devlink is on by default
> this does not usually happen, but if fw_devlink is disabled then it is
> very possible that the parent clock will be probed after the lpcg first
> attempt.
>
> Signed-off-by: Diogo Silva <diogo.pais@ttcontrol.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2024-07-02 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 11:54 [PATCH] " Diogo Manuel Pais Silva
2024-07-01 23:55 ` Peng Fan
2024-07-02 8:10 ` [PATCH v2] " Diogo Manuel Pais Silva
2024-07-02 10:14 ` Peng Fan [this message]
2024-08-28 8:31 ` Abel Vesa
2024-09-02 14:18 ` [PATCH v3] " Diogo Manuel Pais Silva
2024-09-04 2:03 ` Peng Fan
2024-09-04 6:47 ` Diogo Manuel Pais Silva
2024-09-04 6:50 ` [PATCH v4] " Diogo Manuel Pais Silva
2024-09-05 18:35 ` Stephen Boyd
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=DB7PR04MB594880A7CE8BA67F493044B188DC2@DB7PR04MB5948.eurprd04.prod.outlook.com \
--to=peng.fan@nxp.com \
--cc=abelvesa@kernel.org \
--cc=diogo.pais@ttcontrol.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--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®