| commit | 67601bdb4ed30a9f859eb2a9542dd3a973ea907e | [log] [tgz] |
|---|---|---|
| author | James Feist <james.feist@linux.intel.com> | Tue Jun 16 17:14:44 2020 -0700 |
| committer | James Feist <james.feist@linux.intel.com> | Thu Jun 18 21:30:51 2020 +0000 |
| tree | 8a36708c36787c41ec28a8ffe7a5e590b8dd5e42 | |
| parent | 4f45e429cc3d99b5fb2666e30395d116e474efec [diff] |
Add Available interface Some sensors become unavailable and this is expected, this adds the available interface to be able to track this, and allows an external app to set this in cases where the sensor cannot distinguish that it is not working. Tested: Set the property on d-bus, saw the property and reading change Change-Id: Ib52ee668caeccc590b95ad2b1ea60470721d28ab Signed-off-by: James Feist <james.feist@linux.intel.com>
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