diff options
author | Nicolai Stange <nicstange@gmail.com> | 2017-02-07 00:12:02 +0300 |
---|---|---|
committer | John Stultz <john.stultz@linaro.org> | 2017-03-23 22:14:03 +0300 |
commit | 4e53aa2fde4124878fc6b2183d6e8ec46e12ceb0 (patch) | |
tree | f1c4272d0e0881e88111b05be2cb3ac3288c7ba7 /drivers/vfio | |
parent | 3814ae092d36da04d5fbaf777c1564dc4ee68559 (diff) | |
download | linux-4e53aa2fde4124878fc6b2183d6e8ec46e12ceb0.tar.xz |
clocksource: em_sti: Compute rate before registration
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, em_sti violates this requirement in that it registers its
clockevent device with a dummy rate and sets its final rate through
clockevents_config() called from its ->set_state_oneshot().
This patch moves the setting of the clockevent device's rate to its
registration.
I checked all current em_sti users in arch/arm/mach-shmobile and right now,
none of them changes any rate in any clock tree relevant to em_sti after
their respective time_init(). Since all em_sti instances are created after
time_init(), none of them should ever observe any clock rate changes.
- Determine the ->rate value in em_sti_probe() at device probing rather
than at first usage.
- Set the clockevent device's rate at its registration.
- Although not strictly necessary for the upcoming clockevent core changes,
set the clocksource's rate at its registration for consistency.
Signed-off-by: Nicolai Stange <nicstange@gmail.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'drivers/vfio')
0 files changed, 0 insertions, 0 deletions