[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191213025435.7F2092073D@mail.kernel.org>
Date: Thu, 12 Dec 2019 18:54:34 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Jerome Brunet <jbrunet@...libre.com>,
Michael Turquette <mturquette@...libre.com>
Cc: Jerome Brunet <jbrunet@...libre.com>,
Kevin Hilman <khilman@...libre.com>,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, Jian Hu <jian.hu@...ogic.com>
Subject: Re: [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 <jian.hu@...ogic.com>
> Fixes: fc0c209c147f ("clk: Allow parents to be specified without string names")
> Signed-off-by: Jerome Brunet <jbrunet@...libre.com>
> ---
Applied to clk-fixes
Powered by blists - more mailing lists