On 10/10/13 12:13, Maxime Ripard wrote: > On Wed, Sep 25, 2013 at 04:16:14PM -0700, Stephen Boyd wrote: >> On 09/25/13 07:03, Maxime Ripard wrote: >>> + sun5i_clockevent.cpumask = cpumask_of(0); >> Can this timer interrupt any CPU or is it hardwired to CPU0? If the >> interrupt can go to any CPU this should be cpu_possible_mask instead. > I've changed the few other things you spotted, but this one making the > timer unusable. > > I think what happens here is that we have the A31 I've tested these > patches on is a quad-core SoC. As such, the device tree has 4 CPUs > declared. However, we don't have any SMP support for it now. So we end > up having 4 cpus set as possible, and only one online (the boot cpu), > which isn't working.
Can you explain more why it isn't working? Is the timer being rejected in favor of another timer? > > Would using cpu_online_mask work in our case? It may work but it's probably hiding a problem with CONFIG_SMP=y -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
