On Wed, Jan 22, 2014 at 02:02:57PM +0800, Xiaoguang Chen wrote: > Hi, Mike > > We met a issue between clk_prepare_enable /clk_disable_unprepare and > clk_set_parent.
clk_prepare_enable/disable_unprepare are perfectly fine in themselves. You're looking at the problem wrongly - because drivers can perfectly well call clk_prepare() and clk_unprepare() themselves. There's no requirement for the enable and prepare to be paired together under any kind of lock. > and if below condition occurs, there will be problem > > thread1 thread 2 > call clk_disable_unprepare Okay, if we're calling clk_disable_unprepare(), then the clock must already have been prepared and enabled - which means that the current parent is already prepared and enabled. > 1) clk_disable > get enable lock > ............... > release enable lock This may result in the parent being disabled too. > > call clk_set_parent > get prepare lock > set clock's > parent to another parent At this point, the existing parent clock should be disabled if this clock was enabled, and unprepared if this clock was prepared. The new parent should be prepared and enabled as appropriate too so that everything is kept balanced. > release prepare lock > > 2) clk_unprepare > get prepare lock > unprepare parent clock <<-------------- > release prepare lock And with the above guarantee - which is required in any case to make reparenting safe - there's no problem here. -- FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad. Estimate before purchase was "up to 13.2Mbit". -- 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/