The clockevent has to be reprogrammed if the timer's input
clock frequency changes and the timer is in periodic mode, in order to
maintain the correct timer interval.
Signed-off-by: Soren Brinkmann <soren.brinkm...@xilinx.com>
---
drivers/clocksource/cadence_ttc_timer.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/clocksource/cadence_ttc_timer.c
b/drivers/clocksource/cadence_ttc_timer.c
index a92350b55d32..68a336038d8f 100644
--- a/drivers/clocksource/cadence_ttc_timer.c
+++ b/drivers/clocksource/cadence_ttc_timer.c
@@ -338,6 +338,10 @@ static int ttc_rate_change_clockevent_cb(struct
notifier_block *nb,
/* update cached frequency */
ttc->freq = ndata->new_rate;
+ if (ttcce->ce.mode == CLOCK_EVT_MODE_PERIODIC)
+ ttc_set_interval(ttc, DIV_ROUND_CLOSEST(ttc->freq,
+ PRESCALE * HZ));
+
/* fall through */
}
case PRE_RATE_CHANGE:
--
1.8.4.2
--
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/
