All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jakob Hauser <jahau@rocketmail.com>
Cc: Sebastian Reichel <sre@kernel.org>, Lee Jones <lee@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Beomho Seo <beomho.seo@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Stephan Gerhold <stephan@gerhold.net>,
	Raymond Hackley <raymondhackley@protonmail.com>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 00/10] Add RT5033 charger device driver
Date: Sat, 25 Mar 2023 17:08:20 +0100	[thread overview]
Message-ID: <20230325160819.GA1820@bug> (raw)
In-Reply-To: <cover.1677620677.git.jahau@rocketmail.com>

Hi!

> Some comments on the end-of-charge behavior. The rt5033 chip offers three
> options. In the Android driver, a forth option was implemented.

Hmm. I'm working on that on motorola-cpcap driver, and I guess this is going
to be common problem for many drivers.

> - By default, the rt5033 chip charges indefinitely. The current goes down but
>   there is always a charge voltage to the battery, which might not be too good
>   for the battery lifetime.
> - There is the possibility to enable a fast charge timer. The timer can be
>   set to 4, 6, 8... 16 hours. After that time has elapsed, charging stops
>   and the battery gets discharged. This option with a timer of 4 hours was
>   chosen by Beomho Seo in the patchset of March 2015. However, that option
>   is confusing to the user. It doesn't initiate a re-charge cycle. So when
>   keeping plugged in the device over night, I find it discharging on the
>   next morning.
> - The third option of the rt5033 chip is enabling charging termination. This
>   also enables a re-charge cycle. When the charging current sinks below the
>   end-of-charge current, the chip stops charging. The sysfs state changes to
>   "not charging". When the voltage gets 0.1 V below the end-of-charge constant
>   voltage, re-charging starts. Then again, when charging current sinks below
>   the end-of-charge current, the chip stops charging. And so on, going up and
>   down in re-charge cycles. In case the power consumption is high (e.g. tuning
>   on the display of the mobile device), the current goes into an equilibrium.
>   The downside of this charging termination option: When reaching the end-of-
>   charge current, the capacity might not have reached 100 % yet. The capacity
>   to reach probably depends on power consumption and battery wear. On my mobile
>   device, capacity reaches 98 %, drops to 96 % until re-charging kicks in,
>   climbs to 98 %, drops to 96 %, and so on. Not reaching 100 % is a bit
>   confusing to the user, too.

Is the system powered from the battery in the not-charging case?

Anyway, we should teach userspace that "full battery" does not neccessary mean 100%,
as keeping battery at 4.3V wears it down quickly.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2023-03-25 16:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1677620677.git.jahau.ref@rocketmail.com>
2023-02-28 22:32 ` [PATCH 00/10] Add RT5033 charger device driver Jakob Hauser
2023-02-28 22:32   ` [PATCH 01/10] mfd: rt5033: Drop rt5033-battery sub-device Jakob Hauser
2023-02-28 22:32   ` [PATCH 02/10] mfd: rt5033: Fix chip revision readout Jakob Hauser
2023-03-05 10:47     ` Lee Jones
2023-03-05 16:10       ` Jakob Hauser
2023-03-06  9:18         ` Lee Jones
2023-03-06 22:57           ` Jakob Hauser
2023-02-28 22:32   ` [PATCH 03/10] mfd: rt5033: Fix comments and style in includes Jakob Hauser
2023-03-05 10:48     ` Lee Jones
2023-03-05 16:11       ` Jakob Hauser
2023-03-06  9:15         ` Lee Jones
2023-02-28 22:32   ` [PATCH 04/10] mfd: rt5033: Fix STAT_MASK, HZ_MASK and AICR defines Jakob Hauser
2023-03-05 10:52     ` Lee Jones
2023-02-28 22:32   ` [PATCH 05/10] mfd: rt5033: Apply preparatory changes before adding rt5033-charger driver Jakob Hauser
2023-03-05 10:55     ` Lee Jones
2023-03-05 16:14       ` Jakob Hauser
2023-04-02 10:08         ` Jakob Hauser
2023-04-05 15:09           ` Lee Jones
2023-02-28 22:32   ` [PATCH 06/10] power: supply: rt5033_charger: Add RT5033 charger device driver Jakob Hauser
2023-02-28 22:32   ` [PATCH 07/10] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-02-28 22:32   ` [PATCH 08/10] power: supply: rt5033_charger: Make use of high impedance mode Jakob Hauser
2023-04-02 10:14     ` Jakob Hauser
2023-02-28 22:32   ` [PATCH 09/10] power: supply: rt5033_battery: Adopt status property from charger Jakob Hauser
2023-02-28 22:32   ` [PATCH 10/10] dt-bindings: Add documentation for rt5033 mfd, regulator and charger Jakob Hauser
2023-02-28 23:15     ` Rob Herring
2023-03-01  2:35     ` Rob Herring
2023-03-05 15:54       ` Jakob Hauser
2023-04-02 10:21         ` Jakob Hauser
2023-03-25 16:08   ` Pavel Machek [this message]
2023-03-27 20:22     ` [PATCH 00/10] Add RT5033 charger device driver Jakob Hauser

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=20230325160819.GA1820@bug \
    --to=pavel@ucw.cz \
    --cc=beomho.seo@samsung.com \
    --cc=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jahau@rocketmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=raymondhackley@protonmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sre@kernel.org \
    --cc=stephan@gerhold.net \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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.