diff options
| author | Tero Kristo <[email protected]> | 2017-08-15 08:42:17 +0000 |
|---|---|---|
| committer | Tero Kristo <[email protected]> | 2017-12-01 13:15:38 +0000 |
| commit | 3d8598fb9c5a77837d9c0951efc5c36fdf91d87c (patch) | |
| tree | 51ce4c28c45914709817e762824ad23f48ce3f54 /lib/debugobjects.c | |
| parent | clk: ti: add support for clkctrl aliases (diff) | |
| download | kernel-3d8598fb9c5a77837d9c0951efc5c36fdf91d87c.tar.gz kernel-3d8598fb9c5a77837d9c0951efc5c36fdf91d87c.zip | |
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 <[email protected]>
Acked-by: Stephen Boyd <[email protected]>
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions