[PATCH 15/16] Add device tree for Ebony
David Gibson
david at gibson.dropbear.id.au
Thu Feb 15 12:53:16 EST 2007
On Thu, Feb 15, 2007 at 01:31:36AM +0100, Segher Boessenkool wrote:
> >>> No, they are cascaded in hardware. I think having UIC1 under UCI0
> >>> is a
> >>> correct representation.
> >>
> >> Only the interrupt routing is cascaded AFAICS, and
> >> there is a separate interrupt tree to express that.
> >
> > In the case of the UICs, I don't see that there's anything "only"
> > about the interrupt routing. They're DCR controlled, and are not on
> > the normal bus.
>
> Yes. UIC1 is not addressed via UIC0, and as such should
> not be a child of it; it should be a direct child of its DCR
> controller, just like UIC0.
No, the DCR tree, like the interrupt tree in most cases, is
independent of the main tree structure. The ultimate DCR parent is
the CPU node. I see no reason to prefer the DCR connection over the
interrupt connection for the nesting here.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
More information about the Linuxppc-dev
mailing list