Hi Russell, I've been on holiday, hence the delayed E-mail. On Mon, 27 Oct 2008, Russell King - ARM Linux wrote: > If I take this further, and detect clocks which result in > omap2_clk_wait_ready() being called, but we don't have a corresponding > [if]ck, I see at least these four warnings: > > CLK: omapctrl_ick.0: no other_clk but asked to wait_ready > CLK: sdrc_ick.0: no other_clk but asked to wait_ready > CLK: dpll4_m2x2_ck.0: no other_clk but asked to wait_ready > CLK: omap_32ksync_ick.0: no other_clk but asked to wait_ready > > So, presumably these ick clocks don't have corresponding fck clocks, > which means checking the fck register for the bit would be wrong? Yes, that's right. > So, here's the question: should any of the above clocks result in > omap2_wait_clock_ready() being called? If the answer is no, that's > great. If yes, are there missing clk structures for OMAP3? No, omap2_wait_clock_ready() shouldn't be called for those clocks. The current linux-omap git head does not call omap2_wait_clock_ready() in these cases, as far as I know. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
