| commit | 6f5241692eec25e7c90b7cfcb39940e8b8cde702 | [log] [tgz] |
|---|---|---|
| author | Willy Tu <wltu@google.com> | Tue Aug 03 16:26:35 2021 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Aug 24 11:41:17 2021 +0000 |
| tree | 6ea4d0199e9d376e10c4da12b836e25b4b1e2897 | |
| parent | 964c4c78a6532c65ee0670f39796dac93efb9c06 [diff] |
watchdog: Add Watchdog Timeout signal The `Timeout` signal is used to indicate a watchdog timeout event. It is being used in `phosphor-watchdog` for timeout events. It has a `Action` property to indicate the timeout event that it took. It could be different from the expiredAction due to fallback watchdog. The new signal is picked up in `phosphor-sel-logger` handle Watchdog SEL logs. Change-Id: I0e20af1d23f7a8dbc9a7580797923373b04f2905 Signed-off-by: Willy Tu <wltu@google.com>
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