summaryrefslogtreecommitdiffstats
path: root/drivers/s390
diff options
context:
space:
mode:
authorNicolai Stange <nicstange@gmail.com>2017-02-06 22:12:03 +0100
committerJohn Stultz <john.stultz@linaro.org>2017-03-23 12:14:04 -0700
commita17e0178fa2898bd8c4ccaaefa83c729759a361c (patch)
tree960d68fcf6093d97f24717978c76e95c4c790aa8 /drivers/s390
parent4e53aa2fde4124878fc6b2183d6e8ec46e12ceb0 (diff)
downloadlinux-a17e0178fa2898bd8c4ccaaefa83c729759a361c.tar.gz
linux-a17e0178fa2898bd8c4ccaaefa83c729759a361c.tar.bz2
linux-a17e0178fa2898bd8c4ccaaefa83c729759a361c.zip
clocksource: h8300_timer8: Don't reset rate in ->set_state_oneshot()
With the upcoming NTP correction related rate adjustments to be implemented in the clockevents core, the latter needs to get informed about every rate change of a clockevent device made after its registration. Currently, h8300_timer8 violates this requirement in that it registers its clockevent device with the correct rate, but resets its ->mult and ->rate values in timer8_clock_event_start(), called from its ->set_state_oneshot() function. It seems like commit 4633f4cac85a ("clocksource/drivers/h8300: Cleanup startup and remove module code."), which introduced the rate initialization at registration, missed to remove the manual setting of ->mult and ->shift from timer8_clock_event_start(). Purge the setting of ->mult, ->shift, ->min_delta_ns and ->max_delta_ns from timer8_clock_event_start(). Signed-off-by: Nicolai Stange <nicstange@gmail.com> Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'drivers/s390')
0 files changed, 0 insertions, 0 deletions