On Tuesday 02 July 2013, Jason Gunthorpe wrote:
> On Sat, Jun 29, 2013 at 04:04:03PM -0300, Ezequiel Garcia wrote:
> > Personally, I can't see any disadvantage, and the binding looks much
> > cleaner now. But of course I can be wrong, and I'm open to discussion.
> >
> > There's another pending issue. Arnd Bergmann has required to add a
> > property to specify the available space within the CPU address space
> > for decoding windows. This property would allow to support fully
> > dynamic mbus window allocation.
>
> I wonder if this range is implied - eg it is address space not covered
> by the memory node or any mbus ranges? Is there a situation where that
> is not sufficient?
I think it's sufficient, yes. It feels odd to have the mbus code rely
on the contents of the memory node for that, but it would work.
Arnd
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
