On 06/04, Felipe Balbi wrote: > On Thu, Jun 04, 2015 at 03:18:25PM -0500, Felipe Balbi wrote: > > On Thu, Jun 04, 2015 at 03:08:50PM -0500, Felipe Balbi wrote: > > > Hi, > > > > > > On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote: > > > > Also, check /proc/timer_list for a "Broadcast device". If you don't > > > > define one, the TWD timers are set to periodic mode, with hrtimers > > > > disabled. > > > > > > Did you manage to turn global timer into Broadcast device ? > > > > arm_global_timer is marked PERCPU, so it will never be chosen as > > broadcast. > > Perhaps this is acceptable ? > > diff --git a/drivers/clocksource/arm_global_timer.c b/drivers/clocksource/arm_global_timer.c > index e6833771a716..8c0170ac367d 100644 > --- a/drivers/clocksource/arm_global_timer.c > +++ b/drivers/clocksource/arm_global_timer.c > @@ -169,8 +169,9 @@ static int gt_clockevents_init(struct clock_event_device *clk) > int cpu = smp_processor_id(); > > clk->name = "arm_global_timer"; > - clk->features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT | > - CLOCK_EVT_FEAT_PERCPU; > + clk->features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT; > + if (is_smp() || setup_max_cpus) > + clk->features |= CLOCK_EVT_FEAT_PERCPU; > clk->set_mode = gt_clockevent_set_mode; > clk->set_next_event = gt_clockevent_set_next_event; > clk->cpumask = cpumask_of(cpu); > What is this doing? Allowing the global timer to become the broadcast timer? Can you share all the clockevents that are being registered in the system and what ratings and features they have? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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
