openbmc_project/Logging/IPMI.interface.yaml

6     type followed by type-specific information.  The type-specific information
8     adding the SEL record), sensor number, event direction and event-specific
9     data for system type events; or timestamp and OEM data for OEM type events.
11     The interface allows adding system or OEM type events.  For system type
12     events it requires a generator ID (0x20 for BMC), sensor D-Bus path, event
13     direction (assertion or de-assertion), and event specific data. For OEM type
14     events, it requires the record type and OEM data.
19     - name: IpmiSelAdd
23           - name: Message
27           - name: Path
31           - name: SELData
35           - name: Assert
38                 An indicator if the SEL event is asserting or de-asserting.
39           - name: GeneratorID
45           - name: RecordID
50           - xyz.openbmc_project.Common.Error.InternalFailure
51           - xyz.openbmc_project.Common.Error.InvalidArgument
53     - name: AddExtended
57           - name: Message
61           - name: Path
65           - name: SELData
69           - name: GeneratorID
74           - name: eventType
78           - name: sensorType
82           - name: sensorNum
87           - name: RecordID
92           - xyz.openbmc_project.Common.Error.InternalFailure
93           - xyz.openbmc_project.Common.Error.InvalidArgument
95     - name: IpmiSelAddOem
97           Log an OEM record type SEL entry requested from external to the BMC.
99           - name: Message
103           - name: SELData
107           - name: RecordType
110                 The OEM record type for the SEL entry.
112           - name: RecordID
117           - xyz.openbmc_project.Common.Error.InternalFailure
118           - xyz.openbmc_project.Common.Error.InvalidArgument
120     - name: Clear
124     - name: SELDelete
128           - name: RecordID
133           - xyz.openbmc_project.Common.Error.InternalFailure
134           - xyz.openbmc_project.Common.Error.ResourceNotFound