| commit | 6b6891c52e550c42507d4b413cbc4c6a09235535 | [log] [tgz] |
|---|---|---|
| author | Zev Weiss <zev@bewilderbeest.net> | Thu Apr 22 02:46:21 2021 -0500 |
| committer | Ed Tanous <ed@tanous.net> | Tue Apr 27 22:19:44 2021 +0000 |
| tree | 49bad4273eb148ddf1df5c1524564f2c1c6ec5ee | |
| parent | 8e0eccdf9dac7dee104339a96db7cd6591209537 [diff] |
Add Unit property to dbus interfaces Previously, the lack of the Unit property on the Value interfaces provided by dbus-sensors meant that readings from its sensors weren't displayed in phosphor-webui/webui-vue. Here it's added as an extra parameter to setInitialProperties, allowing sensors that handle multiple types of data (e.g. IpmbSensor, PSUSensor) to determine the appropriate string to pass once they've had time to determine that. Tested: PSUSensor, ADCSensor, CPUSensor, TachSensor, and HwmonTempSensor all have an appropriate Unit property available on dbus, and are displayed in webui-vue. Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: I5e6df74cc42d9fb84852c5bf3ea5d3b383a16cdc
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access