From cd754bf0b11117790f5d926844f7a8b7f595230d Mon Sep 17 00:00:00 2001 From: Christian Geddes Date: Fri, 2 Nov 2018 16:39:35 -0500 Subject: Route scom operations on OCMB chips to fapi2 mmio scom interface After we get OMI targets trained we can communicate with the OCMB chips via MMIO. This includes reading and writing scom registers on the OCMB chip. This commit hooks up all of the plumming so when a HWP calls fapi2::getScom/putScom on an OCMB chip hostboot will be able to determine what functions to call to perform the operation. Change-Id: I3ae6f8b4ad3128f61d886b1fdfbeea82b0c6e76e RTC: 196806 Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/68353 Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: Jenkins OP HW Tested-by: FSP CI Jenkins Reviewed-by: Ilya Smirnov Reviewed-by: Matt Derksen Reviewed-by: Daniel M. Crowell --- src/include/usr/expscom/expscom_reasoncodes.H | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/include/usr/expscom') diff --git a/src/include/usr/expscom/expscom_reasoncodes.H b/src/include/usr/expscom/expscom_reasoncodes.H index 62713531c..9eb7ebc29 100644 --- a/src/include/usr/expscom/expscom_reasoncodes.H +++ b/src/include/usr/expscom/expscom_reasoncodes.H @@ -31,8 +31,8 @@ namespace EXPSCOM { enum EXPSCOMModuleId { - MOD_OCMBSCOM_INVALID = 0x00, // Zero is an invalid module id - MOD_I2CSCOM_PERFORM_OP = 0x01, // i2cscom.C : i2cScomPerformOp + MOD_OCMBSCOM_INVALID = 0x00, // Zero is an invalid module id + MOD_OCMB_UTILS = 0x01, // expscom_utils.C }; enum EXPSCOMReasonCode -- cgit v1.2.3