control: Support `member` signal triggers
`member` signals are signals that a dbus object could send out on dbus
that acts as a notification that does not contain any other data. This
adds support to fan control events that can be triggered by this type of
signal on dbus to essentially run a set of actions. The configuration of
this trigger is contained within the JSON configuration of the trigger
on the event and not against the event's group(s).
i.e.)
"triggers": [
{
"class": "signal",
"signal": "member",
"member":
{
"name": "Pressed",
"path": "/xyz/openbmc_project/Chassis/Buttons/Power0",
"interface": "xyz.openbmc_project.Chassis.Buttons.Power"
}
}
]
Change-Id: Ie7924174333c604fb54c8f18560a890bf6a7c489
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
diff --git a/control/json/triggers/handlers.hpp b/control/json/triggers/handlers.hpp
index 1ad4766..f4e7adb 100644
--- a/control/json/triggers/handlers.hpp
+++ b/control/json/triggers/handlers.hpp
@@ -154,6 +154,15 @@
mgr.setOwner(std::get<Path>(obj), serv, std::get<Intf>(obj), hasOwner);
return true;
}
+
+ /**
+ * @brief Processes a dbus member signal, there is nothing associated or
+ * any cache to update when this signal is received
+ */
+ static bool member(message&, const SignalObject&, Manager&)
+ {
+ return true;
+ }
};
} // namespace phosphor::fan::control::json::trigger::signal