From: "Pali Rohár" <pali.rohar@gmail.com>
To: Paul Kocialkowski <contact@paulk.fr>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew F . Davis" <afd@ti.com>,
Sebastian Reichel <sre@kernel.org>,
Chris Lapa <chris@lapa.com.au>,
Matt Ranostay <mranostay@gmail.com>
Subject: Re: [PATCH 4/5] power: supply: bq27xxx: Look for status change on external power change
Date: Fri, 5 May 2017 10:04:58 +0200 [thread overview]
Message-ID: <20170505080458.GN15744@pali> (raw)
In-Reply-To: <20170430182727.24412-4-contact@paulk.fr>
On Sunday 30 April 2017 20:27:26 Paul Kocialkowski wrote:
> This introduces a dedicated status change work to look for power
> status change. It is triggered by external power change notifications
> and periodically retries detecting a power status change for 5 seconds.
>
> This is largely inspired by a similar mechanism from the sbs-battery
> driver.
What is reason/motivation for such change? It should be written in
commit message (to help understand; not only for me), because really I
do not know why such patch is needed.
> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> ---
> drivers/power/supply/bq27xxx_battery.c | 38 ++++++++++++++++++++++++++++++++--
> include/linux/power/bq27xxx_battery.h | 3 +++
> 2 files changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/power/supply/bq27xxx_battery.c b/drivers/power/supply/bq27xxx_battery.c
> index 926bd58344d9..cade00df6162 100644
> --- a/drivers/power/supply/bq27xxx_battery.c
> +++ b/drivers/power/supply/bq27xxx_battery.c
> @@ -1190,6 +1190,11 @@ static int bq27xxx_battery_status(struct bq27xxx_device_info *di,
> status = POWER_SUPPLY_STATUS_CHARGING;
> }
>
> + if (di->status_retry == 0 && di->status_change_reference != status) {
> + di->status_change_reference = status;
> + power_supply_changed(di->bat);
> + }
> +
> val->intval = status;
>
> return 0;
> @@ -1340,12 +1345,38 @@ static int bq27xxx_battery_get_property(struct power_supply *psy,
> return ret;
> }
>
> +static void bq27xxx_status_change(struct work_struct *work)
> +{
> + struct bq27xxx_device_info *di =
> + container_of(work, struct bq27xxx_device_info,
> + status_work.work);
> + union power_supply_propval val;
> + int ret;
> +
> + bq27xxx_battery_update(di);
> +
> + ret = bq27xxx_battery_status(di, &val);
> + if (ret < 0)
> + return;
> +
> + if (di->status_change_reference != val.intval) {
> + di->status_change_reference = val.intval;
> + power_supply_changed(di->bat);
> + }
> +
> + if (di->status_retry > 0) {
> + di->status_retry--;
> + schedule_delayed_work(&di->status_work, HZ);
> + }
> +}
> +
> static void bq27xxx_external_power_changed(struct power_supply *psy)
> {
> struct bq27xxx_device_info *di = power_supply_get_drvdata(psy);
>
> - cancel_delayed_work_sync(&di->poll_work);
> - schedule_delayed_work(&di->poll_work, 0);
> + cancel_delayed_work_sync(&di->status_work);
> + schedule_delayed_work(&di->status_work, HZ);
> + di->status_retry = 5;
> }
>
> int bq27xxx_battery_setup(struct bq27xxx_device_info *di)
> @@ -1357,8 +1388,10 @@ int bq27xxx_battery_setup(struct bq27xxx_device_info *di)
> psy_cfg.of_node = di->of_node;
>
> INIT_DELAYED_WORK(&di->poll_work, bq27xxx_battery_poll);
> + INIT_DELAYED_WORK(&di->status_work, bq27xxx_status_change);
> mutex_init(&di->lock);
> di->regs = bq27xxx_regs[di->chip];
> + di->status_change_reference = POWER_SUPPLY_STATUS_UNKNOWN;
>
> psy_desc = devm_kzalloc(di->dev, sizeof(*psy_desc), GFP_KERNEL);
> if (!psy_desc)
> @@ -1400,6 +1433,7 @@ void bq27xxx_battery_teardown(struct bq27xxx_device_info *di)
> poll_interval = 0;
>
> cancel_delayed_work_sync(&di->poll_work);
> + cancel_delayed_work_sync(&di->status_work);
>
> power_supply_unregister(di->bat);
>
> diff --git a/include/linux/power/bq27xxx_battery.h b/include/linux/power/bq27xxx_battery.h
> index 0a9af513165a..16d604681ace 100644
> --- a/include/linux/power/bq27xxx_battery.h
> +++ b/include/linux/power/bq27xxx_battery.h
> @@ -67,6 +67,9 @@ struct bq27xxx_device_info {
> int charge_design_full;
> unsigned long last_update;
> struct delayed_work poll_work;
> + struct delayed_work status_work;
> + int status_retry;
> + int status_change_reference;
> struct power_supply *bat;
> struct list_head list;
> struct mutex lock;
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-05-05 8:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 18:27 [PATCH 1/5] power: supply: bq27xxx: Pass of_node along to allow device-tree supply Paul Kocialkowski
2017-04-30 18:27 ` [PATCH 2/5] power: supply: bq27xxx: Register power supply with devm Paul Kocialkowski
2017-05-01 10:55 ` Sebastian Reichel
2017-05-07 17:43 ` Paul Kocialkowski
2017-04-30 18:27 ` [PATCH 3/5] power: supply: bq27xxx: Rename work structure member to poll_work Paul Kocialkowski
2017-04-30 18:27 ` [PATCH 4/5] power: supply: bq27xxx: Look for status change on external power change Paul Kocialkowski
2017-05-05 8:04 ` Pali Rohár [this message]
2017-05-07 17:37 ` Paul Kocialkowski
2017-05-08 13:04 ` Pali Rohár
2017-04-30 18:27 ` [PATCH 5/5] power: supply: bq27xxx: Correct supply status with current draw Paul Kocialkowski
2017-05-28 19:16 ` Pavel Machek
2017-05-31 16:55 ` Paul Kocialkowski
2017-05-31 17:32 ` Pavel Machek
2017-05-31 19:28 ` Paul Kocialkowski
2017-06-07 7:15 ` Paul Kocialkowski
2017-06-07 7:52 ` Pavel Machek
2017-06-07 15:20 ` Paul Kocialkowski
2017-06-07 19:50 ` Pavel Machek
2017-06-08 10:08 ` Paul Kocialkowski
2017-06-08 19:27 ` Sebastian Reichel
2017-06-09 6:16 ` Paul Kocialkowski
2017-06-13 12:14 ` Sebastian Reichel
[not found] <20170430203801.32357-1-contact@paulk.fr>
[not found] ` <20170430203801.32357-4-contact@paulk.fr>
2017-04-30 22:13 ` [PATCH 4/5] power: supply: bq27xxx: Look for status change on external power change Liam Breck
2017-05-01 10:45 ` Paul Kocialkowski
2017-05-01 18:22 ` Liam Breck
2017-05-01 18:34 ` Paul Kocialkowski
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=20170505080458.GN15744@pali \
--to=pali.rohar@gmail.com \
--cc=afd@ti.com \
--cc=chris@lapa.com.au \
--cc=contact@paulk.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mranostay@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).