Tero Kristo 3d8598fb9c clk: ti: clkctrl: use fallback udelay approach if timekeeping is suspended
In certain cases it is possible that the timekeeping has been suspended
already when attempting to disable/enable a clkctrl clock. This will
happen at least on am43xx platform when attempting to enable / disable
the clockevent source itself, burping out a warning from timekeeping core.

The sequence of events leading to this:
-> timekeeping_suspend()
 -> clockevents_suspend()
  -> omap_clkevt_idle()
   -> omap_hwmod_idle()
    -> _omap4_clkctrl_clk_disable()
     -> _omap4_is_timeout()

Avoid the issue by checking if the timekeeping is suspended and using
the fallback udelay approach for checking timeouts.

Signed-off-by: Tero Kristo <t-kristo@ti.com>
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
2017-12-01 15:15:38 +02:00
..
2017-11-03 09:02:30 -07:00
2017-11-03 09:02:30 -07:00
2017-11-01 23:25:43 -07:00
2017-08-30 22:30:30 -07:00
2016-03-02 17:48:26 -08:00
2017-09-29 14:17:17 -07:00
2016-10-23 10:18:45 -07:00
2017-09-01 16:00:54 -07:00
2017-11-01 23:25:51 -07:00
2017-11-01 23:25:51 -07:00