PEL: Use raw procedure names in PEL msg reg
Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.
Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.
There are pointers added to the README and schema to find the available
procedures and their descriptions.
Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072
diff --git a/extensions/openpower-pels/src.cpp b/extensions/openpower-pels/src.cpp
index af25c50..6d1fab6 100644
--- a/extensions/openpower-pels/src.cpp
+++ b/extensions/openpower-pels/src.cpp
@@ -1036,8 +1036,8 @@
if (!regCallout.procedure.empty())
{
// Procedure callout
- callout = std::make_unique<src::Callout>(priority,
- regCallout.procedure);
+ callout = std::make_unique<src::Callout>(priority, regCallout.procedure,
+ src::CalloutValueType::raw);
}
else if (!regCallout.symbolicFRU.empty())
{