Re: [PATCH] arm: sched: stop sched_clock() during suspend

2012-10-23 Thread Linus Walleij
On Mon, Oct 22, 2012 at 1:54 PM, Felipe Balbi wrote: > The scheduler imposes a requirement to sched_clock() > which is to stop the clock during suspend, if we don't > do that IRQ threads will be rescheduled in the future > which might cause transfers to timeout depending on > how driver is writte

Re: [PATCH] arm: sched: stop sched_clock() during suspend

2012-10-22 Thread Linus Walleij
On Mon, Oct 22, 2012 at 7:05 PM, Kevin Hilman wrote: > However, in light of RT throttling, this a correctness issue for process > accounting, so I agree that this should be done for all platforms > instead of providing an optional 'needs suspend' version of the API, > even though it means printk

Re: [PATCH] arm: sched: stop sched_clock() during suspend

2012-10-22 Thread Kevin Hilman
+Colin Cross, Barry Song also Felipe Balbi writes: > The scheduler imposes a requirement to sched_clock() > which is to stop the clock during suspend, if we don't > do that IRQ threads will be rescheduled in the future > which might cause transfers to timeout depending on > how driver is written

Re: [PATCH] arm: sched: stop sched_clock() during suspend

2012-10-22 Thread Felipe Balbi
Hi, On Mon, Oct 22, 2012 at 02:54:37PM +0300, Felipe Balbi wrote: > The scheduler imposes a requirement to sched_clock() > which is to stop the clock during suspend, if we don't > do that IRQ threads will be rescheduled in the future > which might cause transfers to timeout depending on > how driv

[PATCH] arm: sched: stop sched_clock() during suspend

2012-10-22 Thread Felipe Balbi
The scheduler imposes a requirement to sched_clock() which is to stop the clock during suspend, if we don't do that IRQ threads will be rescheduled in the future which might cause transfers to timeout depending on how driver is written. This became an issue on OMAP when we converted omap-i2c.c to