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/registry/schema/schema.json b/extensions/openpower-pels/registry/schema/schema.json
index 89530b4..a98f01c 100644
--- a/extensions/openpower-pels/registry/schema/schema.json
+++ b/extensions/openpower-pels/registry/schema/schema.json
@@ -293,7 +293,7 @@
"description": "The event type PEL field. Optional and defaults to na",
"type": "string",
"enum": ["na", "misc_information_only", "tracing_event",
- "dump_notification"]
+ "dump_notification", "env_normal"]
},
"powerFault":
@@ -438,7 +438,7 @@
{
"description": "The symbolic FRU callout.",
"type": "string",
- "enum": ["service_docs", "pwrsply", "air_mover", "pgood_part", "usb_pgood"]
+ "enum": ["service_docs", "pwrsply", "air_mover", "pgood_part", "usb_pgood", "ambient_temp", "ambient_temp_back", "ambient_perf_loss"]
},
"symbolicFRUTrusted":