| commit | 9f59489e62d6d8a6fd299e118bcc0c3b95fc1353 | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Mon Jul 19 15:06:23 2021 -0700 |
| committer | Ed Tanous <ed@tanous.net> | Wed Jul 21 14:22:23 2021 +0000 |
| tree | 028ae1c71e3525eeda9b8df0c2d88afa4fe8dd25 | |
| parent | f98dca6cd01d52538490f830cf7c2a6d007d2543 [diff] |
Andrew has volunteered to maintain nvme This patchset adds him to the maintainers list so he can do that. In the near future, we should really restructure this so we can use OWNERS files effectively to separate out the per-daemon stuff, but that's more file-moving than I have time for at the moment. I trust arj to do the right thing for the project, and he's already well respected within OpenBMC. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I1ce35495642ebb4a2265002ce7f5dfd905527238
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