On Thu, Mar 08, 2012 at 02:47:25PM -0500, Jason wrote: > On Thu, Mar 08, 2012 at 08:27:11PM +0100, Thomas Gleixner wrote: > > On Thu, 8 Mar 2012, Arnd Bergmann wrote: > > > > > On Thursday 08 March 2012, Jason wrote: > > > > > > > > On Wed, Mar 07, 2012 at 09:13:04PM +0000, Arnd Bergmann wrote: > > > > > Finally, something could be wrong with the interrupt controller. > > > > > AFAICT, you register it through the device tree now, but it's also > > > > > getting initialized through kirkwood_init_irq, so the numbers > > > > > would all be wrong. > > > > > > > > Yes, I'm working through this now. mv_cesa silently fails to come up > > > > if it can't find the interrupt controller via fdt. So, it needs to get > > > > done. > > > > > > > > Right now, I'm looking at how mach-versatile does it (vic_init()) since > > > > it's also an ARM926ej-s... > > > > > > > > > > Ok, sounds good. It's not important whether it's an ARM9 or not btw. > > > You should look at both anything that defines an "interrupt-controller" > > > property as an example including > > > Documentation/devicetree/bindings/arm/vic.txt > > > and Documentation/devicetree/bindings/arm/gic.txt. > > > > > > (taking Thomas Gleixner on Cc) > > > > > > Since the orion irq chip is based on irqchip_generic, it would be > > > perfect to have a generic irqchip binding to go along with > > > kernel/irq/generic-chip.c. Not sure if anyone has thought about this > > > before, but it looks like we can completely avoid using > > > arch/arm/plat-orion/irq.c and arch/arm/mach-kirkwood/irq.c if we > > > do that. > > > > Right. That should be trivial to implement. > > ok, I'm on it. kernel/irq/of_generic_irq.c sound good?
Rob Herring has done some work in this area. Please coordinate with him. g. _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss