PEL: Add ambient temp PEL registry entries
Add 3 new PEL message registry entries:
* temp crossed EPOW3 threshold
* temp crossed EPOW4 threshold
* temp under EPOW3 threshold
These error logs will come from the sensor-monitor application that
monitors the HardShutdown (EPOW4) and SoftShutdown (EPOW3) D-Bus
threshod interfaces. These interfaces will only ever be used on the
ambient virtual sensor in the systems that use PELs.
There is no entry for going below the EPOW4 threshold because, while
ther sensor-monitor code would create an error for that, the interface
will have the hysteresis set so that it will never happen.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ieed5364654a80697e189cf2e7614b0aead1fb218
diff --git a/extensions/openpower-pels/pel_values.cpp b/extensions/openpower-pels/pel_values.cpp
index 2ef8c24..dfad44d 100644
--- a/extensions/openpower-pels/pel_values.cpp
+++ b/extensions/openpower-pels/pel_values.cpp
@@ -176,7 +176,8 @@
{0x00, "na", "Not Applicable"},
{0x01, "misc_information_only", "Miscellaneous, Informational Only"},
{0x02, "tracing_event", "Tracing Event"},
- {0x08, "dump_notification", "Dump Notification"}};
+ {0x08, "dump_notification", "Dump Notification"},
+ {0x30, "env_normal", "Customer environmental problem back to normal"}};
/**
* The possible values for the Event Scope field in the User Header.
@@ -223,10 +224,10 @@
* actual names.
*/
const std::map<std::string, std::string> symbolicFRUs = {
- {"service_docs", "SVCDOCS"}, {"pwrsply", "PWRSPLY"},
- {"air_mover", "AIRMOVR"}, {"pgood_part", "PGDPART"},
- {"usb_pgood", "USBPGD"},
-};
+ {"service_docs", "SVCDOCS"}, {"pwrsply", "PWRSPLY"},
+ {"air_mover", "AIRMOVR"}, {"pgood_part", "PGDPART"},
+ {"usb_pgood", "USBPGD"}, {"ambient_temp", "AMBTEMP"},
+ {"ambient_temp_back", "AMBBACK"}, {"ambient_perf_loss", "AMBPERF"}};
PELValues::const_iterator findByValue(uint32_t value, const PELValues& fields)
{