Hi Rob,
On Thu, Feb 11, 2016 at 9:02 PM, Robert Richter
wrote:
> On 11.02.16 08:50:41, Rob Herring wrote:
>> On Tue, Feb 2, 2016 at 4:09 AM, Ganapatrao Kulkarni
>> wrote:
>> > dt node parsing for numa topology is done using device property
>> > numa-node-id and device node distance-map.
>>
>> Ho
On 11.02.16 08:50:41, Rob Herring wrote:
> On Tue, Feb 2, 2016 at 4:09 AM, Ganapatrao Kulkarni
> wrote:
> > dt node parsing for numa topology is done using device property
> > numa-node-id and device node distance-map.
>
> How is it that powerpc doesn't need flat DT parsing for NUMA? Both
> arche
On Tue, Feb 2, 2016 at 4:09 AM, Ganapatrao Kulkarni
wrote:
> dt node parsing for numa topology is done using device property
> numa-node-id and device node distance-map.
How is it that powerpc doesn't need flat DT parsing for NUMA? Both
arches are memblock based and the binding is similar IIRC, s
Hi Rob,
On Wed, Feb 3, 2016 at 5:04 AM, Rob Herring wrote:
> On Tue, Feb 02, 2016 at 03:39:18PM +0530, Ganapatrao Kulkarni wrote:
>> dt node parsing for numa topology is done using device property
>> numa-node-id and device node distance-map.
>>
>> Reviewed-by: Robert Richter
>> Signed-off-by: G
On Tue, Feb 02, 2016 at 03:39:18PM +0530, Ganapatrao Kulkarni wrote:
> dt node parsing for numa topology is done using device property
> numa-node-id and device node distance-map.
>
> Reviewed-by: Robert Richter
> Signed-off-by: Ganapatrao Kulkarni
> ---
> drivers/of/Kconfig | 11 +++
> driv
dt node parsing for numa topology is done using device property
numa-node-id and device node distance-map.
Reviewed-by: Robert Richter
Signed-off-by: Ganapatrao Kulkarni
---
drivers/of/Kconfig | 11 +++
drivers/of/Makefile | 1 +
drivers/of/of_numa.c | 207
