[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5CpFXjm1a2C01=uiHLjcNSe4MzgLUyfDvK0LCdQ8+KNEw@mail.gmail.com>
Date: Mon, 21 Nov 2022 07:59:33 -0300
From: Fabio Estevam <festevam@...il.com>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: Abel Vesa <abelvesa@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH] clk: imx8mp: register driver at arch_initcall time
On Mon, Nov 21, 2022 at 6:44 AM Rasmus Villemoes
<linux@...musvillemoes.dk> wrote:
> That doesn't seem to be true. To test, I just built the imx8mq clk
> driver as a module, and I could certainly both load and unload that on
> my imx8mp platform. Sure, no "bind" attribute shows up in the
> /sys/bus/platform/drivers/imx8mq-ccm/ directory, which is exactly what
> one expects, but the module can be loaded just fine. And since it can be
> loaded, it should also have a proper __exit call for deregistering the
> driver on unload.
You are right. Sorry for the confusion.
Powered by blists - more mailing lists