Remove OCC EREMOTEIO return code hack
With openbmc/openbmc#2329, an OCC sensor value will not be read when the
associated fault file is set to true. This will set the value to 0 when
a sensor is faulted at startup or not update the previous value during
the monitoring loop if the OCC sensor becomes faulted.
Applications(i.e. fan control) needing to react to a faulted OCC sensor
can subscribe to property changed signals on the OperationalStatus
Functional property for the sensor's dbus object.
Tested:
A faulted OCC sensor has a non-functional status on dbus
Change-Id: Ia43ebb1e0fe0227797bc4034e617ac357edd348d
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
diff --git a/hwmonio.cpp b/hwmonio.cpp
index fe167f5..18ceff9 100644
--- a/hwmonio.cpp
+++ b/hwmonio.cpp
@@ -68,8 +68,7 @@
const std::string& id,
const std::string& sensor,
size_t retries,
- std::chrono::milliseconds delay,
- bool isOCC) const
+ std::chrono::milliseconds delay) const
{
int64_t val;
std::ifstream ifs;
@@ -114,18 +113,6 @@
exit(0);
}
- if (isOCC)
- {
- if (rc == EREMOTEIO)
- {
- // For the OCCs, when an EREMOTEIO is return, set the
- // value to 255*1000
- // (0xFF = sensor is failed, 1000 = sensor factor)
- val = 255000;
- break;
- }
- }
-
if (0 == std::count(
retryableErrors.begin(),
retryableErrors.end(),