summaryrefslogtreecommitdiffstats
path: root/env.bash
diff options
context:
space:
mode:
authorTsung Yeung <tyeung@us.ibm.com>2019-03-19 09:21:53 -0400
committerChristian R. Geddes <crgeddes@us.ibm.com>2019-04-05 11:00:01 -0500
commit40bcbd0f3a78e74a6c23c050f7cef854cc2c283a (patch)
tree166cfea87d64fb2f4121cd6ccaa1c2ff269d86d6 /env.bash
parentb047a25de8a66b6795f026bfb1fdb6caae0ba594 (diff)
downloadtalos-hostboot-40bcbd0f3a78e74a6c23c050f7cef854cc2c283a.tar.gz
talos-hostboot-40bcbd0f3a78e74a6c23c050f7cef854cc2c283a.zip
Enable median rank wr_vref value on NVDIMM
- The NVDIMM restore procedure is required to restore the wr vref values. The current method is to latch in the per-dram wr vref value with PDA. However, this requires multiple CCS sequences due to hardware limitation and would break refresh timing between sequences, introduce possible UEs. To get around this, we will use the median value of all the drams per rank-pair instead of per-dram value. Previous attempt was to use average value but after the speaking with Stephen G. median value is a better approach due to the possibility that bad vref value from failing dram - Added NVDIMM-specifc CCS execute procedure Change-Id: Ie7d1e063c423a4374ca22422395ee5524d70a124 CQ:SW459457 Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/74753 Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Louis Stermole <stermole@us.ibm.com> Reviewed-by: STEPHEN GLANCY <sglancy@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com> Tested-by: HWSV CI <hwsv-ci+hostboot@us.ibm.com> Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com> Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/74790 Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Diffstat (limited to 'env.bash')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud