summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-witherspoon/recipes-phosphor/chassis/avsbus-control/witherspoon
AgeCommit message (Collapse)AuthorFilesLines
2020-04-27meta-ibm: move all meta-witherspoon metadataBrad Bishop4-69/+0
The metadata common to all IBM systems is confusingly split between meta-ibm and meta-witherspoon. Move everything to meta-ibm. The meta-ibm README is re-written to more accurately reflect the scope of the layer. Allow the configuration samples (bblayers.conf.sample, local.conf.sample) to be sourced from either meta-ibm or meta-witherspoon until such a time that any workflows and tooling have had the opportunity to move to meta-ibm. (From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442) Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-08-06Swift: Put in avsbus-enableMatt Spinler1-0/+15
As on Witherspoon, some VRMs on Swift need their AVS buses enabled as part of the power on sequence. The AVS bus connects those VRMs to the processors so the processors can set voltages. On Witherspoon, the sequence was 1. Disable the AVS bus 2. Manually set VRM voltages 3. Enable AVS bus Currently on Swift there is no need to manually set voltages, so the AVS bus disable service and script isn't required. Tested: Tested on swift, and ensured both witherspoon and witherspoon-128 still have all avs scripts and services installed. (From meta-ibm rev: f1ceece0b75a4522ef3089319b12d22fd83ed9ef) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ifd7ebdd5ec3dcdfef97c04e666d83fcb4991b452 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-19Swift: Remove pre-poweron VRM manipulationMatt Spinler2-150/+0
Swift doesn't need to run the vrm-control.sh script to set VRM voltages, which also means it doesn't need to disable/enable their AVS buses around it, nor bind/unbind the VRM device drivers. Remove all of these services, and also create a new recipe for power-workarounds.sh that was in the avsbus-control recipe so that it can remain. (From meta-ibm rev: 65ced2221d38ce08dd7dcc46ec254b1bdd4a714f) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ib64cc45499292ae84689fb11400ff9ff0f5f5942 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-10Swift: Run power-workarounds after PGOODMatt Spinler2-0/+32
On swift, the VRMs that power-workarounds.sh touches can't communicate until the system has been powered on. Rearrange the services to make this happen. (From meta-ibm rev: b5980e57561bc2f161bd61965551c1a3e1323131) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I0ac7fb6adaa0de18feb525259f991e99c147e244 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-10meta-ibm: avsbus-control: Create machine-specific structureAdriana Kobylak3-0/+172
Yocto automatically adds files/<MACHINE>/ to the file path, take advantage of this feature to simplify the recipe and directory structure. Tested: Built witherspoon, witherspoon-128, and swift, and verified they all had the correct avsbus-control script in their image. (From meta-ibm rev: cd6c8359c35986169e3225f853e38fabb7aade1b) Change-Id: Id4051ebceef1bee6898d8637381970ba31dc9508 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>