| commit | dae6e186327928bb78cd8cb9f0bf328dbb761a44 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Fri May 21 16:23:07 2021 +0930 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Tue Jun 01 14:58:33 2021 +0930 |
| tree | a4bcde850bdb6d0cf5511be3d75f91516b770605 | |
| parent | 5db90dba77c17391781e57720c2e78b24a7e76a3 [diff] |
NVMeSensor: Split out NVMeContext An NVMeContext instance contains some number of NVMeSensors, but NVMeSenors do not need to be concerned with the implementation details of NVMeContext. Make it easier to discern what's related to what by splitting NVMeContext out into its own header and source file. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: I812a0f7471b0f7150a76964bc353561ac88ca833
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