ARM: OMAP2 DT clock conversion
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 12 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 12 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/12] ARM: OMAP2 DT clock conversion
Quoted 14 lines · Tony Lindgren
Quoted 5 lines · Tero Kristo
Hmm, some clock node is broken, might be missing a name or parent name for some reason. Can you try to boot with DEBUG enabled so you get pr_debug:s out and see which clock is being initialized during the crash?
...
[ 0.000000] ti_dt_clk_init_provider: ti_dt_clk_init_provider: initializing: core_d18_ck [ 0.000000] ti_dt_clk_init_provider: ti_dt_clk_init_provider: initializing: vlynq_mux_fck [ 0.000000] ti_dt_clk_init_provider: ti_dt_clk_init_provider: initializing: vlynq_fck [ 0.000000] Unable to handle kernel NULL pointer dereference at virtual address 00000000...
Quoted 8 lines
We really should be registering the clocks lazily as needed BTW. That leaves out the dependency to
DEBUG_LLfor seeing any kind of decent error messages during the booting.Regards,
Tony
Hey Tony,
Can you retry with the branch? I just pushed one patch there, seems the parents for the vlynq_mux_fck were somewhat broken (there are holes in the valid mux values list, which hasn't happened with any other mux-clock so far.)
If this works, I will rework the series a bit and send v2 out. Alternatively I need to add extra debug info.
-Tero