[lkml]   [2019]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2] clk: walk orphan list on clock provider registration
Quoting Jerome Brunet (2019-12-03 00:08:05)
> So far, we walked the orphan list every time a new clock was registered
> in CCF. This was fine since the clocks were only referenced by name.
> Now that the clock can be referenced through DT, it is not enough:
> * Controller A register first a reference clocks from controller B
> through DT.
> * Controller B register all its clocks then register the provider.
> Each time controller B registers a new clock, the orphan list is walked
> but it can't match since the provider is registered yet. When the
> provider is finally registered, the orphan list is not walked unless
> another clock is registered afterward.
> This can lead to situation where some clocks remain orphaned even if
> the parent is available.
> Walking the orphan list on provider registration solves the problem.
> Reported-by: Jian Hu <>
> Fixes: fc0c209c147f ("clk: Allow parents to be specified without string names")
> Signed-off-by: Jerome Brunet <>
> ---

Applied to clk-fixes

 \ /
  Last update: 2019-12-13 03:54    [W:0.030 / U:7.640 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site