Update InternalFailure Type and Add Error Type Parameter
This commit modifies the 'InternalFailure' dump type and replaces
it with a more generic 'ErrorLog' type. In addition, it introduces
a new parameter for specifying the type of the error that
triggered the dump.
This is allowing it to cater to various types of errors beyond just
internal failures. With the capability to pass architecture-specific
errors, this change increases compatibility and maintainability without
requiring alterations in the common interface YAML file for each new
error type to be supported.
Change-Id: I896bb995632dad1206385ef92819f3bfffd16f88
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
diff --git a/yaml/xyz/openbmc_project/Dump/Create.interface.yaml b/yaml/xyz/openbmc_project/Dump/Create.interface.yaml
index 3b08b1f..62823cf 100644
--- a/yaml/xyz/openbmc_project/Dump/Create.interface.yaml
+++ b/yaml/xyz/openbmc_project/Dump/Create.interface.yaml
@@ -68,6 +68,12 @@
description: >
The path to a file to create the dump, for example a systemd
core-dump.
+ - name: "ErrorType"
+ description: >
+ Specifies the type of the error that triggered the BMC dump
+ collection. This is a string identifier for the error type. The
+ type of the error dictates the kind of debug data collected
+ during the dump process.
- name: DumpType
description: >
@@ -79,9 +85,12 @@
- name: "UserRequested"
description: >
Dump triggered by the user.
- - name: "InternalFailure"
+ - name: "ErrorLog"
description: >
- Dump triggered due to InternalFailure type error commit.
+ This type of dump is triggered in response to a specific error
+ commit. The error type needs to be specified in the "ErrorType"
+ field. If no parameters are provided, a default dump will be
+ generated.
- name: "Ramoops"
description: >
Dump triggered due to Ramoops type error commit.