NVMeContext: Add the ability to remove NVMeSensors

Sometimes sensors go away, e.g. with drive hot-unplug. Make sure we have
the ability to remove them from the set of monitored sensors.

Change-Id: Ifdd51aebfc1c0be964b98db1bde534f539c3f911
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
1 file changed
tree: 449a1e4cf8499d9fa2732074efdf9710c5f612d1
  1. include/
  2. service_files/
  3. src/
  4. subprojects/
  5. tests/
  6. .clang-format
  7. .clang-ignore
  8. .clang-tidy
  9. .gitignore
  10. Jenkinsfile
  11. LICENSE
  12. MAINTAINERS
  13. meson.build
  14. meson_options.txt
  15. OWNERS
  16. README.md
README.md

dbus-sensors

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.

key features

  • 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

sensor documentation