| commit | 2424cb7c9752cbecc3d133a67cf1c20f8589f2c1 | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Mon Dec 02 22:34:05 2019 +0000 |
| committer | James Feist <james.feist@linux.intel.com> | Mon Dec 02 22:34:05 2019 +0000 |
| tree | 50bea3f201913bc5763401e892407c011812f141 | |
| parent | d89bf5429f3687e483f230b8f5e1858abc37ad8c [diff] |
Revert "Corrected the Settings service name" This reverts commit d89bf5429f3687e483f230b8f5e1858abc37ad8c. Reason for revert: Was right the in the first place https://github.com/openbmc/meta-phosphor/blob/master/recipes-phosphor/settings/phosphor-settings-manager/xyz.openbmc_project.Settings.service Change-Id: I1d1c8c099c3f56976a7b3bb3d92f989c9915d595
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