powerpc/powernv: Don't map M64 segments using M32DT
authorGavin Shan <gwshan@linux.vnet.ibm.com>
Fri, 27 Mar 2015 00:29:00 +0000 (11:29 +1100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 6 May 2015 20:01:57 +0000 (22:01 +0200)
commit4bbea4fee4f957f524167501a419753e887e1479
treecacec1a38cc89b37898646df3103c85cc84bb759
parent709bff6be04a8308b940d7af4fbc24c0accda8fc
powerpc/powernv: Don't map M64 segments using M32DT

commit 027fa02f84e851e21daffdf8900d6117071890f8 upstream.

If M64 has been supported, the prefetchable 64-bits memory resources
shouldn't be mapped to the corresponding PE# via M32DT. Unfortunately,
we're doing that in pnv_ioda_setup_pe_seg() wrongly. The issue was
introduced by commit 262af55 ("powerpc/powernv: Enable M64 aperatus
for PHB3"). The patch fixes the issue by simply skipping M64 resources
when updating to M32DT.

Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/powerpc/platforms/powernv/pci-ioda.c