From: Konstantin Aladyshev <aladyshev22@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kunyi@google.com, aladyshev22@gmail.com,
Konstantin Aladyshev <aladyshev@nicevt.ru>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] hwmon: (sbtsi) Don't read sensor more than once if it doesn't respond
Date: Fri, 2 Apr 2021 00:45:42 +0300 [thread overview]
Message-ID: <20210401214543.4073-1-aladyshev22@gmail.com> (raw)
From: Konstantin Aladyshev <aladyshev@nicevt.ru>
SBTSI sensors don't work when the CPU is off.
In this case every 'i2c_smbus_read_byte_data' function would fail
by a timeout.
Currently temp1_max/temp1_min file reads can cause two such timeouts
for every read.
Restructure code so there will be no more than one timeout for every
read opeartion.
Signed-off-by: Konstantin Aladyshev <aladyshev@nicevt.ru>
---
drivers/hwmon/sbtsi_temp.c | 59 +++++++++++++++++++-------------------
1 file changed, 29 insertions(+), 30 deletions(-)
diff --git a/drivers/hwmon/sbtsi_temp.c b/drivers/hwmon/sbtsi_temp.c
index e35357c48b8e..e09a8cf6de45 100644
--- a/drivers/hwmon/sbtsi_temp.c
+++ b/drivers/hwmon/sbtsi_temp.c
@@ -74,53 +74,52 @@ static int sbtsi_read(struct device *dev, enum hwmon_sensor_types type,
u32 attr, int channel, long *val)
{
struct sbtsi_data *data = dev_get_drvdata(dev);
+ u8 temp_int_reg, temp_dec_reg;
s32 temp_int, temp_dec;
int err;
switch (attr) {
case hwmon_temp_input:
- /*
- * ReadOrder bit specifies the reading order of integer and
- * decimal part of CPU temp for atomic reads. If bit == 0,
- * reading integer part triggers latching of the decimal part,
- * so integer part should be read first. If bit == 1, read
- * order should be reversed.
- */
- err = i2c_smbus_read_byte_data(data->client, SBTSI_REG_CONFIG);
- if (err < 0)
- return err;
-
- mutex_lock(&data->lock);
- if (err & BIT(SBTSI_CONFIG_READ_ORDER_SHIFT)) {
- temp_dec = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_DEC);
- temp_int = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_INT);
- } else {
- temp_int = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_INT);
- temp_dec = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_DEC);
- }
- mutex_unlock(&data->lock);
+ temp_int_reg = SBTSI_REG_TEMP_INT;
+ temp_dec_reg = SBTSI_REG_TEMP_DEC;
break;
case hwmon_temp_max:
- mutex_lock(&data->lock);
- temp_int = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_HIGH_INT);
- temp_dec = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_HIGH_DEC);
- mutex_unlock(&data->lock);
+ temp_int_reg = SBTSI_REG_TEMP_HIGH_INT;
+ temp_dec_reg = SBTSI_REG_TEMP_HIGH_DEC;
break;
case hwmon_temp_min:
- mutex_lock(&data->lock);
- temp_int = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_LOW_INT);
- temp_dec = i2c_smbus_read_byte_data(data->client, SBTSI_REG_TEMP_LOW_DEC);
- mutex_unlock(&data->lock);
+ temp_int_reg = SBTSI_REG_TEMP_LOW_INT;
+ temp_dec_reg = SBTSI_REG_TEMP_LOW_DEC;
break;
default:
return -EINVAL;
}
+ /*
+ * ReadOrder bit specifies the reading order of integer and
+ * decimal part of CPU temp for atomic reads. If bit == 0,
+ * reading integer part triggers latching of the decimal part,
+ * so integer part should be read first. If bit == 1, read
+ * order should be reversed.
+ */
+ err = i2c_smbus_read_byte_data(data->client, SBTSI_REG_CONFIG);
+ if (err < 0)
+ return err;
+
+ mutex_lock(&data->lock);
+ if (err & BIT(SBTSI_CONFIG_READ_ORDER_SHIFT)) {
+ temp_dec = i2c_smbus_read_byte_data(data->client, temp_dec_reg);
+ temp_int = i2c_smbus_read_byte_data(data->client, temp_int_reg);
+ } else {
+ temp_int = i2c_smbus_read_byte_data(data->client, temp_int_reg);
+ temp_dec = i2c_smbus_read_byte_data(data->client, temp_dec_reg);
+ }
+ mutex_unlock(&data->lock);
- if (temp_int < 0)
- return temp_int;
if (temp_dec < 0)
return temp_dec;
+ if (temp_int < 0)
+ return temp_int;
*val = sbtsi_reg_to_mc(temp_int, temp_dec);
--
2.17.1
next reply other threads:[~2021-04-01 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 21:45 Konstantin Aladyshev [this message]
2021-04-05 21:41 ` Guenter Roeck
2021-04-06 18:16 ` [PATCH v2] " Konstantin Aladyshev
2021-04-06 18:42 ` Guenter Roeck
[not found] ` <CACSj6VUCgxCQeA9EF4Oz+pKY+TdF9Gp=DV1V=-TcVE4ixtg45Q@mail.gmail.com>
2021-04-06 20:09 ` Guenter Roeck
2021-04-06 21:09 ` Konstantin Aladyshev
2021-04-06 21:34 ` Guenter Roeck
2021-04-06 22:25 ` Konstantin Aladyshev
2021-04-06 23:28 ` Guenter Roeck
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=20210401214543.4073-1-aladyshev22@gmail.com \
--to=aladyshev22@gmail.com \
--cc=aladyshev@nicevt.ru \
--cc=jdelvare@suse.com \
--cc=kunyi@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®