forked from luck/tmp_suning_uos_patched
1d80415db6
Unfortunately on some exynos systems, resetting the mct counter also resets the architected timer counter. This can cause problems if the architected timer driver has already been initialized because the kernel will think that the counter has wrapped around, causing a big jump in printk timestamps and delaying any scheduled clock events until the counter reaches the value it had before it was reset. The kernel code makes no assumptions about the initial value of the mct counter so there is no reason from a software perspective to clear the counter before starting it. This also fixes the problems described in the previous paragraph. Cc: Olof Johansson <olof@lixom.net> Cc: Tomasz Figa <tomasz.figa@gmail.com> Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Doug Anderson <dianders@chromium.org> Tested-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com> |
||
|---|---|---|
| .. | ||
| acpi_pm.c | ||
| arm_arch_timer.c | ||
| arm_global_timer.c | ||
| bcm_kona_timer.c | ||
| bcm2835_timer.c | ||
| cadence_ttc_timer.c | ||
| clksrc-dbx500-prcmu.c | ||
| clksrc-of.c | ||
| cs5535-clockevt.c | ||
| dummy_timer.c | ||
| dw_apb_timer_of.c | ||
| dw_apb_timer.c | ||
| em_sti.c | ||
| exynos_mct.c | ||
| fsl_ftm_timer.c | ||
| i8253.c | ||
| Kconfig | ||
| Makefile | ||
| metag_generic.c | ||
| mmio.c | ||
| moxart_timer.c | ||
| mxs_timer.c | ||
| nomadik-mtu.c | ||
| qcom-timer.c | ||
| samsung_pwm_timer.c | ||
| scx200_hrt.c | ||
| sh_cmt.c | ||
| sh_mtu2.c | ||
| sh_tmu.c | ||
| sun4i_timer.c | ||
| tcb_clksrc.c | ||
| tegra20_timer.c | ||
| time-armada-370-xp.c | ||
| time-efm32.c | ||
| time-orion.c | ||
| timer-keystone.c | ||
| timer-marco.c | ||
| timer-prima2.c | ||
| timer-sun5i.c | ||
| timer-u300.c | ||
| versatile.c | ||
| vf_pit_timer.c | ||
| vt8500_timer.c | ||
| zevio-timer.c | ||