On Tue, 11 Feb 2014 21:04:21 +0100, Tomasz Figa [off-list ref] wrote:

On 11.02.2014 21:02, Benjamin Herrenschmidt wrote:

quoted

On Tue, 2014-02-11 at 19:01 +0000, Grant Likely wrote:

quoted

quoted

except that the former IMHO better suits the definition of memory
region, which I see as a single contiguous range of memory and can be
simplified to have a single reg entry per region.

My point is rather if multiple reg tuples are found in a reserved memory
node, the kernel must respect them and reserve the memory. I'm not
arguing about whether or not that makes for a good binding.

agreed.

My point is why, if the binding defines that just a single tuple should 
be provided.

It's irrelevant because it gets processed at a different level. It's
important that the core early setup code can quickly parse all the
reserved regions without having any idea what the end-user binding is.
Multiple reg tuples is just fine in this regard.

Whether or not multiple tuples makes sense is defined for each
particular use case by the driver actually using it without impacting
core initialization code one iota.

g.