[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211008030529.223682-1-andrealmeid@collabora.com>
Date: Fri, 8 Oct 2021 00:05:28 -0300
From: André Almeida <andrealmeid@...labora.com>
To: rjw@...ysocki.net, lenb@...nel.org, linux-acpi@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel@...labora.com,
krisman@...labora.com, sebastian.reichel@...labora.com,
pgriffais@...vesoftware.com, hdegoede@...hat.com,
André Almeida <andrealmeid@...labora.com>
Subject: [PATCH 0/1] acpi: battery: Accept charges over the design capacity as full
Hi,
We have come across a battery that, when brand new, can go above the
reported maximum charge, leading to reports like this:
$ cat /sys/class/power_supply/BAT1/uevent
POWER_SUPPLY_NAME=BAT1
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_CHARGE_FULL_DESIGN=4160000
POWER_SUPPLY_CHARGE_FULL=4538000
POWER_SUPPLY_CHARGE_NOW=4539000
POWER_SUPPLY_CAPACITY=100
POWER_SUPPLY_CAPACITY_LEVEL=Full
[...]
And then userspace get confused by Unknown and some programs even say
"Charging: 100%". After applying this patch, kernel reports "Full",
which for practical reasons is true, even if the battery will charge a
bit more. After some time, the battery health degrades and the maximum
charge meets the design expectation. Ideally this would be fixed in the
battery firmware, but it's not always possible to do that.
André Almeida (1):
acpi: battery: Accept charges over the design capacity as full
drivers/acpi/battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.33.0
Powered by blists - more mailing lists