Hi Santosh, On Wed, Mar 13, 2013 at 09:28:22AM +0000, Santosh Shilimkar wrote: > (Forgot to CC Thomas) > > On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote: > > With recent arm broadcast time clean-up from Mark Rutland, the dummy > > broadcast device is always registered with timer subsystem. And since > > the rating of the dummy clock event is very high, it is preferred > > over a real broad-cast clock event. > > > > This is a change in behavior from past and not an intended > > one. So reduce the rating of the dummy clockevent so that > > real broadcast device is selected when available. > > > > Without this all the C states with C3STOP won't work since > > the broad cast notifier will take an abort. > > > > Cc: Mark Rutland <mark.rutland@xxxxxxx> > > Cc: Russell King <linux@xxxxxxxxxxxxxxxx> > > > > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > --- > > Its a regression so hopefully can get into the 3.9-rcx. Noticed > > this one on A15 platform. A9 platform the issue may not be seen > > since the local timer check avoids dummy timer registration. > > > Some one pointed me to a fix made by Mark which was discussed > under '[BUG] ARM Architected timers appear broken in 3.9-rc1' subject. > That patch seems to be more of work around since the root of the > problem is incorrect dummy timer rating. Either way, both patches > fix the issue. Is the problem that the dummy timer is being registered as the broadcast source, or that it is selected as a local timer in preference of real timers? If it is the former, Then I believe my patch solve the issue more generally - if you happen to register a dummy timer before other timers, it will become the broadcast source. Regardless of how temporary this is, it should never happen, and lowering the rating of the dummy won't fix this. If it is the latter, then this patch would ensure that a real timer with a rating over 100 is selected in preference to the dummy, which is certainly what we want. The proposed generic dummy timer in Stephen Boyd's local timer API removal series [1] similarly uses a low rating to ensure that real timers are selected in preference to an always-registered dummy. I note that the architected timer has a higher rating (450) than the dummy (400), so this shouldn't currently be a problem. Have I missed something? [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-March/153208.html Thanks, Mark. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
