On Thu, Sep 20, 2018 at 05:26:42AM -0700, Kumar Gala wrote: > > > On Sep 19, 2018, at 6:30 PM, David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > > On Wed, Sep 19, 2018 at 05:15:35PM -0700, Kumar Gala wrote: > >> How is the length element expected to be used w/ranges. If a child > >> has a reg outside of the length is it not translated via the range? > > > > Yes. > > > >> What if the reg size of a child node overlaps the length? Do we > >> translate up to the point the length specifies? > > > > I believe so, yes. > > > >> If #size-cells of the node is 0, does that mean no length element? > > > > I think so, yes, although I don't think I've ever seen a 'ranges' > > property on a #size-cells = 0 node. > > If we update the spec, we should clarify these things for ranges. Sounds sensible. Note that the first two properties there are kind of obvious if you think about what ranges generally means in the context of a bus bridge. The bus bridge usually doesn't know anything in particular about the child devices, it just decodes certain address ranges on the parent bus and forwards the bus cycles on them to a window in the child bus address space. -- 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
Attachment:
signature.asc
Description: PGP signature
