remove unused fapi2 multiscom function

Change-Id: Idc69f7d5ad73e33b259b1938b82196d99392be15
Reviewed-on: http://gfw160.aus.stglabs.ibm.com:8080/gerrit/24393
Tested-by: Jenkins Server
Reviewed-by: Thi N. Tran <thi@us.ibm.com>
Reviewed-by: Richard J. Knight <rjknight@us.ibm.com>
Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com>
Reviewed-on: http://gfw160.aus.stglabs.ibm.com:8080/gerrit/24670
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>

1 files changed, 0 insertions, 49 deletions

diff --git a/src/import/hwpf/fapi2/include/fapi2_hw_access.H b/src/import/hwpf/fapi2/include/fapi2_hw_access.H
index 2296f415e..06b73afce 100644
--- a/src/import/hwpf/fapi2/include/fapi2_hw_access.H
+++ b/src/import/hwpf/fapi2/include/fapi2_hw_access.H
@@ -44,10 +44,6 @@
 #include <plat_hw_access.H>
 #include <p9_ringId.H>
 
-#ifdef FAPI_SUPPORT_MULTI_SCOM
-    #include <multi_scom.H>
-#endif
-
 namespace fapi2
 {
 //--------------------------------------------------------------------------
@@ -192,51 +188,6 @@ inline ReturnCode modifyRing(const Target<K>& i_target,
                              const RingMode i_ringMode = 0);
 #endif
 
-#ifdef FAPI_SUPPORT_MULTI_SCOM
-/// @brief Performs a multiple SCOM operation
-///        This interface performs multiple SCOM operations on a chip in the
-///        order specified by the input MultiScom object.
-///        See fapiMultiScom.H for details of how to populate the MultiScom
-///        object with SCOM operations.
-///
-/// @tparam K template parameter, passed in target.
-/// @param[in]     i_target Target to operate on.
-/// @param[in,out] io_multiScomObj Reference to a MultiScom object,
-///                                pre-populated with SingleScomInfo entries
-///                                to perform multiple SCOMs on input target
-/// @return fapi2::ReturnCode. FAPI2_RC_SUCCESS if success, else error code.
-///
-/// @note   This is a synchronous interface and would return after all the
-///         SCOM operations are completed or on the first failed operation
-///
-/// @note   SCOMs will be performed in the order they were added to the
-///         input MultiScom object
-///
-/// @note   In case of errors, the platform code is responsible to collect
-///         and add all the required error info and FFDC into the error data
-///         for debugging
-///
-/// @note   If the SCOM operations added are specific to a processor chip,
-///         then the FSI Shift Engine configured in scatter-gather DMA mode
-///         extension would be used to execute the SCOM operations in a
-///         performance optimize mode. In this mode, the special
-///         SCOM_BULK_READ_MODE and SCOM_BULK_WRITE_MODE operations are
-///         supported that allow a large bulk of SCOM access (in multiple of
-///         64 bits) for targets that support auto-increment. The
-///         SCOM_WRITE_UNDER_MASK operation is not supported in this mode
-///
-/// @note   If the SCOM operations added are specific to a memory buffer
-///         chip, then the regular SCOM engine is used to execute the SCOM
-///         operations. SCOM_WRITE_UNDER_MASK operation is supported in
-///         this mode, but the special SCOM_BULK_READ_MODE and
-///         SCOM_BULK_WRITE_MODE operations are not supported due to
-///         hardware limitations.
-///
-template< TargetType K >
-fapi2::ReturnCode multiScom (const Target<K>& i_target,
-                             MultiScom&  io_multiScomObj);
-#endif
-
 // --------------------------------------------------------------------------
 // NOTE:
 // Implement platform Spy access functions if platform supports them.