On 04/07, Lee Jones wrote: > Lots of platforms contain clocks which if turned off would prove fatal. > The only way to recover from these catastrophic failures is to restart > the board(s). Now, when a clock provider is registered with the > framework it is possible for a list of always-on clocks to be supplied > which must be kept ungated. Each clock mentioned in the newly > introduced 'clock-always-on' will be clk_prepare_enable()d where the > normal references will be taken. This will prevent the common clk > framework from attempting to gate them during the clk_disable_unused() > and disable_clock() procedures.
Ah I see now. The disable_clock() part is from the PM core not the common clock framework. This paragraph could be the commit text for the binding patch. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
