soft-off: ensure only one soft off service runs

OpenBMC has two implementations of the soft off function. This function
is utilized to tell the host to shutdown gracefully and for the BMC to
wait for that shutdown.

The implementation used depends on the interface being used to talk
with the host. There is the IPMI based interface and the new PLDM based
interface.

In theory, only one of these interfaces should be used to talk with the
host on a system. In reality there are some systems such as rainier
which are in the process of switching from IPMI to PLDM. In this case
both services for soft off are installed into the image.

Since this co-existence of both packages on a single system is a
temporary situation, put a simple change in which ensures the IPMI soft
off service does not run if the PLDM one is present. The assumption here
is that if the newer PLDM based package is installed, the system owner
prefers the PLDM soft off service be utilized.

Change-Id: I1f78749a7f1c67160281f1186dc6ea0e059aea79
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: ce5946f984076abcf5730de2e38c679f6233af24
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.