From mboxrd@z Thu Jan  1 00:00:00 1970
From: tomasz.figa@gmail.com (Tomasz Figa)
Date: Tue, 11 Feb 2014 21:04:21 +0100
Subject: [PATCH v2 1/5] drivers: of: add initialization code for reserved
 memory
In-Reply-To: <1392148971.3835.15.camel@pasglop>
References: <1391515773-6112-1-git-send-email-m.szyprowski@samsung.com>	 <
 1391515773-6112-2-git-send-email-m.szyprowski@samsung.com>	 <20140205110538.
 99E47C40A89@trevor.secretlab.ca>	 <52FA0D6E.9090304@samsung.com>	 <
 20140211121316.24032C40C4D@trevor.secretlab.ca>	 <52FA33E2.4050004@samsung.
 com>	 <20140211190104.7E6C5C4140E@trevor.secretlab.ca>
 <1392148971.3835.15.camel@pasglop>
Message-ID: <52FA8245.5050707@gmail.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org



On 11.02.2014 21:02, Benjamin Herrenschmidt wrote:
> On Tue, 2014-02-11 at 19:01 +0000, Grant Likely wrote:
>
>>> 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.

Best regards,
Tomasz