summaryrefslogtreecommitdiffstats
path: root/meta-openbmc-machines/meta-openpower/common/recipes-phosphor/packagegroups/packagegroup-obmc-apps.bbappend
diff options
context:
space:
mode:
authorXo Wang <xow@google.com>2017-02-15 17:10:15 -0800
committerPatrick Williams <patrick@stwcx.xyz>2017-02-20 13:37:30 +0000
commitc5fa8eee8fa917bb861a830cc08b176bdff3cbcc (patch)
tree024ebb787706eba1061c396095ba63898e9e285e /meta-openbmc-machines/meta-openpower/common/recipes-phosphor/packagegroups/packagegroup-obmc-apps.bbappend
parent3b9ab4b5754b0f7fd61fb79da38774209a916c3c (diff)
downloadtalos-openbmc-c5fa8eee8fa917bb861a830cc08b176bdff3cbcc.tar.gz
talos-openbmc-c5fa8eee8fa917bb861a830cc08b176bdff3cbcc.zip
meta-zaius: avsbus-control: Raise VDN rails max voltage
Testing showed that the VDN max voltage setting is capping the VCS rail setpoints when those setpoints are written by the host over AVSbus. Raise VRMs' upper limit for voltage on the VDN rails to a value that does not interfere with VCS rail voltages. This is a hacky workaround for what is possibly a logic error with the VRMs' firmware and will be rolled back when the root cause is discovered and corrected. Signed-off-by: Xo Wang <xow@google.com> Change-Id: I85fd94f77509bc51aa7909dd7f522163666040fb
Diffstat (limited to 'meta-openbmc-machines/meta-openpower/common/recipes-phosphor/packagegroups/packagegroup-obmc-apps.bbappend')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud