From: Shawn Guo <shawnguo@kernel.org>
To: Dong Aisheng <aisheng.dong@nxp.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-imx@nxp.com,
Sascha Hauer <kernel@pengutronix.de>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] clk: imx: scu: remove the calling of device_is_bound
Date: Mon, 30 Nov 2020 21:54:19 +0800 [thread overview]
Message-ID: <20201130135419.GI4072@dragon> (raw)
In-Reply-To: <20201119114302.26263-1-aisheng.dong@nxp.com>
On Thu, Nov 19, 2020 at 07:43:02PM +0800, Dong Aisheng wrote:
> The device_is_bound() is unvisable to drivers when built as modules.
s/unvisable/invisible?
I fixed it up and applied the patch.
Shawn
> It's also not aimed to be used by drivers according to Greg K.H.
> Let's remove it from clk-scu driver and find another way to do proper
> driver loading sequence.
>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Fixes: 77d8f3068c63 ("clk: imx: scu: add two cells binding support")
> Reported-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> ---
> drivers/clk/imx/clk-scu.c | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/clk/imx/clk-scu.c b/drivers/clk/imx/clk-scu.c
> index d10f60e48ece..1f5518b7ab39 100644
> --- a/drivers/clk/imx/clk-scu.c
> +++ b/drivers/clk/imx/clk-scu.c
> @@ -153,7 +153,6 @@ static inline struct clk_scu *to_clk_scu(struct clk_hw *hw)
>
> int imx_clk_scu_init(struct device_node *np)
> {
> - struct platform_device *pd_dev;
> u32 clk_cells;
> int ret, i;
>
> @@ -166,17 +165,11 @@ int imx_clk_scu_init(struct device_node *np)
> if (clk_cells == 2) {
> for (i = 0; i < IMX_SC_R_LAST; i++)
> INIT_LIST_HEAD(&imx_scu_clks[i]);
> - /*
> - * Note: SCU clock driver depends on SCU power domain to be ready
> - * first. As there're no power domains under scu clock node in dts,
> - * we can't use PROBE_DEFER automatically.
> - */
> +
> + /* pd_np will be used to attach power domains later */
> pd_np = of_find_compatible_node(NULL, NULL, "fsl,scu-pd");
> - pd_dev = of_find_device_by_node(pd_np);
> - if (!pd_dev || !device_is_bound(&pd_dev->dev)) {
> - of_node_put(pd_np);
> - return -EPROBE_DEFER;
> - }
> + if (!pd_np)
> + return -EINVAL;
> }
>
> return platform_driver_register(&imx_clk_scu_driver);
> --
> 2.23.0
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-30 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 11:43 [PATCH 1/1] clk: imx: scu: remove the calling of device_is_bound Dong Aisheng
2020-11-19 13:08 ` Sudip Mukherjee
2020-11-19 15:30 ` Aisheng Dong
2020-11-19 17:44 ` Sudip Mukherjee
2020-11-24 10:28 ` Aisheng Dong
2020-11-24 10:33 ` Aisheng Dong
2020-11-30 13:54 ` Shawn Guo [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=20201130135419.GI4072@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=sboyd@kernel.org \
--cc=sudipm.mukherjee@gmail.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;
as well as URLs for NNTP newsgroup(s).