Fix to not send a NVDIMM protection state change to OPAL

There is a firmware request call, within the notifyNvdimmProtectionChange
method, that needs to be guarded such that the message is NOT
sent to OPAL.

A guard has been placed in the call so the notification is only
sent to PHYP and not OPAL.

Change-Id: Ib17dd8f3bb20d4d40bf163760da4b4b3c835ff70
CQ:SW471511
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/81976
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Matt Derksen <mderkse1@us.ibm.com>
Reviewed-by: Daniel M Crowell <dcrowell@us.ibm.com>

src/usr/isteps/nvdimm/nvdimm.C

@@ -3112,6 +3112,12 @@ errlHndl_t notifyNvdimmProtectionChange(Target* i_target,
 
 #ifdef __HOSTBOOT_RUNTIME
 
+        // Don't send message to OPAL
+        if (TARGETING::is_sapphire_load())
+        {
+            break;
+        }
+
         // Send combined status to phyp
         // Get the Proc Chip Id
         RT_TARG::rtChipId_t l_chipId = 0;
@@ -3187,7 +3193,6 @@ errlHndl_t notifyNvdimmProtectionChange(Target* i_target,
                                         &l_req_fw_msg,
                                         &l_resp_fw_msg_size,
                                         &l_resp_fw_msg);
-
 #endif
 
     } while (0);