| commit | 964c4c78a6532c65ee0670f39796dac93efb9c06 | [log] [tgz] |
|---|---|---|
| author | Andrei Kartashev <a.kartashev@yadro.com> | Wed Aug 11 11:52:54 2021 +0300 |
| committer | Andrei Kartashev <a.kartashev@yadro.com> | Wed Aug 18 15:10:36 2021 +0300 |
| tree | e1c94421242dc069d5254a25617cea23f62ec26d | |
| parent | ce8e3892a6d6dbf325f75a9f5eb710445dd04d39 [diff] |
SEL: add record with custom Sensor/Event Type The existing `IpmiSelAdd` method is suited only to add limited range of internal SEL record types since it lack some important SEL record fields. BMC system may want to support more event types and/or adding external records with IPMI Add SEL Entry Command. In order to implement this extended version of the method was added: `AddExtended`. The method is similar to existing `IpmiSelAdd` except it accept additional data fields: `eventType`, `sensorType`, `sensorNum` and don't need `Assert` field since it is part of `eventType`. `Path` field was not excluded to support case where software want to define custom eventType but still use internal sensor lookup mechanism. Empty string can be used when there is no dbus sensor for the record. Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com> Change-Id: I595ae9409ef695368e94eca837f9bdc1ad93c0e3
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir