| commit | 30cccb1b4f9768f7c76452d00a256593e87cd6e4 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Mon Mar 21 14:20:58 2022 +1030 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Thu Mar 24 23:18:13 2022 +0000 |
| tree | c754eef2c4ef40424d44864ed622191fbefc05b8 | |
| parent | 25e20bd8cc614edb6bc3a335d6b4eb2e9df5c054 [diff] |
nvmesensor: Remove MCTP transport implementation This was implemented in terms of a series of patches against libmctp that were never upstreamed (because they in-turn relied on kernel patches that also were never upstreamed). Further, there are no configurations enabling the nvme-mi-mctp option in openbmc/openbmc. This is motivated by the need to refactor NVMeContext to support polling all sensors inside the polling period on a given root bus. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: Ib20b7f3ce218191a391d7b2d893f204fb97b7ab5
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