diff options
author | Simon Horman <horms+renesas@verge.net.au> | 2013-08-08 17:59:17 +0900 |
---|---|---|
committer | Simon Horman <horms+renesas@verge.net.au> | 2013-08-30 09:31:39 +0900 |
commit | 7658ea2fb57831c6836ffcfb20bcb84f3ff55dfb (patch) | |
tree | cdd98e20b4589f58f9f1dcca64789bfa12264d2a /virt/kvm | |
parent | ab40900b70dc31a64f23b1b4dbb0917afb039775 (diff) | |
download | blackbird-obmc-linux-7658ea2fb57831c6836ffcfb20bcb84f3ff55dfb.tar.gz blackbird-obmc-linux-7658ea2fb57831c6836ffcfb20bcb84f3ff55dfb.zip |
ARM: shmobile: r8a7779: Update early timer initialisation order
a894fcc2d01a89e6fe3da0845a4d80a5312e1124 ("ARM: smp_twd: Divorce smp_twd
from local timer API") altered twd_local_timer_common_register() so that it
may make use of late_timer_init.
This is problematic on marzen with Magnus's recent patch "ARM: shmobile:
marzen: Switch to DT_MACHINE_START" which switches marzen around to enable
USE_OF and thus shmobile_timer_init(), which is registered as
late_time_init by shmobile_earlytimer_init() stops being a no-op.
As a work-around I have updated r8a7779_earlytimer_init() so that
shmobile_earlytimer_init() is called after r8a7779_register_twd().
Or in other words, the shmobile_earlytimer_init() setting of
late_time_init overwrites that of twd_local_timer_common_register().
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Acked-by: Magnus Damm <damm@opensource.se>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions