[patch] ACPI battery driver emits POWER_SUPPLY_STATUS_FULL when power lead plugged in

Richard Hughes
2009-01-25T10:35:58Z

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Sat, 2009-01-24 at 19:37 +0300, Alexey Starikovskiy wrote:
> > I don't understand, why this guesswork over fully charged? If you cannot
> > detect fully charged, then *don't*.
> >
> > But if you must sinthesize it, and you can get an up-to-date "last full
> > capacity" from the battery when comparing, I suggest:
> >
> > full = (current capacity == last full capacity) && !charging &&
> > !discharging
> certainly, 90% is wrong, but 100% makes a day...

I think we need some sort of logic like this.

> > That would *still* be wrong in a few corner cases, but at least they're rare
> > corner cases that happens only when the pack recalibrates its fuel gauge.
> full in this case is not exact term. As any other term beside current_now and voltage_now.
> Capacity of the battery is estimated, so any number that was depending on it, is estimated too.

Right, never underestimate the brokenness of some people's batteries out
there. Coupled with broken BIOS's, some of the fix-up code in HAL is
'interesting'. I think all the fix-up code in HAL belongs in in the
kernel.

> > If there isn't a reliable way to detect the "full" state, just drop the
> > fully charged detection altogether.
> People are used to see "full" state of the battery. I think we could tolerate not-full-enough
> for sub-second interval instead of dropping full state altogether.

We shouldn't drop the full state, we should just add some metric like
above. What about something like the attached (untested) patch? Would
something this be accepted?

Richard.

[-- Attachment #2: acpi-battery-charged.patch --]
[-- Type: text/x-patch, Size: 1776 bytes --]

diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
index 65132f9..d400a11 100644
--- a/drivers/acpi/battery.c
+++ b/drivers/acpi/battery.c
@@ -138,6 +138,38 @@ static int acpi_battery_technology(struct acpi_battery *battery)

static int acpi_battery_get_state(struct acpi_battery *battery);

+static int acpi_battery_is_charged(struct acpi_battery *battery)
+{
+ int percentage;
+
+ /* either charging or discharging */
+ if (battery->state != 0)
+ return 0;
+
+ /* battery not reporting charge */
+ if (battery->full_charge_capacity == ACPI_BATTERY_VALUE_UNKNOWN ||
+ battery->capacity_now == 0)
+ return 0;
+
+ /* good batteries update full_charge as the batteries degrade */
+ if (battery->full_charge_capacity != ACPI_BATTERY_VALUE_UNKNOWN &&
+ battery->full_charge_capacity != 0) {
+ percentage = (100 * battery->capacity_now) / battery->full_charge_capacity;
+ if (percentage > 90)
+ return 1;
+ }
+
+ /* fallback to using design values for broken batteries */
+ if (battery->design_capacity != ACPI_BATTERY_VALUE_UNKNOWN &&
+ battery->design_capacity != 0) {
+ percentage = (100 * battery->capacity_now) / battery->design_capacity;
+ if (percentage > 90)
+ return 1;
+ }
+
+ return 0;
+}
+
static int acpi_battery_get_property(struct power_supply *psy,
enum power_supply_property psp,
union power_supply_propval *val)
@@ -155,7 +187,7 @@ static int acpi_battery_get_property(struct power_supply *psy,
val->intval = POWER_SUPPLY_STATUS_DISCHARGING;
else if (battery->state & 0x02)
val->intval = POWER_SUPPLY_STATUS_CHARGING;
- else if (battery->state == 0)
+ else if (acpi_battery_is_charged(battery))
val->intval = POWER_SUPPLY_STATUS_FULL;
else
val->intval = POWER_SUPPLY_STATUS_UNKNOWN;