Age | Commit message (Collapse) | Author | Files | Lines |
|
- We have already made the change to make the snooping
port optional, which means that snoopd daemon can still
run and host the interfaces & Postcode Raw Value property
even on the systems with no snooping port.
- The intent behind this commit is to over ride the snoop-device
name to empty from the meta-ibm layer so that the snoopd daemon
will run without the support for snooping port on ibm machines.
Tested:
- Build images for witherspoon-tacoma & rainier, and made sure the
snoopd service runs without any issues.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I622a903f9084a9b94561c1202f8c637d30062112
|
|
For installing gendumpheader plugin, the recipe was including
all files from tools/dreport.d/ibm.d.
Corrected it to take only gendumpheader plugin so that it wont conflict
with installation of other plugins from same directory.
Signed-off-by: PriyangaRamasamy <priyanga24@in.ibm.com>
Change-Id: I5a1358f07aba6997cb9ae84dba59b3420c7ce968
|
|
The firmware code in these power supplies takes about 1500 milliseconds
to boot after they are inserted, and the presence line goes active.
Until the firmware has completely booted, the power supplies will not
respond to the I2C traffic initiated by the BMC device driver code as it
attempts to probe the hardware.
Adding in a DRIVER_BIND_DELAY_MS environment variable, set to 1500
(milliseconds), to delay the device driver binding in order to hold off
the probe until the power supply firmware should be ready, in order to
avoid ENXIO errors.
Change-Id: I101f8e3b7ff1c2c9e76df758c4551c7793006266
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
|
|
- The intent behind this commit is to pull the snooping daemon
into tacoma & rainier.
- This daemon is used for hosting the necessary dbus interface
& Raw Value property for the pldm to write the progress codes
into.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I4730046a40345d74d53b19a5058e8e45d2d40e8f
|
|
The phosphor-inventory-manager application supports creating
associations based on JSON files, where the JSON files have conditions
built into them that say which inventory-manager property values are
required for the associations files to be valid.
Add minimal associations files for the Rainier 2U, Rainier 4U, and
Everest systems that just contain the fan inventory associations for
now. The condition is the 'IM' property on the com.ipzvpd.VSBP
interface on the system/chassis/motherboard path.
Change-Id: Ib6807d8982a2efeb94692b917804c53965d6c98a
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
Now that phosphor-fan-monitor starts at multi-user instead of the
fans-ready target, it needs a JSON config option to let it know when to
start monitoring after the fans have ramped up.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If8eef303ee585dd30b3fbe9764a624eeab3b1a8a
|
|
Moved "inherit native" statements to the last position to remove QA Issues.
The message is: WARNING: QA Issue: {RECIPENAME}: native/nativesdk class is not
inherited last, this can result in unexpected behaviour. Classes inherited
after native/nativesdk: {CLASSFILES} [native-last]
Tested: The witherspoon image builds without the warnings.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: Ic3c71234abfcac8b26478bc32808e3bec8bba810
|
|
The feature was implemented as an append to the kernel (BSP) layers in
meta-phsophor. This created a three way dance between machine layers,
BSP and meta-phosphor, when it should have been the kernel layer
providing this feature and machines could then opt in.
Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY
workaround.
As the feature is simply turning on a pair of kernel options without any
other impact, we can implement it by adding the options to our
defconfigs. In fact, aspeed and hpe kernel configurations enable the two
kernel options:
$ git grep CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y
$ git grep CONFIG_INPUT_EVDEV
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y
Other machines that wish to enable this feature should ensure it is
added to their BSP's defconfig, or add it to their machine specific
defconfig.
Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
- This commit would package the post-code-manager deamon
support for tacoma & rainier machines.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ieea0b1516419d8cde2b93126fb278ffa16f0c15d
|
|
Upstream recipe moved the disabling of deprecated crypto algorithms into
a new DEPRECATED_CRYPTO_FLAGS variable.
(Klaus: also adjust phosphor's EXTRA_OECONF for this package to not
double-disable already obsolete ciphers)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I75e2c35ada37c9510a0af347772cdeb2b23d99e9
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
|
|
This application resides in the phosphor-fan-presence repo and creates
phosphor-logging based event logs for temperature threshold alarms.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id5a7ce7590efe82eb1f9615853cabd58ac269c24
|
|
This will start phosphor-fan-presence at the multi-user target. It
doesn't need to know about the power state when just checking GPIOs and
tach sensors, so let it run all the time. It also avoids a race
condition with phosphor-fan-monitor if it starts earlier.
This commit also adds a JSON vs YAML packageconfig so service files can
be installed to different places based on how it is configured. And
since the service file has different contents based on when it starts,
the phosphor-fan-presence-tach@.service file was moved into the repo so
that the repo itself can determine which one to install based on how the
JSON vs YAML configuration option is set.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I4c00f0854974c70efb5097d0344c45385dbcb085
|
|
This new phosphor-state-manager package allows a user to track the state
of their hypervisor firmware. This new software utilizes the
BootProgress property to determine the hypervisor state and relies on a
different software entity (for example PLDM) to monitor state requests
and send the appropriate messages to the hypervisor firmware.
Includes the autobump which has the new function:
phosphor-state-manager: srcrev bump 58477b5287..75f38ee42d
Andrew Geissler (3):
hypervisor: state management support
hypervisor: monitor boot progress
hypervisor: reset requested host state on power off
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I4c4bfc06db3b38b114c28692db808cffceff628a
|
|
This is the configuration that CI builds.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: Ib9b2ccc554f7ca2c602cec57a300416105791412
|
|
This distro feature is not used anywhere. Remove it to reduce
the clutter.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1dd4e5ae52197a377b552a8a0e7d1e6d7e7ebe7f
|
|
Most openpower machines use DISTRO="openbmc-openpower" but
Romulus has a "openbmc-romulus" distro config file. This
config file has nothing except an inclusion of the openpower
one, so remove this useless indirection.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I371ce4137369e4964eed1529f8a8190e31721ecc
|
|
Fan monitoring should not need the inlet rotors included in the nonzero
speed trust group. This causes the nonfunctional timer to start for
these rotors and immediately stop since they are never actually taken
into account in the determination of trust.
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I411faab9dcd67fa2409f6be39be54969a0eb2520
|
|
Fan monitoring should not need the inlet rotors included in the nonzero
speed trust group. This causes the nonfunctional timer to start for
these rotors and immediately stop since they are never actually taken
into account in the determination of trust.
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I043f1003319e84e3c93b59f80963525d9d7d4eac
|
|
- The intent behind this commit is to enable & set OEM
specific options to pldm recipe via the meta-ibm layer.
- pldm in its current state, has a configurations folder
which contains all the configurations that are consumed
by the daemon at runtime.
- pldm also has an oem folder(s) that can contain the
vendor specific configuration files.
- So, removing these files from the meta-layer as they are
obsolete.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I91d23c37abff45f3da18676269be843610b6a9d1
|
|
The plan on IBM systems is that the host software will communicate via
PLDM which will utilize the D-Bus properties provided by this function.
Note that the new D-Bus interfaces provided by this function could also
be supported via Redfish. The PowerOnDelaySeconds and
PowerOffDelaySeconds properties within the ComputerSystem object would
map to what's provided here. There are no plans currently to do this
though as IBM's only use case is controlling this function via the
in-band PLDM interface.
Tested:
- Verified the generated image had scheduling service and function
worked as expected scheduling a power on then power off
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I781dfba0871853feafed49faa72bf1c05f657d85
|
|
Both rainier and witherspoon-tacoma systems support the mpreboot
feature.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieeb4724a5cf5678ba0f6ab950b5403db5aebcd88
|
|
The memory preserving reboot is a feature utilized on IBM systems which
allows a system to be rebooted with its memory preserved. This is
utilized in situations where the host firmware has crashed and put the
processor in an unusable state. The processors are put back in a good
state by rebooting the system. Memory is preserved though so host
firmware can capture the relevant data from memory needed to debug the
cause of the failure.
This feature is implemented across a few different repositories within
OpenBMC so lets create a distro feature to enable it across all of the
software stacks.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ia16626ba6e46aa8de642abef677735ed957f9f9e
|
|
The ibmtpm2tss tools are required to use the Nuvoton NPCT750A TPM
from userland.
The ibmtpm2tss package also required OpenSSL camellia support, so
remove the override disabling that for those two machines.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: Ifc0afc58f4a31ea4b6d1750d470738d0d0e82754
|
|
There are some machines (Witherspoon-Tacoma and Rainier) that
have a TPM device, which will be used eventually. We need
access to the recipes in this layer.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I3b10ee4d39a69e651a790ae3238e39c45e21ce72
|
|
- This commit would package the biosconfig-manager for both
tacoma & rainier machines.
Tested By :
- With the changes booted the tacoma machine & observed that the
biosconfig-manager services are up & runnning
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I90542368a70284c97e1f33d29770c751a61631ca
|
|
The squashfs tools are used by PLDM during inband update.
Reference: https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/37510
Tested: Verified that the rootfs/usr/sbin/mksquashfs existed.
Change-Id: Id8d00765e72ce04bc8f039403a570aa7dca98b26
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Instead of using phosphor-dbus-monitor to create errors and handle power
offs for fan errors, use phosphor-fan-monitor instead, now that it has
the functionality. To do this, add the new rules to the fan monitor
config files, and remove the phosphor-dbus-monitor fan rules files.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia03186132f04087be76d2fd43412c37698407f60
|
|
The VERSION_ID may not have a commit number for the cases a tag
is created, ex: 2.10.1. Since the code is expecting a commit
number of 1-4 digits, use a '0' if no commit number exists.
Tested: Created a tag 2.10.99 which sets VERSION_ID=2.10.99.
Without this change, build fails with:
"Exception: IndexError: list index out of range"
With this change there are no build errors.
Change-Id: I3b56ebc1844ec6748b92cca3484f9aa1f4d983f8
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
I've been utilizing my gerrit admin abilities to merge autobumps and
backup Brad in these meta layers. The OWNERS plugin disabled this
path for me. My intention is to keep with this same workflow. I'll merge
autobumps and backup Brad as needed.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ib248c6122644dbbd4b024ed07eb7259db85daf1e
|
|
(From meta-ibm rev: c203fa3d1ca3de7d61b3c06a22dbf4385202cc78)
Change-Id: Iab1adeab9ff493e05e26f31f72c9cb708f28e73e
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Please see https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/39379
for details about why this is necessary.
(From meta-ibm rev: 501f9fd6b63c8b11c0ae0f6268a98c33b764caa0)
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I05862abb52f7fac1bcf4fdd939a1101aa2431f9d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The rule of thumb within OpenBMC is to utilize a wants relationship with
targets, especially the multi-user.target. This follows the general
design of always allowing the system to continue whenever possible.
For example I'm doing some bringup in simulation where these services
are not required, but their failure is impacting my ability to reach
a successful multi-user.target state which impacts other targets that
depend on it.
Tested:
- Verified multi-user.target completes successfully now on my bringup
system
(From meta-ibm rev: f2f6d38efdfa1a88a5f41b9871e0d3aa76f193d1)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I687fbbb7006a3d9b9abe1d308802914d64224410
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Everest has the max31785 at a different i2c address that is behind a
mux, so install its hwmon config at that associated location.
Tested:
Hwmon instance for the max31785 starts successfully on Everest
(From meta-ibm rev: cd84eb53a79edcabddd5e7720f9e0389f4e96151)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ide9ca8bd76d708ef9453dc7d02526dfbb1dd8a30
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Rainier does not need/want the old PSU monitor.
(From meta-ibm rev: eba91da180e9ec5b7260aebb87fb05ab1e48c930)
Change-Id: I6c9e58257cd7a8b3a675b69ae3d88603a8fb0e94
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Corrected the gpio pins and paths for detecting fans wired to a PCA9552
behind a mux according to the Everest schematics. Fan presence will fail
to access these gpios until the Everest dts is updated to expose them.
(From meta-ibm rev: 072949a9b84112572559baa76d12b9a7c77f8547)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I9456ff8bd4298f3414f41180732e8e17b738acfa
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Temporarily remove detecting fan presence by gpio on Everest until the
gpios are added within the dts and accessible in userspace.
(From meta-ibm rev: 7c4944f2dfd2ce5ab811f7e07a5a4d8de5949ee4)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I62f80e494a9d0feffa45cc3a1e08f0a859fca35b
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove extraneous commas from the Everest fan monitor JSON config so it
can be loaded/parsed.
(From meta-ibm rev: 84d05fda258fbd02650d859f6fe9a77a6e5ef7a6)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ib0b044f8657593137d67cec036ab615e265398e3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
openbmc master has exceeded the available flash space on witherspoon.
Remove LDAP so it fits again and we can continue to use witherspoon for
HW CI validation of openbmc master commits.
IBM has forked off its own openbmc repo for maintenance of customer
witherspoon systems. Therefore it is not necessary for openbmc
master to continue to support everything.
Tested:
- Verified generated image flashes on witherspoon and HW CI tests passed
- obmc-phosphor-image-witherspoon.squashfs-xz 19.27MB -> 18.53MB
(From meta-ibm rev: 6390f0999f00b1cdfe19daf2d7e8868c25808497)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I39b5d785919bdcd54b6bcf04217439050442f119
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-debug-collector renamed "host-dump-offload-transport" build
option into "host-transport" to make generic for supporting other host
dump action (i.e create,delete) not only offload so, changed build option
here as well based on phosphor-debug-collector.
phosphor-debug-collector patch:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/38792
(From meta-ibm rev: eb951216a95e360431644dba46f04fc0541fb608)
Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I4466896b67cb7490b13e6c32113bb59651fbcdb3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
led-set-all-groups-asserted.sh needs to be called with "false"
as part of below transitions to turn off all indicator LEDs
- BMC booting to standby and staying at standby
- BMC starting to power on
(From meta-ibm rev: e784b71c2d625b4507758df4bb5743fc678251f3)
Change-Id: If248220964c65e91e9382504b1a7095cc5cec26b
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Install all the fan application config files into a rainier image
(From meta-ibm rev: dd3117e5c3b6768ca6975b04ebc70f8e716529b2)
Change-Id: I51d017b3a6ad34595bc9dce0fd1693c0012fc52e
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the fan control config files for the rainier type
machines. The recipe updates to install these files into a rainier image
will collectively be done after all fan application config files are
added.
(From meta-ibm rev: 5d8b514768c45eee76bd19bffc432dc5778ca075)
Change-Id: I5fa1f5cc879d7f3a951f7972ac391767de3647f3
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the fan monitor config files for the rainier type
machines. The recipe updates to install these files into a rainier image
will collectively be done after all fan application config files are
added.
(From meta-ibm rev: b28c40c5cb1eeec7239f39cbf7bb0e901340b501)
Change-Id: I445d141de53577e0c151ece3e258752814a631b4
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the fan presence config files for the rainier type
machines. The recipe updates to install these files into a rainier image
will collectively be done after all fan application config files are
added.
(From meta-ibm rev: f131f38e89da79848595670af0d150e01aaa664a)
Change-Id: I514589fcde2a7d500e272b7d45ac90961bb46368
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add the max31785 fan controller device to hwmon.
(From meta-ibm rev: 71404ba4966e32bb4ed9a120062d669ed642d851)
Change-Id: I4b2cd1c5379e76ccf40f52dc6ceca6a98f931f40
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This reverts commit 3a70e470e8ec8239e27db9b7361f568cebd5ef72.
The health monitor code has fixed openbmc/phosphor-health-monitor#1
so we can put this back in.
(From meta-ibm rev: fc48727d30a75aa9c12d0f49d8a4124202a995ff)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3b5e1ca730af0a06c94291e84397e24d6b2bb83d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The max31785-msl application is now a package within the phosphor-hwmon
recipe, so that package needs to be enabled and installed on
`ibm-ac-server` alias of machines which have a max31785 chip. These
machines require that the minimum ship level(msl) be verified on them
using this application.
Tested:
Built phosphor-hwmon package after enabling max31785-msl package
Verified application, config file, and service existed in image
(From meta-ibm rev: 33184059fa07ca12e11fb9e8dde2d6a31e1f029e)
Change-Id: I186fb6ca930e4107738d4ed90d31b6233be3d6f2
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Use the latest bumped upstream commit of the phosphor-fan-presence repo.
(From meta-ibm rev: a5824115356901e363c55f0d013a9821a51eba1b)
Change-Id: Ib5f3e4718de3f288bf71321680d42234512d1be9
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The next release of Yocto is soon and most of the upstream
layers have switched support strings for it. Support layer
compat for gatesgarth (current) and dunfell (previous).
(From meta-ibm rev: 284e2ad06544f567582b2732a22e052190b5b95a)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic1cb74ebd387715b08feccd8b94bfd0be7d35205
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-health-monitor package added some code recently that only
supports a mtdblock based filesystem. This causes issues with the HW CI
machine, witherspoon, documented in openbmc/phosphor-health-monitor#1.
Time permitting, IBM should come back to the phosphor-health-monitor and
figure out if it makes sense within it's products. If it does, then the
appropriate bmc_health_config.json should be created for IBM systems.
(From meta-ibm rev: 3a70e470e8ec8239e27db9b7361f568cebd5ef72)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I02dff59cade863d287919a01d0b1f93f67661279
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|