Secure Boot: Dynamically set TPM I2C master path in MRW parser

Historically the TPM target as described in the MRW passes directly through to
the Hostboot targeting model without modification (other than filtering out
unwanted attributes).  This approach does not work in multi-TPM or multi-node
systems since the TPM object's I2C master path gets cloned within and across
nodes.  Instead, for multi-node systems, the MRW parser must now walk the I2C
bus connections between each TPM and the chip driving it, and dynamically
compute/set the TPM's I2C master path.  This behavior only activates for
multi-TPM systems due to limitations in other workbooks, as in these cases, the
pre-existing behavior sufficies.

Change-Id: I5845760a390841d083dc0bbe633bc19a90ab23e6
RTC: 184515
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/55240
CI-Ready: Nicholas E. Bofferding <bofferdn@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Santosh S. Puranik <santosh.puranik@in.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: ILYA SMIRNOV <ismirno@us.ibm.com>
Reviewed-by: Marshall J. Wilks <mjwilks@us.ibm.com>
Reviewed-by: Michael Baiocchi <mbaiocch@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>

0 files changed, 0 insertions, 0 deletions