[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGb2v67qHKVGdNDmg_mbT-bkhAmn=NxQBsRZMtGgpdOGh6Z37w@mail.gmail.com>
Date: Tue, 3 Jun 2025 12:41:31 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: tglx@...utronix.de, Jim Cromie <jim.cromie@...il.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>, Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jernej Skrabec <jernej.skrabec@...il.com>, Samuel Holland <samuel@...lland.org>,
Thierry Reding <thierry.reding@...il.com>, Jonathan Hunter <jonathanh@...dia.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>, Marco Elver <elver@...gle.com>, Nam Cao <namcao@...utronix.de>,
linux-kernel@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
linux-tegra@...r.kernel.org, John Stulz <jstultz@...gle.com>,
Will McVicker <willmcvicker@...gle.com>, Peter Griffin <peter.griffin@...aro.org>,
Saravan Kanna <saravanak@...gle.com>
Subject: Re: [PATCH v1 3/7] clocksource/drivers/sun5i: Add module owner
On Mon, Jun 2, 2025 at 11:19 PM Daniel Lezcano
<daniel.lezcano@...aro.org> wrote:
>
> The conversion to modules requires a correct handling of the module
> refcount in order to prevent to unload it if it is in use. That is
> especially true with the clockevents where there is no function to
> unregister them.
>
> The core time framework correctly handles the module refcount with the
> different clocksource and clockevents if the module owner is set.
>
> Add the module owner to make sure the core framework will prevent
> stupid things happening when the driver will be converted into a
> module.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
Acked-by: Chen-Yu Tsai <wens@...e.org>
Powered by blists - more mailing lists