From: Pavel Machek <pavel@ucw.cz>
To: Paul Kocialkowski <contact@paulk.fr>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Pali Rohár" <pali.rohar@gmail.com>,
"Andrew F . Davis" <afd@ti.com>,
"Sebastian Reichel" <sre@kernel.org>,
"Chris Lapa" <chris@lapa.com.au>,
"Matt Ranostay" <mranostay@gmail.com>
Subject: Re: [PATCH 5/5] power: supply: bq27xxx: Correct supply status with current draw
Date: Wed, 7 Jun 2017 21:50:23 +0200 [thread overview]
Message-ID: <20170607195023.GA4083@amd> (raw)
In-Reply-To: <1496848839.5534.7.camel@paulk.fr>
[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]
Hi!
> On Wed, 2017-06-07 at 09:52 +0200, Pavel Machek wrote:
> > > [0]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm
> > > it/?
> > > h=v4.12-rc4&id=7f93e1fa032bb5ee19b868b9649bc98c82553003
> >
> > Is there some documentation that explains what different power supply
> > statuses mean? Because without that, we can have long and useless
> > discussions.
>
> Well, I couldn't really find much except the following from Documentation/
> (which is not that helpful, and the BATTERY_STATUS_* don't seem to exist
> anymore):
>
> " STATUS - this attribute represents operating status (charging, full,
> discharging (i.e. powering a load), etc.). This corresponds to
> BATTERY_STATUS_* values, as defined in battery.h. "
>
> Generally speaking, I think the question to be asked is what information users
> will be interested in in each scenario we have to consider.
Hmm. We really should add some documentation :-(.
> > If you have 40Wh battery, and you are charging it with 1mW, I don't
> > believe you should be indicating "charging". That battery is
> > full. Yes, even full batteries are sometimes charged with very low
> > currents to keep them full.
>
> That makes sense. Note that this patch was however designed to solve the problem
> the other way round: my device will report full battery when the PSU was
> disconnected and that it is, in fact, drawing significant current.
That is documented / correct behaviour sometimes. Thinkpad batteries
have thresholds -- lets say 100% and 95%. They charge battery to full
(as expected), but then they won't start charging battery again unless
it drops below 95%. So you can have "battery full, charger
disconnected" state.
[Design like this prolongs longevity of li-ion batteries.]
> > And I'm not sure what this is supposed to do, but its quite strange
> > code.
>
> Could you comment on what is strange about it? This function corrects the status
> based on the current flow as explained through this thread.
>
> > +static int sbs_status_correct(struct i2c_client *client, int *intval)
> > +{
> > + int ret;
> > +
> > + ret = sbs_read_word_data(client, sbs_data[REG_CURRENT].addr);
> > + if (ret < 0)
> > + return ret;
> > +
> > + ret = (s16)ret;
The last line ... is strange.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-06-07 19:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 18:27 [PATCH 1/5] power: supply: bq27xxx: Pass of_node along to allow device-tree supply Paul Kocialkowski
2017-04-30 18:27 ` [PATCH 2/5] power: supply: bq27xxx: Register power supply with devm Paul Kocialkowski
2017-05-01 10:55 ` Sebastian Reichel
2017-05-07 17:43 ` Paul Kocialkowski
2017-04-30 18:27 ` [PATCH 3/5] power: supply: bq27xxx: Rename work structure member to poll_work Paul Kocialkowski
2017-04-30 18:27 ` [PATCH 4/5] power: supply: bq27xxx: Look for status change on external power change Paul Kocialkowski
2017-05-05 8:04 ` Pali Rohár
2017-05-07 17:37 ` Paul Kocialkowski
2017-05-08 13:04 ` Pali Rohár
2017-04-30 18:27 ` [PATCH 5/5] power: supply: bq27xxx: Correct supply status with current draw Paul Kocialkowski
2017-05-28 19:16 ` Pavel Machek
2017-05-31 16:55 ` Paul Kocialkowski
2017-05-31 17:32 ` Pavel Machek
2017-05-31 19:28 ` Paul Kocialkowski
2017-06-07 7:15 ` Paul Kocialkowski
2017-06-07 7:52 ` Pavel Machek
2017-06-07 15:20 ` Paul Kocialkowski
2017-06-07 19:50 ` Pavel Machek [this message]
2017-06-08 10:08 ` Paul Kocialkowski
2017-06-08 19:27 ` Sebastian Reichel
2017-06-09 6:16 ` Paul Kocialkowski
2017-06-13 12:14 ` Sebastian Reichel
[not found] <20170430203801.32357-1-contact@paulk.fr>
[not found] ` <20170430203801.32357-5-contact@paulk.fr>
2017-04-30 22:35 ` Liam Breck
2017-05-01 10:39 ` Paul Kocialkowski
2017-05-01 18:18 ` Liam Breck
2017-05-01 18:37 ` Paul Kocialkowski
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=20170607195023.GA4083@amd \
--to=pavel@ucw.cz \
--cc=afd@ti.com \
--cc=chris@lapa.com.au \
--cc=contact@paulk.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=pali.rohar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).