Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
The fan control service has a dependency on the max31785 hwmon service
being started where the i2c address of the max31785 is in the name of
the service file. That i2c address is different between witherspoon and
tacoma, so a systemd substitution is needed to place the correct address
based on machine into the fan control service file.
Tested:
Built witherspoon and verified correct i2c address substituted
Built tacoma and verified correct i2c address substituted
Built mihawk and verified base fan control service used(no max31785)
Built swift to verify base fan control service used(max31785)
Verified witherspoon image on hardware
(From meta-ibm rev: 7b56fea6e2180ca110d49868b3ad543f9a5e4e76)
Change-Id: Ie0e43fb18f9349135ad66f40993a9fad662224ea
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add the phosphor-fan-control-init service back in to trigger the
obmc-fan-control-ready target which is used to start
phosphor-fan-monitor. It was not realized that this target was set
within the fan control application's init mode.
Tested:
Built witherspoon image containing phosphor-fan-control-init service
Service is started at poweron and sets obmc-fan-control-ready target
Fan monitor service now starts
(From meta-ibm rev: dc97a9316915d3adc5a31846b76e6a3c2f6cab8e)
Change-Id: Ic0124fec814a6d1588c5dc47e5e16ab8529248bf
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Set the configuration file to phosphor-cooling-type to set all
witherspoon tacomas to be air cooled only.
Tested:
Removed DEVICE & CODE on witherspoon config to see always be set to
air cooled
Updated config on witherspoon tacoma and restarted service to see
always be set to air cooled
(From meta-ibm rev: 373d3485c500ee8d3d07f2f68d0fec896856c374)
Change-Id: I1bf483da9580c4fd4b833da5840a0a98e691a811
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Fan control must support NVMe SSD thermal sensor.
Tested: Fan speed is automatically controlled when using NVMe SSD
(From meta-ibm rev: 4dc75c91139e71ee5f42ba27ddacf46815c8aa8b)
Change-Id: Idb156ebe12d98b26faa7781b462e11b38af5ae7c
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Enable the use of JSON and install the fan presence JSON config file
into the witherspoon image. The other fan applications will continue to
use their respective YAML build time config file(s).
Tested:
Built witherspoon image, uses JSON config
Built mihawk image, continues to use YAML
(From meta-ibm rev: a6817ca6ca8c87a10eb325835ba4db59109f6101)
Change-Id: I1b675e8a3b064b04007d7474d12e5d5ad2094dad
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
JSON config file representing the same configuration that is given as
YAML at build time.
(From meta-ibm rev: 7e31e7a23d51757132e4d74873a16c65f2a1400b)
Change-Id: I8cb2697d93d402bb66f5967cba913e071a16f6b7
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Although 6 fanx_1 pwm targets are deleted, but fan0_1 fan1_1 and fan2_1
will have a default value that causes the issue to remain unresolved.
In this way, two Fans control the same pwm, but I think that our
current fan control event is controlled at the same time, so it does
not affect the fan control.
(From meta-ibm rev: c4ec0f10a091fe74f075d2033fe055b5bbd7d498)
Change-Id: I42647c92ffe5e20430cee28de6fd26e2716153d9
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Fan speed can be increased when occ or ambient is abnormal, so add the
monitor of the ambient and OCC control services.
(From meta-ibm rev: d0a123bdd618570e585a4020593bf9b13395398d)
Change-Id: I17eb679760c2e6f6002f5ea54f7d799f1c62680c
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
According to our thermal team test report, we need to adjust the fan
control event.
Tested
Fan speed will be based on new fan control events.
(From meta-ibm rev: f242630e5a8195eeef089f01537b9be4fde000a2)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: Ib4c296f128d625e78387cead26c46c76faa39535
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add actions to adjust the fan floor speed table used based on the
thermal mode of the system. In addition to adjusting the fan floor speed
table, in some modes the default fan floor required adjustment as well.
These fan floor speed values and the corresponding default fan floor
speed per mode were provided by the thermal characterization team.
Tested:
Generated code from these events
(From meta-ibm rev: 0c6a7b5a5aadcbabd7bf5d25cd102fd228e26f42)
Change-Id: Ic2bfca05979cb41489fcf123f1779d2d5f089e7c
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add the additional thermal modes needed to handle adjusting the fan
floor speeds necessary to support some hot pci cards.
(From meta-ibm rev: 149bc55f4f7a9dbe035c5868aa5fd738e5837a9f)
Change-Id: I3a0de84558381d68fb2c4feafa246d03a2ca9ecb
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Mihawk can use GPU, so fan control must support GPU thermal sensor.
Tested: Fan speed is automatically controlled when using GPU
(From meta-ibm rev: 2ecdfbd9911c5df8909089d87774a768cfb06716)
Change-Id: I7a62dd349a72c1c3fb6dc314e7a011afb51e75b1
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To allow thermal modes to be selected at BMC standby, the fan control
application must be running. The phosphor-fan-control@.service file is
needed to start fan control at BMC standby and the
phosphor-fan-control-init@.service is no longer required.
Tested:
Witherspoon phosphor-fan-control@.service replaced in image
phosphor-fan-control-init@.service removed from image
fan watchdog configs appended to fan control service still
phosphor-fan-control@.service started at BMC standby
fan control thermal modes presented/changeable at BMC standby
no function change in configured thermal modes
(From meta-ibm rev: f59761e1af85b3ae6432bf0297f5cfe5be71e557)
Change-Id: I4a946f58b6f0c22ebd402304ae9d8fd17a197571
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
On witherspoon-tacoma the GPIO that specifies if the system is water
cooled is Q7 (135). Update phosphor-cooling-type's config file
appropriately.
(From meta-ibm rev: 5d62a1c264bd72d9070e046a5ec10ad9b8715392)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I63131a81ecb984e7746e54a98c539a52d887e155
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Utilize the pgood property as a precondition to loading fan control
events based on property states other than the OCC active events. Since
the OCCs are not active when powered off (pgood = 0) those events having
OCCs active as a precondition are not necessary to be added.
This is the first step to enabling fan control to run at BMC standby.
When the default phosphor-fan-control@.service starts after power on,
the pgood property value is already set to 1. Therefore this produces no
change in fan control activity.
Tested:
No change in fan speed control
(From meta-ibm rev: dadf39cdbb093e0c2566189f3e876dd3c01e13d0)
Change-Id: Ieb010804d59ed318463fca1fcbdce5b5123b81df
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
IBMBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-ibm rev: cbbb0e5b4e44d831fce5daafd13272d401440f40)
Change-Id: Ib214f92b2c384e3eb2a1f53ecf4b21034438d001
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Now the mihawk fan event will build error on openbmc master.
So I made some changes in order to solve the problem.
Tested: Verify fan control functionality of mihawk image
(From meta-ibm rev: 3e3ec10428cabe6917ea982159565024fcd21f9b)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: I84aa7e8fd85dba15a5a84bbf7944bb286e5ba9ae
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Most of mihawk's sensors are different from witherspoon, so I temporarily
added the mihawk part and did not change the witherspoon.
Add mihawk version of fan control and d-bus monitor.
Mihawk does not have a water cooled mode, so another independent folder is added.
Tested: 1.Shut down the system if more than three cores
have a temperature greater than 100 degrees Celcius.
2.Fan control support cpu core, dimm, Onboard.
3.Confirm that sensor is able to return normally via REST.
(From meta-ibm rev: 949f91431bba2f0139cc823d674a741f9590c885)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: Icc401f32c67b622f0f1448e1166112e02c135a8f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use an override in bbappends in meta-witherspoon as described and
recommended in the "following best practices when creating layers"
section of the the Yocto development tasks manual.
ibm-ac-server represents common machine configuration shared by all of
IBMs "Accelerated Compute" class of servers. Apply it wherever any
variables are un-bounded by any override.
This enables more flexible use of meta-witherspoon in build
configurations, and easy addition of machines to the layer.
(From meta-ibm rev: bb0e1d0699a4b9905c053c94af7d882cd71779fc)
Change-Id: I82f7338b0d7a64b5e7a67e19bcdff07f48a332d4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
(From meta-ibm rev: 8f7ff601395419a933eb0506d5cc07fd805f7708)
Change-Id: Iffb2c550511b4024b721c2ba81aec1f909ce7703
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Configure fan monitor to monitor the 4 single rotor chassis fans using
the same config parameters as witherspoon. These parameters will likely
change once complete hardware arrives and is thermally characterized.
Tested:
Built swift fan monitor with correctly generated config
Built witherspoon fan monitor resulting in no config change
(From meta-ibm rev: a7f9cd542edc7f09192ebe30ba6c286b1a01f578)
Change-Id: Iee6eccd75ead287db159b52c7f87a0d3a89e8c99
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Configure fan presence for the 4 single rotor chassis fans to use gpio
or tach feedback presence detection. For the internal boost fan,
currently only configure the use of gpio for presence detection. The
requirement of the boost fan is to assist in cooling specific card
locations when necessary and may be updated later to include presence
detection by tach feedback.
Tested:
Built swift fan presence with correctly generated config
Built witherspoon fan presence resulting in no config change
(From meta-ibm rev: 62395b7eb55fd36aa05bc8ed4593aea78c2e2dea)
Change-Id: I10d0bcf9311926cacb1c5310b80a3bc0f00ed782
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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 fans files in their image.
(From meta-ibm rev: 1c8b9d845092ccb6440fc9241993ac3d4db9c2d6)
Change-Id: I2dfa0b04dfba68311d67af10ccfa979f733e630f
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Swift fails to build because fan-presence is a dependency for
fan-control, and fan-monitor is a dependency for inventory.
So add them in swift with an empty yaml file. Also fix the
FILESEXTRAPATHS_append to have the colon at the beginning
(vs prepend where colon goes at the end) to be able to find
the files in the right order.
Tested: Built swift successfully.
(From meta-ibm rev: 2493fdb38e1fe8e1488ea1bcc5c723c788d92bae)
Change-Id: Ie41caf90a15c3c33ef49ce03ce1890ca9f0c7289
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To support the swift system bring-up, install the cooling type and fan
control application with minimal configuration to run fans at full
speed(9500 RPMs).
Tested:
Cooling type included in image and configured correctly
Fan control included in image and configured correctly
(From meta-ibm rev: 2eb5a13421e2c5e5bc0a0cfac9de87f0cd8c9c59)
Change-Id: I3359cf0444c1b4af8fae1b7f51ef608e4dc2c4c2
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
In preparation for additional systems under the witherspoon layer, add
the machine name as a prefix to the phosphor-fan* configuration
directories. This allows additional machines' phosphor-fan*
configurations to be placed in this layer.
Tested:
Witherspoon phosphor-fan image still contains applications &
phosphor-fan applications are correctly configured.
(From meta-ibm rev: a63359eebc376e3340bdbc34fc4c83410172a5ae)
Change-Id: I9d711cb68e4563e5a2c6dc88d12d2071364bf8ae
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Patrick Venture (1):
build: install into bin instead of sbin
meta-ibm: phosphor-fan: grab cooling-type from bindir
The output binaries from phosphor-fan-presence are now installed into
bin instead of sbin.
Change-Id: I2d42f62b4535775ffd0d1b9473375dd8dc66bb61
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Instead of obmc-standby.target, use multi-user.target.
(From meta-ibm rev: 85cff8cc9e66049d8ac26271c13f82d894ac572f)
Change-Id: I03c3d41c031343fa584511889c70e3def92cb83d
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Out of the box bitbake examines built applications, automatically adds
runtime dependencies and thus ensures any library packages dependencies
are automatically added to images, sdks, etc. There is no need to list
them explicitly in a recipe.
Dependencies change over time, and listing them explicitly is likely
prone to errors - the net effect being unnecessary shared library
packages being installed into images.
Consult
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
for information on when to use explicit runtime dependencies.
(From meta-ibm rev: fa99caa61ecd28325e9070f268a51a5b52363bc4)
Change-Id: Icc97d4b33635caf127a17e70ba6c23f1367eb735
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
In the 5.0 Linux kernel, an I2C device path segment changed:
i2c@1e78a000 -> bus@1e78a000
(From meta-ibm rev: 1b6fab536416be38239ca5505cd00b862b779e33)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3bf6f972e79c6cc188facc511b76b2a79d25f269
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Populate the properties on the Control.ThermalMode interface with the
list of supported modes along with setting the default value of the
current mode.
With setting these modes to uppercase, the events must also be updated
to match to effectively load process the event using this property.
Tested:
Introspected the zone object and verified the values of each
property when fan control initializes the zone.
Requires:
https://gerrit.openbmc-project.xyz/18474
(From meta-ibm rev: 8e08d602f92301db11e36ededcdd180b703a82b1)
Change-Id: I06cd35957640568d4719489ef17aff7f3d13cd7f
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
When a user enables the "Custom" thermal control mode, an alternate set
of floor speeds will be used. This alternate set of floor speeds raises
the floor speeds at corresponding ambient temperatures to sufficiently
cool certain hardware configurations.
Tested:
Alternate floor table is loaded when "Custom" mode enabled
Requires:
openbmc/phopshor-fan-presence
f0e4ebd36d085700c8795c4d80b04d21355dc6d2
(From meta-ibm rev: ae9312165a1b6545d1c9466c91033a101137258d)
Change-Id: I260cf8e351b27ee24c1926da9767516c3da0c1ac
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The intent of the wildcards was to match the base recipe
irrespective of version but you don't need the wildcard
to do that. Simply use the recipe name without the version
to match any version of the base recipe.
With the wildcards phosphor-fan%.bbappend for instance
matched every recipe that starts with phosphor-fan causing
strange build warnings like:
invalid packageconfig cooling-type
while building some of the native fan configuration recipes.
Tested: Built a Witherspoon image
(From meta-ibm rev: 56b4d017ce31e686694eb0b304acd6bb9a1d460e)
Change-Id: I83549464086178956405096dcec2729235e4897f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Update meta-ibm to master HEAD.
Patrick Venture (21):
meta-ibm: add IBMBASE
meta-ibm: romulus: chassis: avsbus-control: set LICENSE field
meta-ibm: romulus: chassis: vrm-control: set LICENSE field
meta-ibm: romulus: gpio: id-button: set LICENSE field
meta-ibm: romulus: ipmi-fru-read-inventory-native: set LICENSE field
meta-ibm: romulus: ipmi-inventory-map-native: set LICENSE field
meta-ibm: romulus: ipmi-inventory-sel-native: set LICENSE field
meta-ibm: romulus: led-manager-config-native: set LICENSE field
meta-ibm: romulus; phosphor-logging-callouts-native: set LICENSE field
meta-ibm: witherspoon: chassis: avsbus-control: set LICENSE field
meta-ibm: witherspoon: chassis: vrm-control: set LICENSE field
meta-ibm: witherspoon: events-policy-native: set LICENSE field
meta-ibm: witherspoon: fan-policy-native: set LICENSE field
meta-ibm: witherspoon: fan-watchdog: set LICENSE field
meta-ibm: witherspoon: thermal-policy-native: set LICENSE field
meta-ibm: witherspoon: inventory-cleanup-native: set LICENSE field
meta-ibm: witherspoon: power-supply-policy-native: set LICENSE field
meta-ibm: witherspoon: power-supply-sync: set LICENSE field
meta-ibm: palmetto: ipmi-inventory-map-native: set LICENSE field
meta-ibm: palmetto: led-manager-config-native: set LICENSE field
meta-ibm: dbus-interfaces-mapper-config-native: set LICENSE field
Change-Id: Ic74e30b1cdd013c7d293dffc9423035632f92e43
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The new subtree model brings the subtrees up from the openbmc-machines
layer.
Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|