From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Liam Breck <kernel@networkimprov.net>,
"Mark A . Greer" <mgreer@animalcreek.com>,
linux-pm@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCHv2 0/2] Two bq24190 PM improvments
Date: Mon, 30 Jan 2017 16:02:08 -0800 [thread overview]
Message-ID: <20170131000210.5442-1-tony@atomide.com> (raw)
Hi,
Here's a repost of the two bq24190 patches rebased against current
power-supply tree.
Regards,
Tony
Changes from v1:
- Call pm_runtime_dont_use_autosuspend() and pm_runtime_put_sync()
unconditionally in bq24190_remove() as suggested by Liam
Changes from earlier set:
- Separated from Liam's changes that are now in the power-supply tree
- Moved bdi->initialized before devm_request_threaded_irq() as suggested
by Liam
- Added missing return value check for pm_runtime_get() as suggested by
Liam
- Updated against current power-supply tree, mostly for the probe error
handling
Tony Lindgren (2):
power: bq24190_charger: Check the interrupt status on resume
power: bq24190_charger: Use PM runtime autosuspend
drivers/power/supply/bq24190_charger.c | 211 +++++++++++++++++++++++++--------
1 file changed, 161 insertions(+), 50 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-31 0:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 0:02 Tony Lindgren [this message]
2017-01-31 0:02 ` [PATCH 1/2] power: bq24190_charger: Check the interrupt status on resume Tony Lindgren
2017-02-03 0:32 ` Liam Breck
2017-01-31 0:02 ` [PATCH 2/2] power: bq24190_charger: Use PM runtime autosuspend Tony Lindgren
2017-01-31 0:14 ` Liam Breck
2017-01-31 0:36 ` Tony Lindgren
2017-02-03 1:43 ` Liam Breck
2017-02-03 3:44 ` Tony Lindgren
2017-02-03 10:38 ` Liam Breck
2017-02-03 18:54 ` Tony Lindgren
2017-02-03 21:00 ` Liam Breck
2017-02-03 21:17 ` Tony Lindgren
2017-02-03 21:44 ` Liam Breck
2017-02-03 22:28 ` Tony Lindgren
2017-02-04 0:23 ` Liam Breck
2017-02-07 16:01 ` Tony Lindgren
2017-02-07 18:20 ` Liam Breck
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=20170131000210.5442-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=kernel@networkimprov.net \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgreer@animalcreek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.