control: Create manager object for JSON configs
Begin to transition to separate JSON vs YAMl source objects by creating
a manager object that will contain all the cached data to be used across
all events & zones of a system. This will remove the issue in the YAML
based source where the zone objects contained the cache and essentially
restricted a system to having a single zone object.
Also, include parsing of any configured profiles of the system on the
manager object. These profiles will be used to determine which
configurations are to be used on a system given the active state of any
profiles configured.
Change-Id: I817210f8bb763f03b922651192231529bc48a306
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
diff --git a/control/manager.cpp b/control/manager.cpp
index bdea542..053861b 100644
--- a/control/manager.cpp
+++ b/control/manager.cpp
@@ -138,14 +138,14 @@
}
}
-void Manager::doInit()
+void Manager::doInit(const sdeventplus::Event& event)
{
for (auto& z : _zones)
{
z.second->setFullSpeed();
}
#ifdef CONTROL_USE_JSON
- auto delay = getPowerOnDelay(_bus);
+ auto delay = getPowerOnDelay(_bus, event);
#else
auto delay = _powerOnDelay;
#endif