LockOut: add events for Lock-Out / Tag-Out style devices

It is common practice for dangerous machinery to have a Lock-Out-Tag-Out
process (LOTO) to prevent the system from operating while the machine
is being worked on.  Servers may have Lock-Out style devices to prevent
either power or liquid cooling operations while the system is in
service.  For example, a switch may disable all liquid cooling pumps so
that the coolant does not pump onto the floor while coolant lines are
being repaired.

Add events to indicate the state of a Lock-Out style device.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9ae6cfe02ed492c02e6f19725955ff6b0f0e7afa
3 files changed
tree: 520a99fd9e0b2b7659e3ee9bad8ffb343cf9109c
  1. gen/
  2. registry/
  3. subprojects/
  4. yaml/
  5. .gitignore
  6. .markdownlint.yaml
  7. .prettierrc.yaml
  8. .shellcheck
  9. LICENSE
  10. meson.build
  11. meson.options
  12. OWNERS
  13. README.md
  14. requirements.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.

Building

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.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References