]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
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)
committerSasha Levin <sasha.levin@oracle.com>
Sun, 17 May 2015 23:12:13 +0000 (19:12 -0400)
commit945818207f50087eef7909ab56fd316a27c9d349
tree81cea6a5f1ffdcb6a18a0eed3ae4489e6385908e
parent132a0d3a3c998e6781b9571afc19d467af28ed2b
powerpc/powernv: Don't map M64 segments using M32DT

[ Upstream commit 027fa02f84e851e21daffdf8900d6117071890f8 ]

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.

Cc: <stable@vger.kernel.org> # v3.17+
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
arch/powerpc/platforms/powernv/pci-ioda.c