From: "Andrew F. Davis" <afd@ti.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Dan Murphy <dmurphy@ti.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/8] power: bq27xxx_battery: Cleanup health checking
Date: Fri, 24 Jul 2015 15:27:39 -0500 [thread overview]
Message-ID: <55B29FBB.8080500@ti.com> (raw)
In-Reply-To: <20150723162212.GI29125@pali>
On 07/23/2015 11:22 AM, Pali Rohár wrote:
> On Wednesday 22 July 2015 16:52:00 Andrew F. Davis wrote:
>> Reorganize the logic checking battery health and under temperature
>> condition checking.
>>
>> Signed-off-by: Andrew F. Davis <afd@ti.com>
>> ---
>> drivers/power/bq27xxx_battery.c | 62 +++++++++++++++++++++++++++--------------
>> 1 file changed, 41 insertions(+), 21 deletions(-)
>>
>> diff --git a/drivers/power/bq27xxx_battery.c b/drivers/power/bq27xxx_battery.c
>> index f148222..6775f65 100644
>> --- a/drivers/power/bq27xxx_battery.c
>> +++ b/drivers/power/bq27xxx_battery.c
>> @@ -54,6 +54,8 @@
>> #define BQ27XXX_FLAG_FC BIT(9)
>> #define BQ27XXX_FLAG_OTD BIT(14)
>> #define BQ27XXX_FLAG_OTC BIT(15)
>> +#define BQ27XXX_FLAG_UT BIT(14)
>> +#define BQ27XXX_FLAG_OT BIT(15)
>>
>> /* BQ27000 has different layout for Flags register */
>> #define BQ27000_FLAG_EDVF BIT(0) /* Final End-of-Discharge-Voltage flag */
>> @@ -624,10 +626,34 @@ static int bq27xxx_battery_read_pwr_avg(struct bq27xxx_device_info *di)
>> */
>> static int bq27xxx_battery_overtemp(struct bq27xxx_device_info *di, u16 flags)
>> {
>> - if (di->chip == BQ27500 || di->chip == BQ27541)
>> + if (di->chip == BQ27500 || di->chip == BQ27541 || di->chip == BQ27545)
>> return flags & (BQ27XXX_FLAG_OTC | BQ27XXX_FLAG_OTD);
>> + if (di->chip == BQ27530 || di->chip == BQ27421)
>> + return flags & BQ27XXX_FLAG_OT;
>> +
>> + return false;
>> +}
>> +
>> +/*
>> + * Returns true if a battery under temperature condition is detected
>> + */
>> +static int bq27xxx_battery_undertemp(struct bq27xxx_device_info *di, u16 flags)
>> +{
>> + if (di->chip == BQ27530 || di->chip == BQ27421)
>> + return flags & BQ27XXX_FLAG_UT;
>> +
>> + return false;
>> +}
>> +
>> +/*
>> + * Returns true if a low state of charge condition is detected
>> + */
>> +static int bq27xxx_battery_dead(struct bq27xxx_device_info *di, u16 flags)
>> +{
>> + if (di->chip == BQ27000 || di->chip == BQ27010)
>> + return flags & (BQ27000_FLAG_EDV1 | BQ27000_FLAG_EDVF);
>> else
>> - return flags & BQ27XXX_FLAG_OTC;
>> + return flags & (BQ27XXX_FLAG_SOC1 | BQ27XXX_FLAG_SOCF);
>> }
>>
>> /*
>> @@ -636,29 +662,23 @@ static int bq27xxx_battery_overtemp(struct bq27xxx_device_info *di, u16 flags)
>> */
>> static int bq27xxx_battery_read_health(struct bq27xxx_device_info *di)
>> {
>> - u16 tval;
>> + u16 flags;
>>
>> - tval = bq27xxx_read(di, BQ27XXX_REG_FLAGS, false);
>> - if (tval < 0) {
>> - dev_err(di->dev, "error reading flag register:%d\n", tval);
>> - return tval;
>> + flags = bq27xxx_read(di, BQ27XXX_REG_FLAGS, false);
>> + if (flags < 0) {
>> + dev_err(di->dev, "error reading flag register:%d\n", flags);
>> + return flags;
>> }
>>
>> - if (di->chip == BQ27000 || di->chip == BQ27010) {
>> - if (tval & BQ27000_FLAG_EDV1)
>> - tval = POWER_SUPPLY_HEALTH_DEAD;
>> - else
>> - tval = POWER_SUPPLY_HEALTH_GOOD;
>> - } else {
>> - if (tval & BQ27XXX_FLAG_SOCF)
>> - tval = POWER_SUPPLY_HEALTH_DEAD;
>> - else if (bq27xxx_battery_overtemp(di, tval))
>> - tval = POWER_SUPPLY_HEALTH_OVERHEAT;
>> - else
>> - tval = POWER_SUPPLY_HEALTH_GOOD;
>> - }
>> + /* Unlikely but important to return first */
>> + if (bq27xxx_battery_overtemp(di, flags))
>> + return POWER_SUPPLY_HEALTH_OVERHEAT;
>> + if (bq27xxx_battery_undertemp(di, flags))
>> + return POWER_SUPPLY_HEALTH_COLD;
>> + if (bq27xxx_battery_dead(di, flags))
>> + return POWER_SUPPLY_HEALTH_DEAD;
>
> Good candidates for "if (unlikely(...))" ?
>
I wasn't sure, but I don't see why not. Added.
Thanks,
Andrew
>>
>> - return tval;
>> + return POWER_SUPPLY_HEALTH_GOOD;
>> }
>>
>> static void bq27xxx_battery_update(struct bq27xxx_device_info *di)
>
next prev parent reply other threads:[~2015-07-24 20:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 21:51 [PATCH 0/8] Add support for additional bq27xxx devices Andrew F. Davis
2015-07-22 21:51 ` [PATCH 1/8] power: bq27x00_battery: Add manufacturer property Andrew F. Davis
2015-07-23 15:55 ` Dan Murphy
2015-07-23 15:59 ` Pali Rohár
2015-07-24 15:36 ` Sebastian Reichel
2015-07-22 21:51 ` [PATCH 2/8] power: bq27x00_battery: Fix lines over 80 characters long Andrew F. Davis
2015-07-23 16:00 ` Pali Rohár
2015-07-23 16:02 ` Dan Murphy
2015-07-24 15:36 ` Sebastian Reichel
2015-07-22 21:51 ` [PATCH 3/8] power: bq27x00_battery: Fix function parameter alignment Andrew F. Davis
2015-07-23 16:00 ` Pali Rohár
2015-07-23 16:02 ` Dan Murphy
2015-07-24 15:37 ` Sebastian Reichel
2015-07-22 21:51 ` [PATCH 4/8] power: bq27x00_battery: Checkpatch fixes Andrew F. Davis
2015-07-23 16:01 ` Pali Rohár
2015-07-23 16:04 ` Dan Murphy
2015-07-24 15:37 ` Sebastian Reichel
2015-07-22 21:51 ` [PATCH 5/8] power: bq27x00_battery: Renaming for consistency Andrew F. Davis
2015-07-23 16:12 ` Pali Rohár
[not found] ` <55B11E4C.6000006@ti.com>
2015-07-23 20:15 ` Pali Rohár
2015-07-23 20:56 ` Belisko Marek
2015-07-23 21:15 ` Pali Rohár
2015-07-23 21:36 ` Belisko Marek
2015-07-24 7:44 ` Pali Rohár
2015-07-22 21:51 ` [PATCH 6/8] power: bq27xxx_battery: Fix typos and change naming for state of charge functions Andrew F. Davis
2015-07-23 16:15 ` Pali Rohár
2015-07-23 17:19 ` Andrew F. Davis
2015-07-28 8:41 ` Pali Rohár
2015-07-22 21:51 ` [PATCH 7/8] power: bq27xxx_battery: Add support for additional bq27xxx family devices Andrew F. Davis
2015-07-23 16:20 ` Pali Rohár
2015-07-23 17:42 ` Andrew F. Davis
2015-07-28 8:43 ` Pali Rohár
2015-07-22 21:52 ` [PATCH 8/8] power: bq27xxx_battery: Cleanup health checking Andrew F. Davis
2015-07-23 16:22 ` Pali Rohár
2015-07-23 17:06 ` Joe Perches
2015-07-24 20:32 ` Andrew F. Davis
2015-07-24 20:27 ` Andrew F. Davis [this message]
2015-07-24 20:53 ` Pali Rohár
2015-07-23 16:27 ` [PATCH 0/8] Add support for additional bq27xxx devices Pali Rohár
2015-07-23 17:01 ` Andreas Dannenberg
2015-07-24 15:57 ` Andrew F. Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B29FBB.8080500@ti.com \
--to=afd@ti.com \
--cc=dbaryshkov@gmail.com \
--cc=dmurphy@ti.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sre@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).