Re: [Query]: hrtimers: why don't we consider hrtimers in get_next_timer_interrupt()

Hi Preeti,

On 23 April 2014 17:54, Preeti Murthy preeti.lkml@gmail.com wrote:

On Wed, Apr 23, 2014 at 3:08 PM, Viresh Kumar viresh.kumar@linaro.org wrote:

In case of high resolution mode, the clock device would have already been programmed for the upcoming hrtimer, the last time the list of hrtimers was evaluated. So we have already taken care of hrtimers to expire next.

I actually missed this part and things look correct with this. We aren't choosing the next device event here but just the next time we need tick.

Thanks.