Ensure occ active is asserted after fsi scan
During a normal boot, the FSI scan service runs
before the occ active assert. However, when the BMC
is rebooted and the host is running, need to ensure the
occ active assertion does not happen until FSI has been
scanned.
The OCC active assert causes the openpower-occ-control
application to bind to the OCC device. This can not
happen until the FSI bus has been scanned.
Resolves openbmc/openbmc#2360
Change-Id: I3c5e802f051f72a7ae6c79e414ded16ccac4fa02
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
diff --git a/common/recipes-phosphor/occ/openpower-occ-control/op-occ-enable@.service b/common/recipes-phosphor/occ/openpower-occ-control/op-occ-enable@.service
index 7937382..c4c9638 100644
--- a/common/recipes-phosphor/occ/openpower-occ-control/op-occ-enable@.service
+++ b/common/recipes-phosphor/occ/openpower-occ-control/op-occ-enable@.service
@@ -4,6 +4,12 @@
Conflicts=op-occ-disable@%i.service
Wants=org.open_power.OCC.Control.service
After=org.open_power.OCC.Control.service
+Wants=fsi-scan@%i.service
+After=fsi-scan@%i.service
+# TODO - openbmc/openbmc#2278 - Remove fsi-hub-scan
+# These are not needed once we remove fsi-hub-scan service
+Wants=fsi-hub-scan@%i.service
+After=fsi-hub-scan@%i.service
ConditionPathExists=/run/openbmc/host@%i-on
[Service]