Messages in this thread | | | Date | Tue, 15 Nov 2022 15:49:50 +0200 | From | Tony Lindgren <> | Subject | Re: [PATCH 2/3] power: supply: cpcap-battery: Fix battery identification |
| |
Hi,
* Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> [221110 16:40]: > On 10.11.22 г. 18:05 ч., Sebastian Reichel wrote: > > Why do we care? > > > Because if we know the battery is genuine (or at least pretends to be :) ), > then we can read battery parameters from nvram, see patch 3/3. This will > allow us to charge HV LiPo batteries to 4.35V, using the full capacity.
Let's not enable charge voltages above 4.2V automatically at all unless the user chooses to set a higher charge voltage via sysfs manually.
We have had reports of bloated batteries if left connected to the charger at higher voltage than 4.2V. This seems to happen after connected for some weeks or months. AFAIK this happens both with Android and mainline kernel at higher voltages.
For more information, please see commit d4ee021c410f ("power: supply: cpcap-charger: Limit voltage to 4.2V for battery").
No objections for using the NVRAM to detect the battery max voltages though. That is as long as the default charge voltage does not go above 4.2V.
Regards,
Tony
| |