From: Eugene Shalygin <eugene.shalygin@gmail.com>
To: eugene.shalygin@gmail.com
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org (open list:ASUS EC HARDWARE MONITOR
DRIVER), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v3 1/1] hwmon: (asus-ec-sensors) detect unconnected physical sensors
Date: Sat, 11 Jul 2026 14:26:44 +0200 [thread overview]
Message-ID: <20260711122937.594989-2-eugene.shalygin@gmail.com> (raw)
In-Reply-To: <20260711122937.594989-1-eugene.shalygin@gmail.com>
When there is no physical sensor connected to the motherboard
socket,reading EC register returns one of the special values
(-62, -60, -40). Test for them and return -ENODATA to hwmon.
Signed-off-by: Eugene Shalygin <eugene.shalygin@gmail.com>
---
drivers/hwmon/asus-ec-sensors.c | 49 ++++++++++++++++++++++++++++++---
1 file changed, 45 insertions(+), 4 deletions(-)
diff --git a/drivers/hwmon/asus-ec-sensors.c b/drivers/hwmon/asus-ec-sensors.c
index 29a23484cbe7..3936006adeb6 100644
--- a/drivers/hwmon/asus-ec-sensors.c
+++ b/drivers/hwmon/asus-ec-sensors.c
@@ -185,6 +185,20 @@ enum ec_sensors {
#define SENSOR_TEMP_SENSOR_EXTRA_2 BIT(ec_sensor_temp_sensor_extra_2)
#define SENSOR_TEMP_SENSOR_EXTRA_3 BIT(ec_sensor_temp_sensor_extra_3)
+/*
+ * The values for temperature sensor readings without physical sensors connected.
+ * The value varies across generations and is seemingly defined by the EC chip
+ * used in the given board.
+ */
+static const s32 temperature_blank_values[] = {-62, -60, -40};
+
+static const s32 environment_temp_sensors =
+ SENSOR_TEMP_T_SENSOR | SENSOR_TEMP_T_SENSOR_ALT1 |
+ SENSOR_TEMP_WATER_IN | SENSOR_TEMP_WATER_OUT |
+ SENSOR_TEMP_WATER_BLOCK_IN | SENSOR_TEMP_WATER_BLOCK_OUT |
+ SENSOR_TEMP_T_SENSOR_2 | SENSOR_TEMP_SENSOR_EXTRA_1 |
+ SENSOR_TEMP_SENSOR_EXTRA_2 | SENSOR_TEMP_SENSOR_EXTRA_3;
+
enum board_family {
family_unknown,
family_amd_400_series,
@@ -955,6 +969,7 @@ static const struct dmi_system_id dmi_table[] = {
};
struct ec_sensor {
+ /* this is ec_sensors enum value */
unsigned int info_index;
s32 cached_value;
};
@@ -1047,6 +1062,12 @@ get_sensor_info(const struct ec_sensors_data *state, int index)
return state->sensors_info + state->sensors[index].info_index;
}
+static enum ec_sensors
+get_ec_sensor_type(const struct ec_sensors_data *state, int index)
+{
+ return state->sensors[index].info_index;
+}
+
static int find_ec_sensor_index(const struct ec_sensors_data *ec,
enum hwmon_sensor_types type, int channel)
{
@@ -1291,6 +1312,17 @@ static int get_cached_value_or_update(const struct device *dev,
return 0;
}
+static bool is_blank_temperature_value(s32 value)
+{
+ size_t i;
+
+ for (i = 0; i < ARRAY_SIZE(temperature_blank_values); ++i) {
+ if (value == temperature_blank_values[i])
+ return true;
+ }
+ return false;
+}
+
/*
* Now follow the functions that implement the hwmon interface
*/
@@ -1298,6 +1330,8 @@ static int get_cached_value_or_update(const struct device *dev,
static int asus_ec_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
u32 attr, int channel, long *val)
{
+ const struct ec_sensor_info *sensor_info;
+ enum ec_sensors ec_sensor;
int ret;
s32 value = 0;
@@ -1309,12 +1343,19 @@ static int asus_ec_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
}
ret = get_cached_value_or_update(dev, sidx, state, &value);
- if (!ret) {
- *val = scale_sensor_value(value,
- get_sensor_info(state, sidx)->type);
+ if (ret)
+ return ret;
+
+ sensor_info = get_sensor_info(state, sidx);
+ if (sensor_info->type == hwmon_temp) {
+ ec_sensor = get_ec_sensor_type(state, sidx);
+ if ((environment_temp_sensors & BIT(ec_sensor)) &&
+ is_blank_temperature_value(value))
+ return -ENODATA;
}
+ *val = scale_sensor_value(value, sensor_info->type);
- return ret;
+ return 0;
}
static int asus_ec_hwmon_read_string(struct device *dev,
--
2.55.0
next prev parent reply other threads:[~2026-07-11 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 12:26 [PATCH v3 0/1] hwmon: (asus-ec-sensors) detect unconnected physical sensors Eugene Shalygin
2026-07-11 12:26 ` Eugene Shalygin [this message]
2026-07-11 12:42 ` [PATCH v3 1/1] " sashiko-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260711122937.594989-2-eugene.shalygin@gmail.com \
--to=eugene.shalygin@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.