summaryrefslogtreecommitdiff
path: root/meta-ibm/recipes-phosphor/gpio/phosphor-gpio-monitor_%.bbappend
AgeCommit message (Collapse)AuthorFilesLines
2021-09-02meta-phosphor: change systemd.bbclass to match upstream override syntaxPatrick Williams1-4/+4
Upstream bbclasses changed to typically use the `:${PN}` override syntax, including the SYSTEMD_ variables. Change our systemd.bbclass to do the same for consistency and perform a tree-wide variable replacement. Spot checked by building bletchley and witherspoon and checking some of the SYSTEMD_LINK directives on installed packages under qemu. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
2021-08-11meta-ibm: prep for new override syntaxAdriana Kobylak1-5/+5
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-07-20Remove phosphor-gpio-presence from p10bmcB. J. Wyman1-2/+0
The phosphor-gpio-presence application is no longer needed for power supply presence detection after the updates to using libgpiod in the phosphor-psu-monitor application. Remove the systemd parts of the bbappend, and remove the obmc conf files. Signed-off-by: B. J. Wyman <bjwyman@gmail.com> Change-Id: I18a7f36e21d18a22f7625aadc3229ce5439c8d6a
2021-04-01ibm: gpio-monitor: Replace rainier with p10bmcAdriana Kobylak1-2/+2
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified the files were installed as expected: rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/gpio/phosphor-power-supply-0.conf Change-Id: I6539c71cfc37fa67027204b17c68a0c7f8fec5a6 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-01-12gpio-presence: wants relationship with multi-userAndrew Geissler1-1/+1
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>
2020-04-27meta-ibm: move all meta-witherspoon metadataBrad Bishop1-0/+16
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>