On Tue, 17 Jun 2014, Tomi Valkeinen wrote: > When setting the rate of a clock, by default the clock framework will > change the parent of the clock to the most suitable one in > __clk_mux_determine_rate() (most suitable by looking at the clock rate).
That is just insane. > This is a rather dangerous default, and causes problems on AM43x when > using display and ethernet. There are multiple ways to select the clock > muxes on AM43x, and some of those clock paths have the same source > clocks for display and ethernet. When changing the clock rate for the > display subsystem, the clock framework decides to change the display mux > from the dedicated display PLL to a shared PLL which is used by the > ethernet, and then changes the rate of the shared PLL, breaking the > ethernet. > > As I don't think there ever is a case where we want the clock framework > to automatically change the parent clock of a clock mux, this patch sets > the CLK_SET_RATE_NO_REPARENT for all ti,mux-clocks. > > Signed-off-by: Tomi Valkeinen <tomi.valkei...@ti.com> Reviewed-by: Paul Walmsley <p...@pwsan.com> - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
