summaryrefslogtreecommitdiffstats
path: root/drivers/clocksource/timer-atmel-st.c
diff options
context:
space:
mode:
authorScott Wood <oss@buserror.net>2016-09-22 03:35:17 -0500
committerWill Deacon <will.deacon@arm.com>2016-09-23 17:19:25 +0100
commitf6dc1576cd517440313c9551b6ffa3d7e389c7c7 (patch)
treeb8b7e96634c2df9b8de85b5bb80923c2b6aeae97 /drivers/clocksource/timer-atmel-st.c
parent22e43390456152f6e72ad2632e2b3fb363e94146 (diff)
downloadblackbird-op-linux-f6dc1576cd517440313c9551b6ffa3d7e389c7c7.tar.gz
blackbird-op-linux-f6dc1576cd517440313c9551b6ffa3d7e389c7c7.zip
arm64: arch_timer: Work around QorIQ Erratum A-008585
Erratum A-008585 says that the ARM generic timer counter "has the potential to contain an erroneous value for a small number of core clock cycles every time the timer value changes". Accesses to TVAL (both read and write) are also affected due to the implicit counter read. Accesses to CVAL are not affected. The workaround is to reread TVAL and count registers until successive reads return the same value. Writes to TVAL are replaced with an equivalent write to CVAL. The workaround is to reread TVAL and count registers until successive reads return the same value, and when writing TVAL to retry until counter reads before and after the write return the same value. The workaround is enabled if the fsl,erratum-a008585 property is found in the timer node in the device tree. This can be overridden with the clocksource.arm_arch_timer.fsl-a008585 boot parameter, which allows KVM users to enable the workaround until a mechanism is implemented to automatically communicate this information. This erratum can be found on LS1043A and LS2080A. Acked-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: Scott Wood <oss@buserror.net> [will: renamed read macro to reflect that it's not usually unstable] Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'drivers/clocksource/timer-atmel-st.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud