diff options
author | Joe McGill <jmcgill@us.ibm.com> | 2017-04-07 08:16:05 -0500 |
---|---|---|
committer | Sachin Gupta <sgupta2m@in.ibm.com> | 2017-04-13 00:28:38 -0400 |
commit | dc47a092f6faa2cb838f0bcd046bce3cab50aa65 (patch) | |
tree | c167655eab269b422ccc0e57d03f6e375c6b718b /src/hwpf | |
parent | 1e8dfdb101ec6ceb85c6f9a1d7c9a076d0569b75 (diff) | |
download | talos-sbe-dc47a092f6faa2cb838f0bcd046bce3cab50aa65.tar.gz talos-sbe-dc47a092f6faa2cb838f0bcd046bce3cab50aa65.zip |
p9_htm_setup -- cleanup start behavior for multi-chip systems
Current code will generate an error (not propogated back to caller)
when attempting to start HTM on p1 via ADU. ADU sequence on p1 fails
based on attempting to interlock PB token manager quiesce on slave
fabric chip
A platform change is also required here to get the correct start
behavior. The i_start parameter should be set to true only for
the 'last' chip to be initialized in this istep -- this will ensure
all chips are properly configured, and the last invocation will
trigger all HTMs to begin execution.
p9_adu_coherent_utils
Issue global HTM start (pmisc) without quiesce + reinit sequence
via ADU OPTION reg. Remove TM quiesce interlock as well
p9_htm_adu_ctrl
Rework return code propogation to correctly return first error
Change-Id: Iabac85e4e0341894809464b2d206483170b79f00
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/38981
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: PPE CI <ppe-ci+hostboot@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: CHRISTINA L. GRAVES <clgraves@us.ibm.com>
Reviewed-by: Jenny Huynh <jhuynh@us.ibm.com>
Reviewed-by: Thi N. Tran <thi@us.ibm.com>
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/38983
Reviewed-by: Hostboot Team <hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Sachin Gupta <sgupta2m@in.ibm.com>
Diffstat (limited to 'src/hwpf')
0 files changed, 0 insertions, 0 deletions