[Resend RFC PATCH 3/5] cpuidle/ppc: Add timer offload framework to support deep idle states

2013-07-25 Thread Preeti U Murthy
On ppc, in deep idle states, the local clock event device of CPUs gets switched off. On PowerPC, the local clock event device is called the decrementer. Make use of the broadcast framework to issue interrupts to cpus in deep idle states on their timer events, except that on ppc, we do not have an

[RFC PATCH 3/5] cpuidle/ppc: Add timer offload framework to support deep idle states

2013-07-25 Thread Preeti U Murthy
On ppc, in deep idle states, the lapic of the cpus gets switched off. Hence make use of the broadcast framework to wakeup cpus in sleep state, except that on ppc, we do not have an external device such as HPET, but we use the lapic of a cpu itself as the broadcast device. Instantiate two

[RFC PATCH 3/5] cpuidle/ppc: Add timer offload framework to support deep idle states

2013-07-25 Thread Preeti U Murthy
On ppc, in deep idle states, the lapic of the cpus gets switched off. Hence make use of the broadcast framework to wakeup cpus in sleep state, except that on ppc, we do not have an external device such as HPET, but we use the lapic of a cpu itself as the broadcast device. Instantiate two

[Resend RFC PATCH 3/5] cpuidle/ppc: Add timer offload framework to support deep idle states

2013-07-25 Thread Preeti U Murthy
On ppc, in deep idle states, the local clock event device of CPUs gets switched off. On PowerPC, the local clock event device is called the decrementer. Make use of the broadcast framework to issue interrupts to cpus in deep idle states on their timer events, except that on ppc, we do not have an