On Wed, 21 Aug 2013 17:39:48 +0200, Tomasz Figa <t.figa@xxxxxxxxxxx> wrote: > On Tuesday 20 of August 2013 10:35:51 Stephen Warren wrote: > > >> a) Adjust memory.txt to allow multiple entries in memory-regions, and > > >> add an associated memory-region-names property. > > >> > > I don't believe that's a good approach unless you have at least a > > partial idea of how the current bindings will be extended to support > > multiple memory regions. > > I believe that at least three "at least partial" ideas have been brought in > this thread. Moreover, I don't think that defining the simple binding now > would stop us from extending it according to any of those ideas in any way. I would plan on extending later with suggestion 'a)' above. Making the memory-region an array of phandles is a better match with how most of the core bindings work. I actually regret the *-gpio properties that were defined earlier becasue it makes it harder for software to look at a tree and determine if there are any gpio references. It of course doesn't need to be done immediately, only when it becomes required. g. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
