[CPUSensor] Remove interface in destructor

As part of clean exit remove availableInterface and
operationalInterface in CPUSensor destructor.

Tested: Verified interface removed signal is emitted as expected.

Signed-off-by: Arun P. Mohanan <arun.p.m@linux.intel.com>
Change-Id: I5f1f0a1a63b31cd62bbb73d1324d25eab7beff85
1 file changed
tree: c0a37db8708e9008f5ba15aac30dfef900601b73
  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