[PATCH 1/3] vic: add device tree bindings
Grant Likely
grant.likely at secretlab.ca
Sun Jul 31 14:11:07 EST 2011
On Mon, Jul 25, 2011 at 11:31:51PM +0100, Jamie Iles wrote:
> Hi Grant,
>
> On Mon, Jul 25, 2011 at 02:04:34PM -0600, Grant Likely wrote:
> > irq_domain_add_simple() is a stop-gap shortcut for interrupt
> > controllers that don't use irq_domain directly. I'm okay with doing
> > this in the short term, but I imagine it will want to change in the
> > near future to take advantage of hw->linux irq translation provided by
> > irq_domain when it matures.
>
> I have to admit to taking this from other controllers without fully
> understanding it. Is there any documentation on how this should be done
> correctly in the longer term?
Documentation? Ummmm... no, not yet. :-/ There will be though.
>
> > > + }
> >
> > I think that rather than writing a interrupt-controller-specific
> > parse route like this one, it would be much better to have a generic
> > helper that finds and sorts all the interrupt controllers before
> > calling a setup callback for each one.
>
> Hmm, not sure I follow this. I can see that many controllers would have
> some common properties so there will be some common code - are you
> suggesting having something do all the parsing then callbacks for each
> controller type that takes some kind of template or am I way off the
> mark?
No, I'm more talking about having a routine that finds all the
interrupt controllers and figures out the cascading order, and then
calls each irq controller setup routine in order.
g.
More information about the devicetree-discuss
mailing list