commit | 3c969f656faa6c5301a7918810a7331b824295b0 | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Fri Jan 07 11:15:31 2022 -0600 |
committer | Matt Spinler <spinler@us.ibm.com> | Fri Jan 07 11:21:37 2022 -0600 |
tree | ff551bacfa416da27f2ea2ae639a463c78373318 | |
parent | 50107246047ad793e50ccc8aa717e25196b4a20a [diff] |
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
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