From: "Danilo Krummrich" <dakr@kernel.org>
To: "Daniel Baluta" <daniel.baluta@oss.nxp.com>
Cc: "Alexander Stein" <alexander.stein@ew.tq-group.com>,
<abelvesa@kernel.org>, <peng.fan@nxp.com>,
<mturquette@baylibre.com>, <sboyd@kernel.org>, <Frank.Li@nxp.com>,
<s.hauer@pengutronix.de>, <kernel@pengutronix.de>,
<festevam@gmail.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <hanguidong02@gmail.com>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-clk@vger.kernel.org>, <imx@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: scu/imx8qxp: do not register driver in probe()
Date: Thu, 12 Feb 2026 18:22:37 +0100 [thread overview]
Message-ID: <DGD5O31G6G9X.R8G6EBXXFKAH@kernel.org> (raw)
In-Reply-To: <9e33e5e5-76cd-4395-acb4-e2e03e436bf5@oss.nxp.com>
On Wed Feb 11, 2026 at 3:59 PM CET, Daniel Baluta wrote:
> On 2/11/26 16:43, Alexander Stein wrote:
>> Am Mittwoch, 11. Februar 2026, 15:23:16 CET schrieb Danilo Krummrich:
>>> +{
>>> + int ret;
>>> +
>>> + ret = platform_driver_register(&imx8qxp_clk_driver);
>>> + if (ret)
>>> + return ret;
>>> +
>>> + ret = imx_clk_scu_module_init();
>>> + if (ret)
>>> + platform_driver_unregister(&imx8qxp_clk_driver);
>>> +
>>> + return ret;
>>>
> Also, because the logical flow is that CLK driver is uing SCU for calls I would first call
> imx_clk_scu_module_init and then register the imx8qxp_clk driver.
>
> But there is no functionality issues your your approach too, just a better logical flow.
I now remember why I kept it this way around. If we swap it we have to call
imx_clk_scu_module_exit() in the unwind path of imx8qxp_clk_init().
Consequently, we'd have to drop __exit from imx_clk_scu_module_exit().
Please let me know what you prefer.
Thanks,
Danilo
next prev parent reply other threads:[~2026-02-12 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 14:23 [PATCH] clk: scu/imx8qxp: do not register driver in probe() Danilo Krummrich
2026-02-11 14:43 ` Alexander Stein
2026-02-11 14:59 ` Daniel Baluta
2026-02-12 10:57 ` Danilo Krummrich
2026-02-12 17:22 ` Danilo Krummrich [this message]
2026-02-12 19:43 ` Daniel Baluta
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=DGD5O31G6G9X.R8G6EBXXFKAH@kernel.org \
--to=dakr@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=abelvesa@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=daniel.baluta@oss.nxp.com \
--cc=driver-core@lists.linux.dev \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanguidong02@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=peng.fan@nxp.com \
--cc=rafael@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@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