| commit | a9d1508b4493d6c84eede78c61eddf7f5f6a9f97 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Mon May 24 13:55:12 2021 +0930 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Thu Jun 03 10:45:33 2021 +0930 |
| tree | 55e0e8ecd7da9404ab8c74bf3b7345339517742e | |
| parent | fa500ae9aba49c49e2855434d301662671cfe185 [diff] |
NVMeContext: Split out NVMeMCTPContext The MCTP-oriented implementation of NVMeContext requires linking against a libmctp build that provides an SMBus binding implementation. The SMBus binding implementation isn't upstream, and neither are the kernel interfaces it relies on. Later, an NVMe MI Basic implementation will be introduced. NVMe MI Basic only requires support for SMBus block reads rather than MCTP, though is not as fully featured as the MCTP interface and is not required to be supported by implementers of the NVMe specification. For now, reduce NVMeContext to a base class that NVMeMCTPContext extends and only use the NVMeMCTPContext type where explicitly required. This opens up the opportunity to make MCTP support a build-time configurable option. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: I6920f79ca389481f3be43ee9a0d336bf8f72d55b
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