Re: [PATCH V2 0/2] clockevents: Stop unused clockevent devices

On 3 April 2015 at 09:04, Viresh Kumar wrote: > Hi, > > A clockevent device is used to service timers/hrtimers requests and the next > event (when it should fire) is decided by the timer/hrtimer expiring next. > When > no timers/hrtimers are pending to be serviced, the expiry time is set to a >

Re: [PATCH V2 0/2] clockevents: Stop unused clockevent devices

On 3 April 2015 at 09:04, Viresh Kumar viresh.ku...@linaro.org wrote: Hi, A clockevent device is used to service timers/hrtimers requests and the next event (when it should fire) is decided by the timer/hrtimer expiring next. When no timers/hrtimers are pending to be serviced, the expiry

[PATCH V2 0/2] clockevents: Stop unused clockevent devices

Hi, A clockevent device is used to service timers/hrtimers requests and the next event (when it should fire) is decided by the timer/hrtimer expiring next. When no timers/hrtimers are pending to be serviced, the expiry time is set to a special value: KTIME_MAX. This would normally happen with

[PATCH V2 0/2] clockevents: Stop unused clockevent devices

Hi, A clockevent device is used to service timers/hrtimers requests and the next event (when it should fire) is decided by the timer/hrtimer expiring next. When no timers/hrtimers are pending to be serviced, the expiry time is set to a special value: KTIME_MAX. This would normally happen with