hwmontemp: Remove trace for unmatched hwmon file

This trace occurred when there was a temp*_input file that didn't have
an entity-manager configuration used by hwmontempsensor.

Remove it since there are valid cases for this, such as
* PSUSensor or some other application monitors that temperature.
* That temperature doesn't need to be monitored.

An alternative could be to make it a debug trace.

Tested:
No longer see statements like the following the journal:
    failed to find match for 9-004d

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Idaeb84f755ce0760071ccb1e17a8fad2dc8059c3
1 file changed
tree: ff551bacfa416da27f2ea2ae639a463c78373318
  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