PEL: Clean up PEL Entry D-bus signals
Don't emit an InterfacesAdded signal when restoring the
org.open_power.Logging.PEL.Entry interface on D-Bus, since this happens
before the bus name is claimed.
Also, don't emit PropertiesChanged signals when the PEL code updates the
Resolution, EventID, and ServiceProviderNotify properties with their
final values on the xyz.openbmc_project.Logging.Entry interface.
Definitely the PC signals aren't necessary during the restore phase, and
while technically it'd be valid to send them after the IA signal has
already been emitted for the Logging.Entry interface, nobody is
listening for them anyway and doing it this way makes it so only
InterfacesAdded signals are emitted when event logs are created.
Change-Id: Ia30163fb58e78d3746015903acc7597b2a097aa4
diff --git a/extensions/openpower-pels/manager.hpp b/extensions/openpower-pels/manager.hpp
index e4c4953..42ce0c4 100644
--- a/extensions/openpower-pels/manager.hpp
+++ b/extensions/openpower-pels/manager.hpp
@@ -61,7 +61,7 @@
setEntryPath(entry.first);
setServiceProviderNotifyFlag(entry.first);
// Create PELEntry interface and setup properties with their values
- createPELEntry(entry.first);
+ createPELEntry(entry.first, true);
}
setupPELDeleteWatch();
}
@@ -419,8 +419,10 @@
* supported
*
* @param[in] obmcLogID - The OpenBMC entry log ID
+ * @param[in] skipIaSignal - If The InterfacesAdded signal should be
+ * skipped after creating the interfaces.
*/
- void createPELEntry(uint32_t obmcLogID);
+ void createPELEntry(uint32_t obmcLogID, bool skipIaSignal = false);
/**
* @brief Reference to phosphor-logging's Manager class