threshold: fix up documentation per sensor.value

The Sensor.Value has a list of "recognized hierarchies" which is
similarly replicated in all of the Threshold interfaces.  The lists
in the Threshold objects were incomplete, so update them.

Also, make trivial whitespace / formatting changes to ensure linewrap
is at the appropriate (80) columns.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I6bd76ca423e1ea3c2e0c7ce59e10dce1125eb6d1
5 files changed
tree: 4097d2380e30d8e5ad3f9f4db8f50a3900f856a7
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .shellcheck
  6. LICENSE
  7. MAINTAINERS
  8. meson.build
  9. meson_options.txt
  10. README.md
README.md

phosphor-dbus-interfaces

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

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 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