Fixed periodic cal bug causing data fails

A quarter-cycle adjustment signal (blue waterfall) in the PHY
was updating erroneously when periodic cal was being run. This
update sets a bit that disables the blue waterfall from updating.

Change-Id: I82d2ee89f8e0b1628d1640e10a89f39ad353fb1d
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/35170
Reviewed-by: JACOB L. HARVEY <jlharvey@us.ibm.com>
Reviewed-by: Louis Stermole <stermole@us.ibm.com>
Reviewed-by: Brian R. Silver <bsilver@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com>
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/35185
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>

src/import/chips/p9/procedures/hwp/memory/lib/workarounds/dp16_workarounds.C

@@ -105,7 +105,9 @@ fapi_try_exit:
 fapi2::ReturnCode rd_dia_config5( const fapi2::Target<fapi2::TARGET_TYPE_MCA>& i_target )
 {
     // Config provided by S. Wyatt 8/16
-    constexpr uint64_t rd_dia_config = 0x0010;
+    // 8 corresponds to bit 52 and is a workaround for periodic calibration related fails.
+    // Currently, it looks like this workaround will be required for all versions of Nimbus, so just hard coding it
+    constexpr uint64_t rd_dia_config = 0x0810;
 
     // Not checking fo EC level as this isn't an EC feature workaround, it's a incorrect documentation workaround.
     static const std::vector<uint64_t> l_addrs =