From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: Yassine Oudjana <y.oudjana@protonmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] power: supply: add support for S2MU005 battery fuel gauge device
Date: Sun, 1 Feb 2026 12:14:58 +0100 [thread overview]
Message-ID: <aX8yPp2JVubxHNFJ@venus> (raw)
In-Reply-To: <DG2QBROWWMLI.2EE3CBLLPAJHR@disroot.org>
Hi,
On Sat, Jan 31, 2026 at 04:44:36PM +0530, Kaustabh Chakraborty wrote:
> On 2026-01-29 02:59 +01:00, Sebastian Reichel wrote:
> >> +static int s2mu005_fg_get_status(struct s2mu005_fg *priv, int *value)
> >> +{
> >> + int current_now;
> >> + int capacity;
> >> + int ret;
> >> +
> >> + ret = s2mu005_fg_get_current_now(priv, ¤t_now);
> >> + if (ret)
> >> + return ret;
> >> +
> >> + if (current_now <= 0) {
> >> + *value = POWER_SUPPLY_STATUS_DISCHARGING;
> >> + return 0;
> >> + }
> >> +
> >> + ret = s2mu005_fg_get_capacity(priv, &capacity);
> >> + if (ret)
> >> + return ret;
> >> +
> >> + if (capacity < 90)
> >> + *value = POWER_SUPPLY_STATUS_CHARGING;
> >> + else
> >> + *value = POWER_SUPPLY_STATUS_FULL;
> >
> > Usually there is some kind of hysteresis that stops charging
> > when the battery is full and then restarts charging once the
> > battery drops under a certain capacity. As this code first
> > checks the current to determine if the battery is discharging
> > and only then checks if the battery is full - does your code
> > toggle between FULL and DISCHARGING?
>
> (Perhaps I misunderstood your query, let me know if I did)
>
> It has been a while since I last tested this - but as far as I can
> recall, after a certain threshold, the current would constantly bounce
> between -ve and +ve. I believe it was somewhere around 90% to 95% and
> above. If that's what 'hysteresis' is, then yes.
A typical charging setup is:
1. charge to 100%
2. stop charging
3. wait for charge to drop under 95% (or some other treshold)
4. restart charging
5. go to 1
> An older revision of this driver (I don't have it anymore) used to add
> up the consecutive values of current in order to reduce the effect of
> this inconsistency, but it was still unreliable.
>
> Moreover, I do not possess any documentation for this device, so it's
> not possible for me to know what or how.
For the setup I described above, you consider everything above the
treshold as POWER_SUPPLY_STATUS_FULL independent of the current
direction. So you need to reorder:
if (capacity >= 90)
return POWER_SUPPLY_STATUS_FULL;
if (current_now < 0)
return POWER_SUPPLY_STATUS_DISCHARGING;
else if (current_now == 0)
return POWER_SUPPLY_STATUS_NOT_CHARGING;
else
return POWER_SUPPLY_STATUS_CHARGING;
Greetings,
-- Sebastian
next prev parent reply other threads:[~2026-02-01 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 15:39 [PATCH 0/2] Add support for Samsung S2MU005 battery fuel gauge device Kaustabh Chakraborty
2026-01-26 15:39 ` [PATCH 1/2] dt-bindings: power: supply: document Samsung S2MU005 battery fuel gauge Kaustabh Chakraborty
2026-01-26 20:06 ` Conor Dooley
2026-01-26 20:15 ` Kaustabh Chakraborty
2026-01-26 15:39 ` [PATCH 2/2] power: supply: add support for S2MU005 battery fuel gauge device Kaustabh Chakraborty
2026-01-29 1:59 ` Sebastian Reichel
2026-01-31 11:14 ` Kaustabh Chakraborty
2026-02-01 11:14 ` Sebastian Reichel [this message]
2026-02-01 14:29 ` Kaustabh Chakraborty
2026-02-06 13:04 ` Kaustabh Chakraborty
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=aX8yPp2JVubxHNFJ@venus \
--to=sebastian.reichel@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kauschluss@disroot.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=y.oudjana@protonmail.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