On Sun, Feb 28, 2021 at 11:29 AM Andy Shevchenko
[off-list ref] wrote:
On Sun, Feb 28, 2021 at 11:07 AM Andy Shevchenko
[off-list ref] wrote:
quoted
On Friday, February 26, 2021, Rasmus Villemoes [off-list ref] wrote:
quoted
The only purpose of this driver is to serve as a consumer of the input
clock, to prevent it from being disabled by clk_disable_unused().
We have a clock API to do the same (something like marking it used or so) why do you need a driver?
Example:
https://elixir.bootlin.com/linux/latest/source/drivers/platform/x86/pmc_atom.c#L365
If it's a DT based platform I think you can make it somehow work thru DT.
Okay, briefly looking at the state of affairs [1] seems like you need
to hack it into clock provider.
[1]: https://elixir.bootlin.com/linux/latest/C/ident/CLK_IS_CRITICAL
--
With Best Regards,
Andy Shevchenko