| commit | 4ec6587fa908fe9df41cc0962ab6ff6446fbd54f | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Tue Jul 31 11:00:25 2018 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Wed Jun 17 08:39:28 2020 -0700 |
| tree | dbfd640519af2763fa2a1e590a97ca18e52ca4a8 | |
| parent | 12a8ca89d996ecebe09f70d107d8a63f9cbd441a [diff] |
Change sensor Value to double Generally most demons we've looked at take the int64 values and immediately translates the value to a double. As the individual demons are doing the floating point computation anyway, there doesn't seem to be a large benefit to keeping separating the value on dbus, only to recompute in each demon, causing extra overhead for consumers. In some cases this causes an extra d-bus call, for instance when reading a threshold a consumer to know the value needs to also access the value field to get the scale, which is arguably more expensive than having the property be a double in the first place. Change-Id: If47c19f77286e3764d167a6843ba91e2ca1769b8 Signed-off-by: James Feist <james.feist@linux.intel.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Only the xyz/openbmc_project interfaces are built by default.
Enable the OpenPower D-Bus interfaces with:
--enable-openpower-dbus-interfaces
Enable IBM D-Bus interfaces with:
--enable-ibm-dbus-interfaces