Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp10938592ybi; Thu, 25 Jul 2019 07:20:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqx6KIkyu++hNO8cj+KiPF4VON13CKSQVunaYBtwLFmefKkUo9kSA+o+55VcPxG//E/hrxOW X-Received: by 2002:a17:902:a514:: with SMTP id s20mr86466408plq.162.1564064448209; Thu, 25 Jul 2019 07:20:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564064448; cv=none; d=google.com; s=arc-20160816; b=ljvMvHqCstkgZLsG2wQidf9Hul+yFAKpsK49Rqk/a5nCCjwiYaRv9SeMBi8EwJeq+O GMJ0FAQEJ0GlyO1idOIcnbeqoDEmnUFOhcJR2v1uBVWPpvGLy5eTYDzcqwCUTE29F76Q OxYhxdiLkazfbXui9NO7bIxVJliYR00pRQ7ujAvtjuJ0PKpVF+CXOyT7wmS1z6jfDHeY QLYq89BkQqKWnaGuGoqMOl/n4CNosADru/jBvVG2Ljo2SSGsrQbkIfA1T0XUjpjHGD2B kdNqr8dFlZu8AkPK89WnCXFrJAA2igaJandwMnURfJe+0ttOEjlqbzx/gW9A2U2XK7K6 ejHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=9lpEIpCXHFfNmFCZkOjPjl+kYtFsIolKVOJaYVjNOcQ=; b=y8CYA4yRfhuc3KN67nu3TQG4xyeoVqi6TYSLnCbWs9DU7/Q+hgZ5aYYwCf8Lm1fAmy H0f8j0s54XgQWDbSG2SUBzIdUxFlOZ3j3O54FqlArpfOGYNFpRgp0y3Y3KeWbfM4uqgu ytmDlhUVxO21iWelPd0QqhZTx2j4160MdurX9XINxLILxrYjegbNOn+KX/Ljv7kZPkSr BDepGZF5BGZJTyrLJT89JTbfdMzCSJe+LIZYkugt4R3CzA3byjyRlerkwAOWpdW+fWqc yi3u1E7CeTIX6F4uK10JuW1CaxG9sLgUyncMqDKA8mKbABVAwYodiKKsAQaE/lyqqVQd gO1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=pClRb23D; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x9si19080790pfi.211.2019.07.25.07.20.33; Thu, 25 Jul 2019 07:20:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=pClRb23D; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389566AbfGYNkC (ORCPT + 99 others); Thu, 25 Jul 2019 09:40:02 -0400 Received: from mail-yw1-f68.google.com ([209.85.161.68]:46789 "EHLO mail-yw1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389523AbfGYNkB (ORCPT ); Thu, 25 Jul 2019 09:40:01 -0400 Received: by mail-yw1-f68.google.com with SMTP id z197so19242339ywd.13 for ; Thu, 25 Jul 2019 06:40:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9lpEIpCXHFfNmFCZkOjPjl+kYtFsIolKVOJaYVjNOcQ=; b=pClRb23DEELadcP2hvlaLTNBN9yBrISbS5y+2Sy58VGj4Na8t28OTw/3TBQxSeKiGa ya/pMORmmEz8ivB9+l0x9g+WjZdQpqbyWpPuVjw78499uHVw+bJFxkYRu0MRjvQxcoqG ttIEHjWh5R85T1aAoaUjRzo236BGJ9Gl2NMSilykUIVINmhDuhX8oCAhtlfWhLYzsI6c f6g43kIRS45FZ/q9owmTbNtyaBVbijlHYeSrZRY+MaHzS9r8LMV6QPc/F6pud16pN7gH O03xcv5jrziakvliPeRdtuDU0qkVKSERW+WK0HBkkPxeJQbNlVTC+lyZg+RegmnXrEqV BO+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9lpEIpCXHFfNmFCZkOjPjl+kYtFsIolKVOJaYVjNOcQ=; b=M1rXHSB2+yX7Qj8gFqK1KqdMdDme020fINwgRgVxu9AwbffT7fHsFR1JQkjNRqpt8H wOWo9LMQ3LvH63uju44EE0dJ2o7fSuRxeMMSV/W5nPxJExug7ni9jMdgrFI3lVMJTxdx D7DfSaw8OqMBWxycjnLLbpCKvmTk9cp6mX/beXPM80lnugZDyo/EiSi1eMLNLwsw53Gp 4MJOVdHTZjIqynTf3L2ZFxF5CYuibT3beprFWZ4/oHRYVNGN4KMQ2AELCKhVJpWdLBXy p/y71OQzhPq21GVFZ4J3baW+iSbN+QHdHHh77oNiHypoHVqjdzGl6Vm8qqIqsZ5kN72r mYRA== X-Gm-Message-State: APjAAAWAdgvV1so4oH+BPxPNcMqhVUFRpMN+vMN+NLmKKF0lCBwoKWFP C/T/brgJM2/hvyEx1YrSmR/8mYu0EfNoT3PSI8rqJw== X-Received: by 2002:a81:30c9:: with SMTP id w192mr52641306yww.371.1564062000403; Thu, 25 Jul 2019 06:40:00 -0700 (PDT) MIME-Version: 1.0 References: <1564043102-25298-1-git-send-email-rtresidd@electromag.com.au> In-Reply-To: <1564043102-25298-1-git-send-email-rtresidd@electromag.com.au> From: Guenter Roeck Date: Thu, 25 Jul 2019 06:39:48 -0700 Message-ID: Subject: Re: [PATCH 1/1] power/supply/sbs-battery: Fix confusing battery status when idle or empty To: Richard Tresidder Cc: Sebastian Reichel , Enric Balletbo i Serra , Nick Crews , andrew.smirnov@gmail.com, Guenter Roeck , david@lechnology.com, Thomas Gleixner , Kate Stewart , Greg Kroah-Hartman , rfontana@redhat.com, allison@lohutok.net, baolin.wang@linaro.org, Linux PM list , linux-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 25, 2019 at 1:25 AM Richard Tresidder wrote: > > When a battery or batteries in a system are in parallel then one or more > may not be providing any current to the system. > This fixes an incorrect > status indication of FULL for the battery simply because it wasn't > discharging at that point in time. > The battery will now be flagged as IDLE. > Have also added the additional check for the battery FULL DISCHARGED flag > which will now flag a status of EMPTY. > > Signed-off-by: Richard Tresidder > --- > > Notes: > power/supply/sbs-battery: Fix confusing battery status when idle or empty > > When a battery or batteries in a system are in parallel then one or more > may not be providing any current to the system. > This fixes an incorrect > status indication of FULL for the battery simply because it wasn't > discharging at that point in time. > The battery will now be flagged as IDLE. > Have also added the additional check for the battery FULL DISCHARGED flag > which will now flag a status of EMPTY. > > drivers/power/supply/power_supply_sysfs.c | 3 ++- > drivers/power/supply/sbs-battery.c | 28 ++++++++++++++-------------- > include/linux/power_supply.h | 2 ++ > 3 files changed, 18 insertions(+), 15 deletions(-) > > diff --git a/drivers/power/supply/power_supply_sysfs.c b/drivers/power/supply/power_supply_sysfs.c > index ce6671c..68ec49d 100644 > --- a/drivers/power/supply/power_supply_sysfs.c > +++ b/drivers/power/supply/power_supply_sysfs.c > @@ -51,7 +51,8 @@ > }; > > static const char * const power_supply_status_text[] = { > - "Unknown", "Charging", "Discharging", "Not charging", "Full" > + "Unknown", "Charging", "Discharging", "Not charging", "Full", > + "Empty", "Idle" > }; > > static const char * const power_supply_charge_type_text[] = { > diff --git a/drivers/power/supply/sbs-battery.c b/drivers/power/supply/sbs-battery.c > index ea8ba3e..e6c636c 100644 > --- a/drivers/power/supply/sbs-battery.c > +++ b/drivers/power/supply/sbs-battery.c > @@ -294,14 +294,10 @@ static int sbs_status_correct(struct i2c_client *client, int *intval) > > ret = (s16)ret; > > - /* Not drawing current means full (cannot be not charging) */ > - if (ret == 0) > - *intval = POWER_SUPPLY_STATUS_FULL; > - > - if (*intval == POWER_SUPPLY_STATUS_FULL) { > - /* Drawing or providing current when full */ > - if (ret > 0) > - *intval = POWER_SUPPLY_STATUS_CHARGING; > + if (*intval == POWER_SUPPLY_STATUS_DISCHARGING) { > + /* Charging indicator not set in battery */ > + if (ret == 0) > + *intval = POWER_SUPPLY_STATUS_IDLE; But doesn't the above already indicate that it _is_ discharging ? > else if (ret < 0) > *intval = POWER_SUPPLY_STATUS_DISCHARGING; This doesn't make sense. *intval is already set to POWER_SUPPLY_STATUS_DISCHARGING in this situation. > } > @@ -424,10 +420,12 @@ static int sbs_get_battery_property(struct i2c_client *client, > > if (ret & BATTERY_FULL_CHARGED) > val->intval = POWER_SUPPLY_STATUS_FULL; > - else if (ret & BATTERY_DISCHARGING) > - val->intval = POWER_SUPPLY_STATUS_DISCHARGING; > - else > + else if (ret & BATTERY_FULL_DISCHARGED) > + val->intval = POWER_SUPPLY_STATUS_EMPTY; > + else if (!(ret & BATTERY_DISCHARGING)) > val->intval = POWER_SUPPLY_STATUS_CHARGING; > + else > + val->intval = POWER_SUPPLY_STATUS_DISCHARGING; > > sbs_status_correct(client, &val->intval); > > @@ -781,10 +779,12 @@ static void sbs_delayed_work(struct work_struct *work) > > if (ret & BATTERY_FULL_CHARGED) > ret = POWER_SUPPLY_STATUS_FULL; > - else if (ret & BATTERY_DISCHARGING) > - ret = POWER_SUPPLY_STATUS_DISCHARGING; > - else > + else if (ret & BATTERY_FULL_DISCHARGED) > + ret = POWER_SUPPLY_STATUS_EMPTY; > + else if (!(ret & BATTERY_DISCHARGING)) > ret = POWER_SUPPLY_STATUS_CHARGING; > + else > + ret = POWER_SUPPLY_STATUS_DISCHARGING; > > sbs_status_correct(chip->client, &ret); > > diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h > index 28413f7..c9f3347 100644 > --- a/include/linux/power_supply.h > +++ b/include/linux/power_supply.h > @@ -37,6 +37,8 @@ enum { > POWER_SUPPLY_STATUS_DISCHARGING, > POWER_SUPPLY_STATUS_NOT_CHARGING, > POWER_SUPPLY_STATUS_FULL, > + POWER_SUPPLY_STATUS_EMPTY, > + POWER_SUPPLY_STATUS_IDLE, > }; > > /* What algorithm is the charger using? */ > -- > 1.8.3.1 >