[PATCH 15/16] Add device tree for Ebony

[Yoder Stuart-B08248]

> -----Original Message-----
> From: Segher Boessenkool [mailto:segher at kernel.crashing.org] 
> Sent: Wednesday, February 14, 2007 9:09 PM
> To: David Gibson
> Cc: linuxppc-dev at ozlabs.org; Yoder Stuart-B08248
> Subject: Re: [PATCH 15/16] Add device tree for Ebony
> 
> >> 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.
> 
> Yes true; you can hang the UICs from somewhere under the
> "soc" node or whatever you want.  You need some way to
> distinguish separate identical devices though; you can't
> do it by device unit since your devices don't have any
> (they don't have a "reg" but only a "dcr-reg").  If you
> would hang them in a DCR tree, you could use the plain
> "reg" property instead of the "dcr-reg" property and
> all would be fine (if the DCR binding allows this -- and
> it better should, it is the standard OF addressing algorithm).

Is there a DCR binding?  Are the dcr-* properties documented 
anywhere:

dcr-reg         // what do these fields mean?
dcr-parent      // in case there is more than one controller??
dcr-controller
dcr-access-method = "native"   // what are the other options?

Stuart