| commit | 4316218ab824c3c60f566b38f620a6d778e45a83 | [log] [tgz] |
|---|---|---|
| author | Patrick Venture <venture@google.com> | Wed Oct 23 10:44:53 2019 -0700 |
| committer | Patrick Venture <venture@google.com> | Wed Oct 23 10:44:53 2019 -0700 |
| tree | c13c48ff2e5175498320c7e37e8ebc08af62802a | |
| parent | 432d1edf7ac86f69558273307a59e4b1cf86b8a6 [diff] |
PSUSensor: create association before init By creating the association interface before initializing, it sets up the sensors with the object mapper. Tested: Verified the same sensors were available on dbus, and now they showed up under the ObjectMapper as well. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I972b3c313e93b68f741d01a53142e75885d292b4
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