Re: [RFC v4 16/22] clockevents: use ->min_delta_ticks_adjusted to program minimum delta

> static int clockevents_program_min_delta(struct clock_event_device *dev) > { > - unsigned long long clc; > - int64_t delta; > - > - delta = dev->min_delta_ns; > - > if (clockevent_state_shutdown(dev)) > return 0; > > dev->retries++; > - clc =

Re: [RFC v4 16/22] clockevents: use ->min_delta_ticks_adjusted to program minimum delta

> static int clockevents_program_min_delta(struct clock_event_device *dev) > { > - unsigned long long clc; > - int64_t delta; > - > - delta = dev->min_delta_ns; > - > if (clockevent_state_shutdown(dev)) > return 0; > > dev->retries++; > - clc =

[RFC v4 16/22] clockevents: use ->min_delta_ticks_adjusted to program minimum delta

The use of a clockevent device's ->min_delta_ns in the event programming path hinders upcoming changes to the clockevent core making it NTP correction aware: both, ->mult and ->min_delta_ns would need to get updated as well as consumed atomically and we'd rather like to avoid any locking here. We

[RFC v4 16/22] clockevents: use ->min_delta_ticks_adjusted to program minimum delta

The use of a clockevent device's ->min_delta_ns in the event programming path hinders upcoming changes to the clockevent core making it NTP correction aware: both, ->mult and ->min_delta_ns would need to get updated as well as consumed atomically and we'd rather like to avoid any locking here. We