quoted
I'm not so happy abusing the statistic counters like this. Especially
when we have a better API for temperature and voltage: hwmon.
phy_temp_warn maps to hwmon_temp_max_alarm. phy_temp_high maps to
either hwmon_temp_crit_alarm or hwmon_temp_emergency_alarm.
The under voltage maps to hwmon_in_lcrit_alarm.
FWIW, the statistics counters in this driver are already abused
(phy_polarity_detect, phy_open_detect, phy_short_detect), so
I am not sure if adding more abuse makes a difference (and/or
if such abuse is common for phy drivers in general).
Hi Guenter
Abuse is not common in general. I think this is the only driver
abusing stats to return flags. At the time those where added, we did
not have phy cable test support. Now we do, i would also suggest that
the driver makes use of that infrastructure to issue a cable test
report. These 'stats' need to stay, since they are ABI, but we should
not add more.
That is also why i said "Especially when we have a better API".
Andrew