BMC/tmp/openbmc.git/meta-ibm, branch warrior

meta-ibm: Pin phosphor-fan to d9a580aa50

2019-06-28T18:17:09+00:00

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 Signed-off-by: Brad Bishop

Put dbus monitor policies in one place

2019-06-27T20:22:43+00:00

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 Signed-off-by: Brad Bishop

swift: Add dbus monitor policy configurations

2019-06-27T20:22:43+00:00

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 Signed-off-by: Brad Bishop

Make dbus monitor policies machine specific

2019-06-27T20:22:42+00:00

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 Signed-off-by: Brad Bishop

Remove `witherspoon` from recipe file names

2019-06-27T20:22:42+00:00

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 Signed-off-by: Brad Bishop

meta-ibm: Remove phosphor-dbus-monitor native recipes

2019-06-27T20:22:42+00:00

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 Signed-off-by: Brad Bishop

meta-ibm: phosphor-dbus-monitor non-native

2019-06-26T20:57:56+00:00

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 Signed-off-by: Brad Bishop

meta-ibm: witherspoon: Add total_power sensor to chassis association

2019-06-26T20:57:56+00:00

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 Change-Id: I9a5daf64e9888a5b7c817fab59658a054de25a83 Signed-off-by: Brad Bishop

meta-ibm: witherspoon: Rename sensor associations

2019-06-26T14:04:22+00:00

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 Signed-off-by: Brad Bishop

meta-ibm: acx22: Add allarch to avsbus-control

2019-06-21T22:07:52+00:00

avsbus-control provides scripts, so set the package arch appropriately. (From meta-ibm rev: 3168dfa433d1ecda4fb41612942951d06d075157) Change-Id: Ic136d2cdf03019b69da45062057866bad75c1085 Signed-off-by: Brad Bishop