powerpc/powernv: Don't warn on PE init if unfreeze is unsupported
authorRussell Currey <ruscur@russell.cc>
Wed, 16 Nov 2016 01:12:26 +0000 (12:12 +1100)
committerMichael Ellerman <mpe@ellerman.id.au>
Tue, 22 Nov 2016 00:57:07 +0000 (11:57 +1100)
commitd4791db527bf397c84c9956c3ece9692ed5322ac
treebd1eda3a9bd325ae5f09dea37e98a501103f6830
parente9eb0278dad9c7a2631d5432180a130710110c09
powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is
called.  This is to remove any existing freeze, and has no negative side
effects if the PE is already in an unfrozen state.  On PHB backends that
don't support this operation and return OPAL_UNSUPPORTED, this creates a
scary and misleading warning message.

Skip the warning message on init if OPAL_UNSUPPORTED is returned.

As far as I'm aware, this currently only affects NPUs.

Fixes: 313483d ("powerpc/powernv: Unfreeze PE on allocation")
Signed-off-by: Russell Currey <ruscur@russell.cc>
Acked-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Reviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/platforms/powernv/pci-ioda.c