Don't reset/setup I2C master 0 as SBE owns it

  Hostboot shouldn't be messing with I2C master 0 as the
  SBE is actively using it.  Reseting or setting it up
  will cause SBE I2C errors the next time it accesses it

Change-Id: I12b16d158a18b09dadff1de4534f3ea986a532a6
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/36569
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Reviewed-by: Michael Baiocchi <mbaiocch@us.ibm.com>
Reviewed-by: Corey V. Swenson <cswenson@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>

src/usr/i2c/i2c.C

@@ -3228,6 +3228,14 @@ errlHndl_t i2cProcessActiveMasters ( i2cProcessType      i_processType,
                     continue;
                 }
 
+                // Never touch engine 0 for Host -- the SBE owns
+                // it
+                if ( ( engine == 0 ) &&
+                     (io_args.switches.useHostI2C == 1) )
+                {
+                    continue;
+                }
+
                 // Look for any device on this engine based on speed_array
                 bool skip = true;
                 for ( size_t j = 0; j < I2C_BUS_ATTR_MAX_PORT; j++ )