On Wed, Sep 5, 2012 at 5:11 PM, Benoit Cousson <b-cous...@ti.com> wrote: > > Hi Tony, > > On 09/05/2012 02:03 AM, Tony Lindgren wrote: > > If NR_IRQS is less than MAX_IRQS, we end up writing past the > > irq_target_cpu array in omap_wakeupgen_init(): > > > > /* Associate all the IRQs to boot CPU like GIC init does. */ > > for (i = 0; i < max_irqs; i++) > > irq_target_cpu[i] = boot_cpu; > > > > This can happen if SPARSE_IRQ is enabled as by default NR_IRQS is > > set to 16. Without this patch we're overwriting other data during > > the boot. > > In fact I already sent a patch to fix that when I started my SPARSE_IRQ > cleanup, but it looks like it was never merged :-( > I guess I forgot a little bit that series. > Indeed. I remember acking few patches in that series. Infact this patch set was the basis on which I was talking to Arnd that SPARSE_IRQ should work on OMAP. Didn't think that it has not made it yet in mainline.
Regards Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
