lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 27 Mar 2023 22:22:04 +0200
From:   Jakob Hauser <jahau@...ketmail.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Sebastian Reichel <sre@...nel.org>, Lee Jones <lee@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Beomho Seo <beomho.seo@...sung.com>,
        Chanwoo Choi <cw00.choi@...sung.com>,
        Stephan Gerhold <stephan@...hold.net>,
        Raymond Hackley <raymondhackley@...tonmail.com>,
        linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH 00/10] Add RT5033 charger device driver

Hi Pavel,

On 25.03.23 17:08, Pavel Machek wrote:
> Hi!

...

>> - 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?

Yes, at RT5033 in the "not charging" state the system draws the power 
from the battery.

...

Kind regards,
Jakob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ