From: Stephen Boyd <sboyd@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>,
Diogo Manuel Pais Silva <diogo.pais@ttcontrol.com>,
Peng Fan <peng.fan@nxp.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>,
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 v4] clk: imx8qxp: Defer instead of failing probe
Date: Thu, 05 Sep 2024 11:35:54 -0700 [thread overview]
Message-ID: <0e1436511cadbe5eb6e0b567d61f0cea.sboyd@kernel.org> (raw)
In-Reply-To: <DU0PR01MB9382A24116486931F28843BA9D9C2@DU0PR01MB9382.eurprd01.prod.exchangelabs.com>
Quoting Diogo Manuel Pais Silva (2024-09-03 23:50:02)
> 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>
> ---
Please stop sending as replies to previous patches.
> drivers/clk/imx/clk-imx8qxp-lpcg.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/imx/clk-imx8qxp-lpcg.c b/drivers/clk/imx/clk-imx8qxp-lpcg.c
> index d0ccaa040225..1c3e1a7df8ca 100644
> --- a/drivers/clk/imx/clk-imx8qxp-lpcg.c
> +++ b/drivers/clk/imx/clk-imx8qxp-lpcg.c
> @@ -225,8 +225,8 @@ static int imx_lpcg_parse_clks_from_dt(struct platform_device *pdev,
>
> ret = of_clk_parent_fill(np, parent_names, count);
It would be better to move to struct clk_parent_data here and use the
.index member if possible. That would allow the clks to be registered
without their parent(s) being registered. It lets the core take care of
finding the parents.
prev parent reply other threads:[~2024-09-05 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 11:54 [PATCH] clk: imx8qxp: Defer instead of failing probe 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
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 [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=0e1436511cadbe5eb6e0b567d61f0cea.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=abelvesa@kernel.org \
--cc=diogo.pais@ttcontrol.com \
--cc=peng.fan@nxp.com \
/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