3 Dec
2025
3 Dec
'25
11:58 a.m.
On Wed, Dec 03, 2025 at 04:12:04PM +0530, Siddharth Vadapalli wrote:
On Tue, 2025-12-02 at 22:53 +0000, Mark Brown wrote:
Avoid this confused ownership by moving the pm_runtime_get_noresume() to after the last point at which the probe() function can fail.
Thank you for the patch. The 'clock already disabled' issue persists on J721E SoC with the patch applied:
Do you mean it reappears rather than persists?
https://gist.github.com/Siddharth-Vadapalli-at-TI/a664f59366ad681856b862d621...
Interesting, I can't see any logging that indicates we should be reaching the error handling paths in that log...