npu2-opencapi: Fix 'link internal error' FIR, take 2
npu2-opencapi: Fix 'link internal error' FIR, take 2

When setting up an opencapi link, we set the transport muxes first,
then set the PHY training config register, which includes disabling
nvlink mode for the bricks. That's the order of the init sequence, as
found in the NPU workbook.

In reality, doing so works, but it raises 2 FIR bits in the PowerBus
OLL FIR Register for the 2 links when we configure the transport
muxes. Presumably because nvlink is not disabled yet and we are
configuring the transport muxes for opencapi.

bit 60: link0 internal error
bit 61: link1 internal error

Overall the current setup ends up being correct and everything works,
but we raise 2 FIR bits.

So tweak the order of operations to disable nvlink before configuring
the transport muxes. Incidentally, this is what the scripts from the
opencapi enablement team were doing all along.

Signed-off-by: Frederic Barrat <c90240987c583ac0802fbeb88cb1684edc683e18@linux.vnet.ibm.com>
Acked-by: Andrew Donnellan <efc2d7c347a094a6ec1d918179e819039044c564@au1.ibm.com>
Signed-off-by: Stewart Smith <ec31ab75ddf977353c8f660f92ea8b23f64aef25@linux.ibm.com>

shenki/skiboot,open-power/skiboot,qemu/skiboot,open-power/skiboot,qemu/skiboot,legoater/skiboot,shenki/skiboot,shenki/skiboot,shenki/skiboot,stewart-ibm/skiboot,legoater/skiboot,stewart-ibm/skiboot,legoater/skiboot,open-power/skiboot,legoater/skiboot,qemu/skiboot,qemu/skiboot,open-power/skiboot,legoater/skiboot,shenki/skiboot,stewart-ibm/skiboot,open-power/skiboot,qemu/skiboot