From: "Pali Rohár" <pali.rohar@gmail.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: bq27x00_battery status report issue
Date: Thu, 19 Jan 2012 11:56:43 +0100 [thread overview]
Message-ID: <10055259.ygSgKeUM8f@pali> (raw)
In-Reply-To: <CANOLnONB5m5iNbWy1=7WWN7T76S1vACbWtJu+KGyhqw2-cA3sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
On Saturday 14 January 2012 23:10:05 Grazvydas Ignotas wrote:
> Hi,
>
> After 270968c0984ae "bq27x00_battery: Fix reporting status value for
> bq27500 battery" status doesn't seem to be reported correctly when the
> battery is close to fully charged state. It reports "Not charging"
> while in fact there is >130mA current flowing to the battery according
> to current_now.
>
> This status report seems to be based on CHG bit in status register,
> but looking at the datasheet the description says "(Fast) charging
> allowed", which I guess means that the chip recommends charging and
> not that charging is actually going on? If you check the bit while
> battery is discharging and it's not full, the bit is also set.
Now I do not have device with bq27500 chip for testing. I read datasheet again
and I think that your interpretation may be correct. Can you write patch for
this problem and test it?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-19 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 21:10 bq27x00_battery status report issue Grazvydas Ignotas
2012-01-19 10:56 ` Pali Rohár [this message]
2012-01-20 11:02 ` Grazvydas Ignotas
2012-01-20 13:38 ` Pali Rohár
2012-02-01 17:37 ` Anton Vorontsov
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=10055259.ygSgKeUM8f@pali \
--to=pali.rohar@gmail.com \
--cc=cbouatmailru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=notasas@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 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.