From: Rajkumar Kasirajan <[email protected]> If battery is not identified while fg probe, mah_max_design gets initialized with unknown battery's charge full design. Reinitialize mah_max_design if battery is identified after fg probe.
Signed-off-by: Lee Jones <[email protected]> Signed-off-by: Rajkumar Kasirajan <[email protected]> Reviewed-by: Vijaya Kumar K-1 <[email protected]> Reviewed-by: Marcus COOPER <[email protected]> Reviewed-by: Olivier CLERGEAUD <[email protected]> Reviewed-by: Arun MURTHY <[email protected]> Reviewed-by: Rabin VINCENT <[email protected]> Tested-by: Rupesh KUMAR <[email protected]> Tested-by: Jonas ABERG <[email protected]> --- drivers/power/ab8500_fg.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/power/ab8500_fg.c b/drivers/power/ab8500_fg.c index 1a78116..0780b60 100644 --- a/drivers/power/ab8500_fg.c +++ b/drivers/power/ab8500_fg.c @@ -2090,7 +2090,8 @@ static int ab8500_fg_get_ext_psy_data(struct device *dev, void *data) case POWER_SUPPLY_PROP_TECHNOLOGY: switch (ext->type) { case POWER_SUPPLY_TYPE_BATTERY: - if (!di->flags.batt_id_received) { + if (!di->flags.batt_id_received && + di->bm->batt_id != BATTERY_UNKNOWN) { const struct abx500_battery_type *b; b = &(di->bm->bat_type[di->bm->batt_id]); -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
