[lkml]   [2019]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/7] clocksource/arm_arch_timer: Direcly assign set_next_event workaround
On 11/04/2019 18:17, Daniel Lezcano wrote:
> On 08/04/2019 17:49, Marc Zyngier wrote:
>> 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.
>> Signed-off-by: Marc Zyngier <>
> Do you want me to take the patch ?
> Otherwise:
> Acked-by; Daniel Lezcano <>

I'd like to keep most of the series together (just so that I don't have
to track extra stuff).

Thanks for the Ack though.

Jazz is not dead. It just smells funny...

 \ /
  Last update: 2019-04-15 12:19    [W:0.044 / U:6.764 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site