[PATCH] clk: Propagate prepare and enable when reparenting orphans
dianders at chromium.org
Fri Nov 7 16:46:20 PST 2014
On Fri, Nov 7, 2014 at 4:23 PM, Russell King - ARM Linux
<linux at arm.linux.org.uk> wrote:
> On Fri, Nov 07, 2014 at 04:14:23PM -0800, Doug Anderson wrote:
>> I guess I'm still confused. My patch continues to be about orphans
>> and I don't see the bug you are pointing to.
> Ah, in which case, the question changes: how can an orphaned clock be
> succesfully prepared and enabled?
> Drivers expect that a clock for which clk_enable() has returned
> successfully _will_ at that point be supplying the clock. If we don't
> yet know it's parent, how do we know that it will be supplying that
> What about a driver calling clk_set_rate() on an orphaned clock?
> From what I can see (__clk_reparent will re-set the child's clock when
> reparenting) having a driver able to claim an orphaned clock, let
> alone prepare and enable it, looks rather buggy to me.
Yes, it is pretty questionable. I discussed some of this in my
comment message in this patch. Specifically, I said:
> NOTE: this does bring up the question about whether the enable of the
> orphan actually made sense. If the orphan's parent wasn't enabled by
> default (by the bootloader or the default state of the hardware) then
> the original enable of the orphan probably didn't do what the caller
> though it would. Some users of the orphan might have preferred an
> EPROBE_DEFER be returned until we had a full path to a root clock.
> This patch doesn't address those concerns and really just syncs up the
I'm not sure I want to go all the way doing the above and adding the
EPROBE_DEFER because I think that there are probably lots of users out
there that are assuming that they can enable/disable an orphaned clock
and I can't myself commit to fixing all of them. If you want to
propose such a patch and can get it landed then my patch would
certainly not be necessarily.
Also see the note in the original commit message:
> Note that xin32k on rk808 is a clock that cannot be disabled in
> hardware (it's an always on clock), so really all we needed to do was
> to sync up the state.
More information about the linux-arm-kernel