From: Hermes Zhang <Hermes.Zhang@axis.com>
To: "Pali Rohár" <pali@kernel.org>, "Hermes Zhang" <Hermes.Zhang@axis.com>
Cc: "lars@metafoo.de" <lars@metafoo.de>,
Sebastian Reichel <sre@kernel.org>, kernel <kernel@axis.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] power: supply: bq27xxx: Return the value instead of -ENODATA
Date: Thu, 1 Apr 2021 01:51:28 +0000 [thread overview]
Message-ID: <3acaabf2ec63418891e3f698c16b9a21@XBOX01.axis.com> (raw)
In-Reply-To: <20210331140238.jl3qprpqhqave4bf@pali>
On 3/31/21 10:02 PM, Pali Rohár wrote:
> @@ -1655,9 +1655,6 @@ static int bq27xxx_battery_read_time(struct bq27xxx_device_info *di, u8 reg)
> return tval;
> }
>
> - if (tval == 65535)
> - return -ENODATA;
> -
> return tval * 60;
> I'm not sure if this is correct change. If value 65535 is special which
> indicates that data are not available then driver should not return
> (converted) value 65535*60. If -ENODATA is there to indicate that data
> are not available then -ENODATA should not be used.
>
> And if there is application which does not handle -ENODATA for state
> when data are not available then it is a bug in application.
Yeah, I just have a feeling return -ENODATA for time_to_full/empty is
not good here. Because:
1. From chip datasheet, it mentioned return 65535 when it's not
available (e.g. read time_to_full when discharging), but the driver
changes behavior here.
2. There is other case will return -ENODATA (e.g. the gauge not
calibrated), so it will confuse application which is real failure.
Could we change the value in minute instead of seconds in
bq27xxx_battery_read_time(), so that means driver do nothing but only
pass the value from the chip?
Best Regards,
Hermes
next prev parent reply other threads:[~2021-04-01 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 13:51 Hermes Zhang
2021-03-31 14:02 ` Pali Rohár
2021-04-01 1:51 ` Hermes Zhang [this message]
2021-04-01 8:50 ` Pali Rohár
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=3acaabf2ec63418891e3f698c16b9a21@XBOX01.axis.com \
--to=hermes.zhang@axis.com \
--cc=kernel@axis.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=sre@kernel.org \
/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®