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/pel_entry.hpp b/extensions/openpower-pels/pel_entry.hpp
index 5b36d29..4d1bd6c 100644
--- a/extensions/openpower-pels/pel_entry.hpp
+++ b/extensions/openpower-pels/pel_entry.hpp
@@ -33,7 +33,7 @@
PELEntry(sdbusplus::bus::bus& bus, const std::string& path,
const std::map<std::string, PropertiesVariant>& prop, uint32_t id,
Repository* repo) :
- PELEntryIface(bus, path.c_str(), prop),
+ PELEntryIface(bus, path.c_str(), prop, true),
_obmcId(id), _repo(repo)
{
}
@@ -65,4 +65,4 @@
};
} // namespace pels
-} // namespace openpower
\ No newline at end of file
+} // namespace openpower