summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-witherspoon
AgeCommit message (Collapse)AuthorFilesLines
2019-07-11README: Remove BB_ENV_EXTRAWHITEAdriana Kobylak1-3/+11
The step to set the BB_ENV_EXTRAWHITE variable is not needed to build a machine configuration. Removed. (From meta-ibm rev: b615fddcc52b8eb051d6a9755b16a75624f4c4ba) Change-Id: I24f3b8d3d4e83e725c5ba187ea8669f7b1cd1e7b Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-10swift-ipmi: Add in bmc fru configAndrew Geissler2-0/+120
Refactor the config yaml to be machine specific The only rule is the values in this file not conflict with the FRU_ID fields in the Swift MRW. Swift MRU has FRU_ID values that go into the 50s so just add 10 to all values in this file. (From meta-ibm rev: 89af26a2ca92f79493a652ae279a6c48a67d1f7f) Change-Id: I4a2e3ca95791d0ec2201b027894833a7ef7b4cfb Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-10swift-ipmi: Add support for non-host based configAndrew Geissler2-0/+21
The Swift MRW does a few things different here: - Renames these from gv100 to ga100 - Starts their FRU_ID at 15 - Only has 4 vs. 6 of them (From meta-ibm rev: 91a87c8b0288f235452b3073e24a5519020553e8) Change-Id: I0af55e2d0bf5e317dfae45b4e53810d3b6d8897c Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-09wspoon:pfp: Performance enhanced eventsMatthew Barth2-377/+463
With updates from openbmc/openbmc#2911, event actions are now able to be configured with groups subsets and event timers are now included in the available event triggers. Actions with group subsets allow a single event's set of triggers to run actions against a given group subset instead of the entire event groups. Also, with timers being included as a trigger, events can be configured with or without a timer instead of a disabled timer being created for events that previously did not require a timer. Tested: Generated code is functionally equivalent to previous yaml Verified fan control functionality of wspoon image (From meta-ibm rev: 1a43941fb100db7c46430f0dbbc82799276e9c13) Change-Id: Ide4167ef1a202381b702b7f6fe58b7f30501ecb3 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-28meta-ibm: Pin phosphor-fan to d9a580aa50Matthew Barth1-0/+2
This allows upstream to drop some backward-incompatible changes while the yaml in meta-ibm gets updated to the new format coming in from upstream. (From meta-ibm rev: 81ca4572471629b5114a52afb50a84d9e2cc92d1) Change-Id: Ia554f14c624d236e02d7898d2f95e7a90384dadf Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-27Put dbus monitor policies in one placeMatthew Barth13-0/+0
To better organize the policies(and the configurations) that are used by phosphor-dbus-monitor, all of them are now located under the `dbus` directory. This moves toward a more understandable and centralized scheme for the recipe(s) used to configure and build phosphor-dbus-monitor. (From meta-ibm rev: 4b80c4f2b3a62d8084fc43f95177e299d53387ae) Change-Id: Ie99c5dbe55c2295fc5cd7b5e7722cc10064e1b71 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-27swift: Add dbus monitor policy configurationsMatthew Barth7-10/+1229
Swift has two power supplies, same as Witherspoon, therefore will use the same power supply policy configuration. Swift and Witherspoon will also share the event policy configuration for OCC throttling. The thermal policy configuration will be shared between Swift and Witherspoon, but may change for air cooled Swift to not also shutdown at 3 or more cores over 115C. The fan policy configurations will be different for Swift, therefore they will be separate. At this time, there are some areas unknown on how fan presence and functional states will be handled for both air and water cooled Swift machines, so these are configured to be the same. Tested: Built witherspoon phosphor-dbus-monitor resulting in no image change Built swift phosphor-dbus-monitor resulting in correct policies (From meta-ibm rev: fd06a2cbfd5f6e43aba4887ae1398984410d52cc) Change-Id: I1125f00ecd51c23aac2da4cd2a47432ac3bc2de7 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-27Make dbus monitor policies machine specificMatthew Barth11-8/+8
Policy configurations will be loaded by machine within the system meta layer (in this case meta-witherspoon). This allows different machines to have different policies and/or different policy configurations. The .bbappend can be used to alter which policies are used on a machine. The thought here being that most machines within the same system meta layer would use the same policies. However these policies would likely have different configurations, this is where each machine would have its own policy configuration which would be loaded per the policy recipe. Tested: Built witherspoon phosphor-dbus-monitor resulting in no image change Built swift phosphor-dbus-monitor where no polices exist now (From meta-ibm rev: 6275fda44b3fd1a039f6aef55e920b542b8135ef) Change-Id: I9c86e9eb15756236e1e802f18345fb8c7ab5400a Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-27Remove `witherspoon` from recipe file namesMatthew Barth11-4/+4
Remove `witherspoon` from recipe file names, which includes the directory containing the policy configuration files. Tested: Built witherspoon phosphor-dbus-monitor resulting in no image change (From meta-ibm rev: c8562bc0066f8657d2fbb5c1962826e686a7f652) Change-Id: I7d7d247865bc2f8432e01a46caa43cc8770ae100 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-27meta-ibm: Remove phosphor-dbus-monitor native recipesMatthew Barth5-61/+0
The native recipes are no longer used after the switch to non-native recipes in the meta-phosphor layer. Tested: Built witherspoon phosphor-dbus-monitor resulting in no image change Built swift phosphor-dbus-monitor resulting in no image change (From meta-ibm rev: c50b717ce219342c4730d3f029712d5a7d10da07) Change-Id: I0026c06592921d0f1633bd3a24e6cd0530d3cc19 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-26meta-ibm: phosphor-dbus-monitor non-nativeMatthew Barth5-0/+78
Create the phosphor-dbus-monitor non-native recipes to allow the switch from native to non-native within the meta-ibm layer. Upon switching to the non-native recipe in meta-phosphor, these non-native recipes will then replace the native recipes in providing the policy configuration files(yaml). Tested: Built witherspoon phosphor-dbus-monitor resulting in no image change (From meta-ibm rev: 0ca32c6b6d0566a29756ecd05ffb748764296a27) Change-Id: Idf800c0d537b6051c3bc263908d9bbb2bc6ab2de Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-26meta-ibm: witherspoon: Add total_power sensor to chassis associationEddie James1-1/+3
This sensor is needed under the chassis association so that bmcweb can report the PowerControl/PowerConsumedWatts Redfish property. (From meta-ibm rev: bc0b221dda4f9aad8589469066d8f075b69789f0) Signed-off-by: Eddie James <eajames@linux.ibm.com> Change-Id: I9a5daf64e9888a5b7c817fab59658a054de25a83 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-26meta-ibm: witherspoon: Rename sensor associationsShawn McCarney1-80/+80
BMCWeb uses ObjectMapper associations to find sensor information for Redfish. The names of these associations have changed. Updating the Witherspoon association names to match the new naming scheme. See https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/22976 for more information on the new sensor association names. (From meta-ibm rev: 0c2b3acd905de8d8547139075ecc034f213636d9) Change-Id: Iccb0f3d4f75d8716447cc4bb488cf268374309c1 Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-22meta-ibm: acx22: Add allarch to avsbus-controlBrad Bishop1-0/+1
avsbus-control provides scripts, so set the package arch appropriately. (From meta-ibm rev: 3168dfa433d1ecda4fb41612942951d06d075157) Change-Id: Ic136d2cdf03019b69da45062057866bad75c1085 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-21meta-ibm: acx22: new YAML dependency schemeBrad Bishop10-777/+17
A prior patch added a new recipe acx22-yaml-config to provide all the YAML configuration for ACx22 systems. This patch switches the layer to that recipe by setting EXTRA_OECONF and DEPENDS as appropriate in the required bbappends. With this switch, a number of recipes and their provided YAML are now dead metadata, so remove those. (From meta-ibm rev: 3828b0070fd01e948fea02545da2bd91f96add36) Change-Id: I723320ed88cf2fb7cbc063e4f41637fc98a5787e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-19Swift: Remove pre-poweron VRM manipulationMatt Spinler7-10/+29
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-19Different PS I2C addresses for wspoon vs swiftMatt Spinler4-0/+12
Since the power supply I2C addresses are swapped between the 2 systems, there needs to be separate config files. (From meta-ibm rev: 7b91758259c860052d5f292a86a56c0d18884616) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I3eb8ec881a7e4d7887c79a53ef142ee2f948b53f Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-19swift: Move fan presence configMatthew Barth1-0/+0
Fan presence config files reside under the machine name directory within `phosphor-fan-presence-config`. Tested: Verified config.yaml picked up for witherspoon machine Verified config.yaml picked up for swift machine (From meta-ibm rev: 86142b4ce89084bf3310e3c9cbebc32a9c17afd2) Change-Id: I5b379d593394218c9149cf1648f3288b37f6f96a Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-19swift: Move fan monitor configMatthew Barth1-0/+0
Fan monitor config files reside under the machine name directory within `phosphor-fan-monitor-config`. Tested: Verified monitor.yaml picked up for witherspoon machine Verified monitor.yaml picked up for swift machine (From meta-ibm rev: 470fe1f5de23711c3348d17638e65c106f54304f) Change-Id: I87065dc923243e05b4ddbc54b0c1290617cb16f0 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-19meta-ibm: acx22: new YAML config recipeBrad Bishop8-0/+1212
YAML configuration files exist scattered throughout the OpenBMC tree and how they are used is controlled with layers dependencies of virtuals and preferred providers. Most of the time the above scheme is very difficult to comprehend. This patch continues a re-thinking of that approach towards a more centralized scheme. Specifically this patch implements a single YAML config recipe for the ACx22 systems. The logic contained in the recipe was pulled from all over the OpenBMC tree - the ability to comprehend how the different YAML files are generated and consumed should be greatly eased. A couple notable details: - Specialized tasks for doing deep YAML dictionary merges existed in the upstream recipes (-hardcoded.yaml, -config.yaml), but it was observed that simply concatenating the YAML files produced the same results, so the specialized deep merge logic was not copied here and can be deprecated upstream. - Unlike the upstream recipes, acx22-yaml-config is a target recipe and as such enables MACHINE based overrides. YAML files were copied from different locations in the tree, and run through a styling application (pyyaml dump(load(yaml))): phosphor-ipmi-fru-read-bmc-inventory-native:bmc-fru-config.yaml -> acx22-yaml-config:acx22-ipmi-fru-bmc.yaml phosphor-ipmi-fru-read-not-sent-by-host-inventory-native:fru-config-not-sent-by-host.yaml -> acx22-yaml-config:acx22-ipmi-fru-not-sent-by-host.yaml phosphor-ipmi-host:occ_sensors.hardcoded.yaml -> acx22-yaml-config:acx22-ipmi-occ-sensors.yaml phosphor-ipmi-host:hwmon_sensors.hardcoded.yaml -> acx22-yaml-config:acx22-ipmi-hwmon-sensors.yaml phosphor-ipmi-host:witherspoon_hwmon_sensors.hardcoded.yaml -> acx22-yaml-config:ac922-ipmi-extra-hwmon-sensors.yaml phosphor-ipmi-sensor-inventory-mrw-config-native:config.yaml -> acx22-yaml-config:acx22-ipmi-sensors-mrw.yaml (From meta-ibm rev: 3cb4a62140dca941e801026f447f13374cf68968) Change-Id: Id0584812bbf40c0118c8c4383d9dd67c38a45dec Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-11swift.conf: Build an ext4 imageAdriana Kobylak1-0/+2
Build an ext4 image for swift to be used in its eMMC chip. Tested: An ext4 image was built in addition to the current ubi ones. (From meta-ibm rev: 59bef037b63a73626434bfbfa22e1a53ca7133cd) Change-Id: I102b821754e2dd4998797f29bb935bd69324e8a3 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-11swif: Add power supply sensorsMatthew Barth3-2/+48
Initially configure Swift's power supply sensors as they were on Witherspoon. Keep the config files separate between systems as they will be different due to differences between the power supplies used. Tested: Built Swift image that contained the config files Built Witherspoon image that still contained the config files (From meta-ibm rev: d8d27673f1b277db83859408842619ae24606235) Change-Id: I64d893c6c5dbea0e4d4a592042b17d6bad5b4596 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-11swif: Add CP0/CP1 OCC sensorsMatthew Barth3-7/+809
Create Swift's OCC sensors initially using the same thresholds as they were on Witherspoon. Swift has 12 dimms/proc with 2 temp sensors per dimm. Also there are 2 GPUs/proc. Tested: Built image that contained the config files (From meta-ibm rev: 2bd366ab4bd4b9e085b70d46f07f5f1acdd35790) Change-Id: Ia381c561f283c4d542e0035534375fa14c493278 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-10Swift: Swap power supply I2C bus addresses.Matt Spinler2-4/+4
The top supply, PS0, is 0x68, and PS1 is 0x69. (From meta-ibm rev: c4df414e0284f1859ff1c709eb84eace6d848e87) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I4a9f38830f86b18932a918119bafaf1f5bd5d72a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-10Swift: Fix UCD90160 device pathMatt Spinler1-1/+1
More than 1 directory in the path is dependent on the I2C bus. (From meta-ibm rev: dc4b6022d75a5ed50588c71f1890f5cb7df0dcd4) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Iec2026ab941e735e684b939bca40482a7c603150 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-10Swift: run avsbus-disable.sh through dos2unixMatt Spinler1-18/+18
It had the '^M' which which prevented the BMC from running it. (From meta-ibm rev: 06b094f1a87a61da756323ce5ea3e75d6f4c709f) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I42dfc1a8d3af5c8f949003775b3076218de9035a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-10Swift: Run power-workarounds after PGOODMatt Spinler6-0/+41
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-06-05swift: Add CP1 ir35219 and ir35221 sensorsMatthew Barth4-0/+96
On processor 1 in Swift, an IR35219 is used for the VDD vrm and IR35221s are used for the VDN & VCS vrms and VIO vrm. Initially the same warn/crit configuration values as Witherspoon will be used. Tested: Built image that contained the config files (From meta-ibm rev: a296aa3c0ad4278c060c66c4ca4c1ed5913cfe06) Change-Id: I961c12469c550d36ec03bc5f249fe46019d1c5d1 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-05swift: Add CP0 ir35219 and ir35221 sensorsMatthew Barth4-0/+96
On processor 0 in Swift, an IR35219 is used for the VDD vrm and IR35221s are used for the VDN & VCS vrms and VIO vrm.. Initially the same warn/crit configuration values as Witherspoon will be used. Tested: Built image that contained the config files (From meta-ibm rev: e21e2d20610744cfbf1d96345e0781ae3a47159d) Change-Id: I94b687e77f988442e9b6a7f5583608be01a793c8 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-05swift: Add si7021a20 ambient sensorMatthew Barth2-0/+6
Swift has 3 ambient temperature sensors, the si7021a20 will be labeled as `ambient2` and initially use the same warn/crit temperature configurations as Witherspoon. Tested: Built image that contained the config file (From meta-ibm rev: 44d15151813b30aeb9f93cf4afb2818be2ed0b70) Change-Id: Ie5e538d270ab27cd1ebd4979c79038c1b18bb1db Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-05swift: Add dps310 ambient sensorMatthew Barth2-0/+6
Swift has 3 ambient temperature sensors, the dps310 will be labeled as `ambient1` and initially use the same warn/crit temperature configurations as Witherspoon. Tested: Built image that contained the config file (From meta-ibm rev: b86d99ad97152a5932f0e53a3a80a422e421437b) Change-Id: Ibd7a11b9203d6ec82b500874d6d38a3e762e4173 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-05swift: Add tmp275 ambient sensorMatthew Barth2-0/+6
Swift has 3 ambient temperature sensors, the tmp275 will be labeled as `ambient0` and initially use the same warn/crit temperature configurations as Witherspoon. Tested: Built image that contained the config file (From meta-ibm rev: 51daebff52005f4cf40fa5a4bf8c5f779bb6c997) Change-Id: Iebb780c517a41ec64e5ad99ebf41c401faab90e9 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-04Swift: Bump MRW versionMatt Spinler1-1/+1
Pick up a change that assigns types to the panel and VRM cards so gen_openpower_fru.pl can find them when looking for VPD. (From meta-ibm rev: 318efca67822aa625b6868bcb08508e7695c5bf3) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I26537326fb1fe0e653d3c7c470710c8a93cafb5e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-04witherspoon-pfault-analysis: srcrev bump 9c7897ce91..03c19db6a8Andrew Geissler1-1/+1
Brandon Wyman (7): Use YAML for UCD definitions Fill in example YAML file based on Witherspoon Update script and template to parse index and path Update to get RailNames from parsing YAML Update to get GPIConfigs from parsing YAML Update to get GPIOAnalysis from parsing YAML Add YAML and error function for MEM_GOODx faults (From meta-ibm rev: a97929f0835cb2d4106e63ca7ddc33ce72f3f7aa) Change-Id: I83a10984a83916107f864d7c54209c1f1ab4f367 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-30Swift: Fix BMC VPD pathMatt Spinler1-1/+1
Fix the EEPROM path to match what is on the real hardware. (From meta-ibm rev: 8396c6dfc1da6cfe7594e50999f947e5af9dd9c7) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ibd8fc6aae43aadbf242498ba82f3c0660121d6fa Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-30Swift: Fix syntax error in gpio_defs.jsonMatt Spinler1-1/+1
Add a missing comma. (From meta-ibm rev: 3ea8d6e97d452bd77b51e081e880b8e211211efc) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I9b9f25767b47a4f48a2653c7ba7a88cf1d4bb779 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-30meta-ibm: Swift: Add inventory config YAMLMatt Spinler4-2/+18
It will create the xyz.openbmc_project.Inventory.Item.Chassis interface on the chassis. (From meta-ibm rev: 8074814d81f5bd8b3b9467e2392f1888059ec897) Change-Id: I40c3d94bfdce7388e6c525b253d6b456b10b8604 Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-30meta-ibm: witherspoon: drop channel.yamlBrad Bishop2-9/+0
These files aren't used by ipmid anymore, so drop. See host-ipmid change 41ac50530a for details. (From meta-ibm rev: 19be7dbb08bb6c4e9a992a41972148240f955b75) Change-Id: I648cb8b7f1dba2a5a32ed1a1b05c18a15334763a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29meta-ibm: witherspoon: remove unused inventory recipesBrad Bishop2-17/+0
With the transition to target class recipes for phosphor-inventory a couple files are now dead code and can be removed. (From meta-ibm rev: 2728c26b8515a86d9c773948faa4b750e6d3e448) Change-Id: I4dc355349a7ad34e87314ea021963816f0ebe50e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29witherspoon-128: Use ${MACHINE} for device tree file nameAdriana Kobylak1-1/+1
Replace "witherspoon-128" with ${MACHINE} for the device tree file name as it's better practice to use bitbake variables instead of hard-coding values. Tested: Output of "bitbake obmc-phosphor-image -e": # pre-expansion value: # "${KMACHINE}-bmc-opp-${MACHINE}.dtb" KERNEL_DEVICETREE="aspeed-bmc-opp-witherspoon-128.dtb" (From meta-ibm rev: 8bbd213225ea5d6e3d1eb8537308f398dc85b6a2) Change-Id: I46e72947ddf47d3cbc20ab04f2b949ee717423cf Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29swift: Point to swift's kernel device treeAdriana Kobylak1-3/+1
The kernel device tree for swift has been merged upstream. Tested: Output of "bitbake obmc-phosphor-image -e": # pre-expansion value: # "${KMACHINE}-bmc-opp-${MACHINE}.dtb" KERNEL_DEVICETREE="aspeed-bmc-opp-swift.dtb" (From meta-ibm rev: b652e467727899419334e6bf8b5b63e3a4150b56) Change-Id: Ib7f4063234d1412bdbeb01044947d92c75df704e Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29YAML updates for Swift MEM_GOODx fault isolationBrandon Wyman1-2/+90
Use new memGoodError() function to analyze MEM_GOOD0 and MEM_GOOD1 faults for isolation. Add GPIOAnalysis sections to the YAML file to use the two PCA9539 devices that will be used to isolate and make the appropriate call outs. (From meta-ibm rev: bbca98df7f6d46709a840b5054f14eb0371851ad) Change-Id: Ieff5dfb9d514891f3ee3e1267256b165f69e7a08 Signed-off-by: Brandon Wyman <bjwyman@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29Recipe updates for power sequencer YAML filesBrandon Wyman4-0/+216
Add YAML file for Witherspoon power sequencer information. Add YAML file for Swift power sequencer information. Add native recipe to pull in YAML files. Update recipe to set appropriate configuration variable for YAML file to use based on machine configuration. Depends-On: I54958ce49496464e601ff9c6f2b081ee8d2c07be gerrit.openbmc-project.xyz/c/openbmc/witherspoon-pfault-analysis/+/20513 (From meta-ibm rev: b5b193f18604177387d7ad0fd196415cd9098f51) Change-Id: I415f8226f23098b4e4af0a7dc1e9374c9699a327 Signed-off-by: Brandon Wyman <bjwyman@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-28meta-ibm: witherspoon: inventory: target class recipesBrad Bishop2-0/+20
In the near future meta-phosphor will switch phosphor-inventory-manager over to target class configuration recipes in place of native class configuration recipes. Configuration recipes populate the /usr/share/phosphor-inventory filesystem with the YAML configuration that the phosphor-inventory-manager build process expects. Those are preferable to native class config recipes because native recipes cannot be overridden based on MACHINE. Add a target class recipe for inventory-cleanup so meta-ibm is ready when meta-phosphor makes the cut-over. (From meta-ibm rev: 0105129e023c3e310b264a607eaeff41a8ed7ed7) Change-Id: I58f4a11bf8fb9d7f47ecdd4f73f83581ef507779 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-23swift: Increase read-write volume to 32MBAdriana Kobylak1-0/+5
Swift will be using UBI for its filesystem. Since it has 128MB flash chips, increase the size of the read-write volume to 32MB, same as witherspoon-128. (From meta-ibm rev: af07bab16662383dbf01ed4b7fae5083e66ae357) Change-Id: I631c69791e67f29903ae1e2377fc4414f33a0317 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-22meta-ibm: witherspoon: fans: drop unused variableBrad Bishop1-1/+0
meta-phosphor dropped support for native class config recipes and uses target class config recipes by default. Drop the reference to PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT as it is no longer used in meta-phosphor. (From meta-ibm rev: bed9adaf6d89aa2ac42b91c06e4ee4be4e17c40e) Change-Id: I3cd896636924a59ecebd0eb25cad261f1bc070ab Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-21meta-ibm: witherspoon: fans: switch to non-nativeBrad Bishop25-9/+10
meta-phosphor recently enabled target class config recipes. Those are preferable to native class config recipes because native recipes cannot be overridden based on MACHINE, so switch to target class config recipes. Switching to target class recipes consists of temporarily setting PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT to 0, overriding the phosphor distro default of 1. After all OpenBMC BSP layers have moved to target class config recipes PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT can be removed from meta-phosphor and any BSP layers. Any references to -native recipes are replaced with their target class counterparts. Any -native bbappends are re-worked to apply to their target class counterparts. Finally, use BPN instead of PN when setting FILESEXTRAPATHS, to avoid unfortunate directory hierarchies if these bbappends are copy/pasted and then used to bbappend a native recipe. Since this patch moves to target class recipes, this is a noop; however, this avoids unfortunate directory hierarchies with native bbappends such as: meta-base/recipes-foo/bar/baz-native.bb meta-base/recipes-foo/bar/baz/a-file meta-append/recipes-foo/bar/baz-native.bbappend meta-append/recipes-foo/bar/baz-native/b-file Using "${THISDIR}/${BPN}:" enables a more sensible hierarchy: meta-base/recipes-foo/bar/baz-native.bb meta-base/recipes-foo/bar/baz/a-file meta-append/recipes-foo/bar/baz-native.bbappend meta-append/recipes-foo/bar/baz/b-file This behavior occurs because By default FILESPATH is set in base.bbclass (in OE-Core) to look for files in ${BP}, ${BPN} and files (and a number of subdirectories of those based on ${FILESOVERRIDES}). (From meta-ibm rev: 6587e6ca03ca50411bc11cf87b5e11971dfe343f) Change-Id: Ib2c3f0052c1e01a84416da2eb868a54d8810e750 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-15swift: Add BMC riser EEPROMAnthony Wilson1-1/+6
Added the BMC riser EEPROM for swift. (From meta-ibm rev: 2203c6935c10a4cabff80b5d17e9e10e0c007910) Signed-off-by: Anthony Wilson <wilsonan@us.ibm.com> Change-Id: Id401da931e8ffbcf4d44151605d969e34af73276 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-15Add EXTRA_IFACES to power supply configurationsAnthony Wilson3-0/+3
Adding support for multiple interface associtions for inventory items. Testing: Verifed that the interface was associated properly. (From meta-ibm rev: d77ba6c270497a25c0eff607741bed9bac7a8a4c) Signed-off-by: Anthony Wilson <wilsonan@us.ibm.com> Change-Id: Ia3d83b58681f1ebf7befef1eb3f65f19fb8dc03a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-14meta-ibm: witherspoon: fix file search pathsBrad Bishop5-5/+5
Typically it does not make any sense to append to FILESEXTRAPATHS. FILESEXTRAPATHS is set in a bbappend when overriding something from another layer. The typical desire will be to make bitbake search for files in the layer with the bbappend and not some other layer earlier in the priority list. Further, appending to FILESEXTRAPATHS will introduce unexpected behavior when multiple layers append the same recipe - layers with higher layer priorities that append to FILESEXTRAPATHS will find their files overriden by files in layers with lower priorities. (From meta-ibm rev: a588016cb556b425a00286ace2c8324590aac98b) Change-Id: I7672219fdab5e2c9cc03423d7f507ef2e6a842c2 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-08-27 02:45:57 +0300