commit f2704dc3905667c82d5d7835f575a9226701361c
author Andrew Geissler <geissonator@yahoo.com> Mon May 23 16:09:45 2022 -0400
committer Sampa Misra <sampmisr@in.ibm.com> Fri Jun 03 04:16:17 2022 +0000
tree b9e230f2185d5549b1973254c836266b5ce73ae8
parent 8c2135c53678f9928cbef29bf400ff682ad0d88b

support a BootProgress of SystemSetup for host running

SystemSetup is a BootProgress that indicates the host is booted, but in
a state where user interaction is needed. On an IBM system, this state
is entered when VMI needs some configuration or when PHYP's NVRAM has
been cleared.

pldm needs to consider the host running in this scenario because it's
needed to send user configuration information like the VMI IP and
static vs. dhcp information.

Tested:
- Verified that pldm properly communicates with the host firmware when
  it is in SystemSetup

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3072919569572c4eecc71cd8cd44352f5474c2b6

host-bmc/dbus_to_host_effecters.cpp

diff --git a/host-bmc/dbus_to_host_effecters.cpp b/host-bmc/dbus_to_host_effecters.cpp
index 2486c64..a4d4be0 100644
--- a/host-bmc/dbus_to_host_effecters.cpp
+++ b/host-bmc/dbus_to_host_effecters.cpp
@@ -166,7 +166,9 @@
             (currHostState != "xyz.openbmc_project.State.Boot.Progress."
                               "ProgressStages.OSRunning") &&
             (currHostState != "xyz.openbmc_project.State.Boot.Progress."
-                              "ProgressStages.OSStart"))
+                              "ProgressStages.OSStart") &&
+            (currHostState != "xyz.openbmc_project.State.Boot.Progress."
+                              "ProgressStages.SystemSetup"))
         {
             std::cout << "Host is not up. Current host state: "
                       << currHostState.c_str() << "\n";