From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Yikai Tsai <yikai.tsai.wiwynn@gmail.com>
Cc: patrick@stwcx.xyz, "Carsten Spieß" <mail@carsten-spiess.de>,
"Jean Delvare" <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] hwmon: (isl28022) Fix current reading calculation
Date: Mon, 16 Jun 2025 06:00:24 -0700 [thread overview]
Message-ID: <454245c8-ce59-4c87-9d92-4a924f83aa1f@roeck-us.net> (raw)
In-Reply-To: <5f774072-9d85-41d1-acf0-cb95450a16fb@roeck-us.net>
On 6/16/25 05:59, Guenter Roeck wrote:
> On 6/10/25 05:27, Geert Uytterhoeven wrote:
>> Hi Yikai,
>>
>> On Mon, 19 May 2025 at 10:48, Yikai Tsai <yikai.tsai.wiwynn@gmail.com> wrote:
>>> According to the ISL28022 datasheet, bit15 of the current register is
>>> representing -32768. Fix the calculation to properly handle this bit,
>>> ensuring correct measurements for negative values.
>>>
>>> Signed-off-by: Yikai Tsai <yikai.tsai.wiwynn@gmail.com>
>>
>>
>>> --- a/drivers/hwmon/isl28022.c
>>> +++ b/drivers/hwmon/isl28022.c
>>> @@ -154,6 +154,7 @@ static int isl28022_read_current(struct device *dev, u32 attr, long *val)
>>> struct isl28022_data *data = dev_get_drvdata(dev);
>>> unsigned int regval;
>>> int err;
>>> + u16 sign_bit;
>>>
>>> switch (attr) {
>>> case hwmon_curr_input:
>>> @@ -161,8 +162,9 @@ static int isl28022_read_current(struct device *dev, u32 attr, long *val)
>>> ISL28022_REG_CURRENT, ®val);
>>> if (err < 0)
>>> return err;
>>> - *val = ((long)regval * 1250L * (long)data->gain) /
>>> - (long)data->shunt;
>>> + sign_bit = (regval >> 15) & 0x01;
>>> + *val = (((long)(((u16)regval) & 0x7FFF) - (sign_bit * 32768)) *
>>> + 1250L * (long)data->gain) / (long)data->shunt;
>>
>> Isn't this complex operation to convert the 16-bit register value to
>> a two-complement signed number equivalent to a simple cast?
>>
>> (s16)regval
>>
>> isl28022_read_in() has similar code, but as the sign bit is not always
>> the MSB, it needs two additional shifts:
>>
>> ((s16)(regval << shift)) >> shift
>>
>
> Yes, I know. This could all be simplified using sign_extend32(), but I really
> wanted to be able to apply it. If someone sends me a register map, maybe I can
s/map/dump/
> write unit test code and use it to simplify the driver.
>
> Guenter
>
next prev parent reply other threads:[~2025-06-16 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 8:40 [PATCH v2 0/1] " Yikai Tsai
2025-05-19 8:40 ` [PATCH v2 1/1] " Yikai Tsai
2025-05-20 4:56 ` Guenter Roeck
2025-06-10 12:27 ` Geert Uytterhoeven
2025-06-16 12:59 ` Guenter Roeck
2025-06-16 13:00 ` Guenter Roeck [this message]
2025-06-16 13:17 ` Geert Uytterhoeven
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=454245c8-ce59-4c87-9d92-4a924f83aa1f@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@carsten-spiess.de \
--cc=patrick@stwcx.xyz \
--cc=yikai.tsai.wiwynn@gmail.com \
/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®