From: Andreas Kemnade <andreas@kemnade.info>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Lee Jones <lee@kernel.org>, Sebastian Reichel <sre@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v3 2/3] power: supply: Add bd718(15/28/78) charger driver
Date: Fri, 29 Aug 2025 13:15:42 +0200 [thread overview]
Message-ID: <20250829131542.4f46ebf4@akair> (raw)
In-Reply-To: <6341e004-880c-4a81-811d-a8b367aab39d@gmail.com>
Am Fri, 29 Aug 2025 09:35:00 +0300
schrieb Matti Vaittinen <mazziesaccount@gmail.com>:
> > to indicate that a measurement of the open circuit voltage
> > is available in some register, which enables you do do more
> > precise capacity estimation, right?
>
> AFAIR, the ROHM fuel-gauge algorithm used OCV tables when battery was
> not really open, but 'relaxed', to adjust the coulomb counter based on
> the SOC estimated from the OCV. The 'relaxed' condition was met when the
> current consumption had been 'small', and battery had not been charged
> 'recently'. I have a vague memory the BD71828 had some hardware support
> for knowing battery was 'relaxed', the BD71815 and BD71827 might have
> used coulomb counter 'history' for this. I can try to remember all this
> a bit better if Andreas continues to upstream also the fuel-gauging
> logic from the original RFC. But yeah, these interrupts were for over
> current.
78 at least has. But then the question is how often the relaxed state
really is reached. Current limit is around 3mA per default
(REX_CURCD_TH). So if your
power management is suboptimal, you will not reach that state on
discharing. So, regarding charging, at least when I am on vacation,
the limit on available energy is also my protection against spending
too much time with my electronics (esp. on the smartphone). But that
also means that I will not always charge the device fully. Lowering
current may also mis-indicated that the battery is full.
So the scene is set for any mess with fuel gauges, not limited to the
BD71878.
Regards,
Andreas
next prev parent reply other threads:[~2025-08-29 11:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 18:23 [PATCH v3 0/3] power: supply: add charger for BD71828 Andreas Kemnade
2025-08-21 18:23 ` [PATCH v3 1/3] mfd: bd71828, bd71815 prepare for power-supply support Andreas Kemnade
2025-09-03 12:23 ` Lee Jones
2025-09-03 21:04 ` Andreas Kemnade
2025-09-11 9:47 ` (subset) " Lee Jones
2025-08-21 18:23 ` [PATCH v3 2/3] power: supply: Add bd718(15/28/78) charger driver Andreas Kemnade
2025-08-28 7:45 ` Linus Walleij
2025-08-28 13:01 ` Matti Vaittinen
2025-08-29 6:35 ` Matti Vaittinen
2025-08-29 11:15 ` Andreas Kemnade [this message]
2025-08-29 12:27 ` Matti Vaittinen
2025-09-16 17:39 ` Sebastian Reichel
2025-08-21 18:23 ` [PATCH v3 3/3] MAINTAINERS: Add entry for BD71828 charger Andreas Kemnade
2025-08-22 5:15 ` Matti Vaittinen
2025-08-22 5:17 ` Matti Vaittinen
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=20250829131542.4f46ebf4@akair \
--to=andreas@kemnade.info \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mazziesaccount@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 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.