On 5/21/21 5:42 AM, Riwen Lu wrote:
The scpi hwmon shows the sub-zero temperature in an unsigned integer,
which would confuse the users when the machine works in low temperature
environment. This shows the sub-zero temperature in an signed value and
users can get it properly from sensors.
Signed-off-by: Riwen Lu <luriwen@xxxxxxxxxx>
Tested-by: Xin Chen <chenxin@xxxxxxxxxx>
What did you test ? Did you really manage to run the system
in such an environment ?
---
drivers/hwmon/scpi-hwmon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/scpi-hwmon.c b/drivers/hwmon/scpi-hwmon.c
index 25aac40f2764..583a600bc82d 100644
--- a/drivers/hwmon/scpi-hwmon.c
+++ b/drivers/hwmon/scpi-hwmon.c
@@ -99,7 +99,7 @@ scpi_show_sensor(struct device *dev, struct device_attribute *attr, char *buf)
scpi_scale_reading(&value, sensor);
- return sprintf(buf, "%llu\n", value);
+ return sprintf(buf, "%lld\n", value);
'value' is declared as u64, not as s64.
I can not evaluate what the firmware actually reports. The API
reports an u64. Do you have any evidence for your claim that
it returns a signed value under any circumstances ?
On top of that, your change affects not only temperature values,
but all attributes. It is highly unlikely that the firmware would
report negative power or energy values. It is, however, possible
that energy values have the upper bit of an u64 set after a
long runtime. Your change would result in a negative energy value
if that is ever the case.
Guenter
