From b445b93fc21ee80515090087e063fd74b8d508a3 Mon Sep 17 00:00:00 2001 From: Matthew Raybuck Date: Thu, 28 Mar 2019 10:41:20 -0500 Subject: Handle bad PEC from UCD device op The current UCD code doesn't have any error handling for a bad PEC byte instead it is just ignored. This will add the necessary error handling to the retry code for bad PEC bytes. Change-Id: I8d9960a203b5864812bcaa0019087bb3dcff0c53 RTC:205982 Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/75174 Reviewed-by: Michael Baiocchi Tested-by: Jenkins Server Tested-by: Jenkins OP Build CI Tested-by: FSP CI Jenkins Tested-by: Jenkins OP HW Reviewed-by: Nicholas E. Bofferding --- src/include/usr/i2c/i2creasoncodes.H | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/include/usr/i2c') diff --git a/src/include/usr/i2c/i2creasoncodes.H b/src/include/usr/i2c/i2creasoncodes.H index 6e29065db..a2b79be32 100644 --- a/src/include/usr/i2c/i2creasoncodes.H +++ b/src/include/usr/i2c/i2creasoncodes.H @@ -66,9 +66,9 @@ enum i2cModuleId READ_I2C_ATTRIBUTES = 0x10, I2C_ACCESS_MUX = 0x11, I2C_GENERIC_PRES_DETECT = 0x12, + I2C_BAD_PEC_BYTE_ERROR = 0x13, }; - /** * @enum i2cReasonCode * @@ -106,6 +106,7 @@ enum i2cReasonCode I2C_INVALID_BLOCK_WRITE_LENGTH = I2C_COMP_ID | 0x1A, // Invalid block write length I2C_INVALID_READ_BYTE_OR_WORD_LENGTH = I2C_COMP_ID | 0x1B, // Invalid read byte/word length I2C_INVALID_BLOCK_READ_LENGTH = I2C_COMP_ID | 0x1C, // Invalid block read length + I2C_BAD_PEC_BYTE = I2C_COMP_ID | 0x1D, // Bad PEC byte }; -- cgit v1.2.3