On 10/12/26 6:59 PM, Jonas Karlman wrote:
Hi Quentin,
On 10/12/2026 6:11 PM, Quentin Schulz wrote:
Hi Jonas,
On 10/12/26 1:15 PM, Jonas Karlman wrote:
[...]
The RK3506 clock driver is notably missing from this list of "RK35xx
clock drivers". I'm assuming this is because support for the RK3506
clock driver got merged after commit c6bba31dbdd4 ("rockchip:
spl-boot-order: Defer probe of boot device"), so it means if it's
broken, it just never worked in the first place and we should rather dig
into the problem instead of doing what we do for the other RK35xx SoCs,
was this your conclusion as well or did I just incorrectly extrapolate?
The RK3506 clock driver currently initialize a few clocks from bind()
in XPL :-S
So it is not affected, or rather it worked around the issue for USB/RAM
boot in a different way. Should probably have mentioned something about
the RK3506 situation in cover letter.
In my work-in-progress branch at [1] I have a "WIP: clk: rockchip:
rk3506: Rework early clock init" commit that re-work that clock init to
use similar probe-after-bind style. I likely just deferred rk3506 for a
future refactor series as it was already "working" and the diff to
change it was very different to the patches in this series.
ACK, thanks for the heads up. Marking this series as Changes Requested
on patchwork as you said you'd send a v2.
Cheers,
Quentin
