Marc Zyngier 5ef19a161c clocksource/arm_arch_timer: Direcly assign set_next_event workaround
When a given timer is affected by an erratum and requires an
alternative implementation of set_next_event, we do a rather
complicated dance to detect and call the workaround on each
set_next_event call.

This is clearly idiotic, as we can perfectly detect whether
this CPU requires a workaround while setting up the clock event
device.

This only requires the CPU-specific detection to be done a bit
earlier, and we can then safely override the set_next_event pointer
if we have a workaround associated to that CPU.

Acked-by: Mark Rutland <mark.rutland@arm.com>
Acked-by; Daniel Lezcano <daniel.lezcano@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2019-04-30 16:10:57 +01:00
..
2019-03-30 10:09:11 -07:00
2019-03-06 09:41:12 -08:00
2019-03-28 11:14:31 +01:00
2019-03-16 13:05:32 -07:00
2019-03-29 03:04:47 +01:00
2019-03-29 10:45:11 +10:00
2019-03-06 14:18:59 -08:00
2019-03-15 14:37:46 -07:00
2019-03-08 10:02:58 -08:00
2019-03-07 08:59:26 -07:00
2019-03-16 12:36:39 -07:00
2019-03-10 11:54:48 -07:00
2019-03-10 11:54:48 -07:00
2019-03-09 15:53:03 -08:00
2019-03-16 13:05:32 -07:00
2019-03-10 11:54:48 -07:00
2019-03-10 10:17:23 -07:00
2019-03-14 09:00:06 -07:00
2019-03-12 09:46:32 -07:00
2019-03-29 14:58:49 -07:00
2019-03-09 14:57:08 -08:00
2019-03-16 12:51:50 -07:00
2019-03-06 09:41:12 -08:00
2019-03-29 15:31:16 +01:00
2019-03-07 12:56:26 -08:00
2019-03-10 12:47:57 -07:00
2019-03-15 14:22:59 -07:00
2019-03-10 12:29:52 -07:00