Make use of obmc-fan-control-ready@.target
This involves the following:
* Start the fan-control-init@.service on a power on.
* That service will set fans to full speed, delay for a bit, and then
start the obmc-fan-control-ready target.
* This target will start the fan monitor and real fan control services.
* On a power off, the target and these services will be deactivated.
Doing it this way ensures the fans will have had time to ramp up from a
cold start before applications start looking at them.
Currently, on a reboot at runtime the same thing will occur. The watchdog
would have already brought the fans to high speed, so this will extend
that time at full speed by another 20 (or similar, it's configurable)
seconds, ensuring we know what speed the fans are at.
Resolves openbmc/openbmc#1567
Change-Id: I73a1f91f0efaf319df97b59334073116d45f40c3
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
diff --git a/meta-ibm/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-control-zone-config/zones.yaml b/meta-ibm/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-control-zone-config/zones.yaml
index ecabc03..0d2c8d0 100644
--- a/meta-ibm/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-control-zone-config/zones.yaml
+++ b/meta-ibm/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-control-zone-config/zones.yaml
@@ -1,3 +1,8 @@
+manager_configuration:
+ power_on_delay: 20
+
+zone_configuration:
+
#Air cooled zones
- zone_conditions:
- name: air_cooled_chassis