On 4/28/26 03:55, Andy Shevchenko wrote:
> 
> There are 6 drivers that do the same, why is only this one special?
> Have you checked the flow on the error path of the caller of this
> `platform_clock_control()`? Maybe there it calls with the opposite
> event to shut the clock down?
> 
> TL;DR: If it's a real issue, it has to be fixed for all affected drivers.

Yes, I'm going to check the other drivers.

-- 
Thanks,
Cássio