On Thu, Jan 15 2015 at 2:27:56 pm GMT, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Thursday 15 January 2015 13:42:57 Marc Zyngier wrote: >> Of course, this is in no way a proper fix, but I suppose the OMAP DT is >> still missing a few bits... > > I must be missing something here, but all the interrupts are listed > correctly in the DT, so what is the omap_hwmod_irq_info actually > achieving on omap4 and omap5? > > Would it work if we just remove the incorrect copy of the resource > and use the one that comes from DT? By the look of it, omap_hwmod_irq_info serves multiple purposes: - low level configuration (pads, probably more stuff) - interrupt description for some drivers, using resources. It should be fairly easy to do the latter, but the former looks more tricky (it would push the pad configuration down to the drivers, which is avoided at the moment). Probably there is a workable strategy, but my knowledge about OMAP is close to *nothing*... M. -- Jazz is not dead. It just smells funny. -- 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
