On 23 May 2014 17:11, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Fri, May 23, 2014 at 05:06:27PM +0530, Tushar Behera wrote: >> On 23 May 2014 16:44, Mark Brown <broonie@xxxxxxxxxx> wrote: > >> > Should be clk_prepare_enable() and similarly for the disable and you >> > should check the error codes but yes, that looks good. > >> I was planning to keep clk_prepare/clk_unprepare in probe/remove. > > Why - what purpose would it serve to leave the clock prepared but not > enabled? I was getting some kernel slow path warning initially while preparing this code, but not able to reproduce that warning now. -- Tushar Behera -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
