From: Nitish Ambastha <nitish.a@samsung.com>
To: rjw@rjwysocki.net, pavel@ucw.cz, len.brown@intel.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: cpgs@samsung.com, nitish.a@samsung.com, nits.ambastha@gmail.com
Subject: [PATCH 1/1] kernel/power/autosleep.c: check for pm_suspend() return before queueing suspend again
Date: Mon, 29 Jun 2015 18:04:57 +0530 [thread overview]
Message-ID: <1435581297-20271-1-git-send-email-nitish.a@samsung.com> (raw)
Prevent tight loop for suspend-resume when some
devices failed to suspend
If some devices failed to suspend, we monitor this
error in try_to_suspend(). pm_suspend() is already
an 'int' returning function, how about checking return
from pm_suspend() before queueing suspend again?
For devices which do not register for pending events,
this will prevent tight loop for suspend-resume in
suspend abort scenarios due to device suspend failures
Signed-off-by: Nitish Ambastha <nitish.a@samsung.com>
---
kernel/power/autosleep.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/kernel/power/autosleep.c b/kernel/power/autosleep.c
index 9012ecf..3923148 100644
--- a/kernel/power/autosleep.c
+++ b/kernel/power/autosleep.c
@@ -26,6 +26,7 @@ static struct wakeup_source *autosleep_ws;
static void try_to_suspend(struct work_struct *work)
{
unsigned int initial_count, final_count;
+ int error = 0;
if (!pm_get_wakeup_count(&initial_count, true))
goto out;
@@ -45,10 +46,20 @@ static void try_to_suspend(struct work_struct *work)
if (autosleep_state >= PM_SUSPEND_MAX)
hibernate();
else
- pm_suspend(autosleep_state);
+ error = pm_suspend(autosleep_state);
mutex_unlock(&autosleep_lock);
+ if (error) {
+ /*
+ * If some devices failed to suspend, its better to wait
+ * to prevent system from trying to suspend in tight loop
+ */
+ pr_info("PM: suspend returned (%d)\n", error);
+ schedule_timeout_uninterruptible(HZ / 2);
+ goto out;
+ }
+
if (!pm_get_wakeup_count(&final_count, false))
goto out;
--
1.7.9.5
next reply other threads:[~2015-06-29 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 12:34 Nitish Ambastha [this message]
2015-06-29 9:21 ` Pavel Machek
2015-06-29 18:54 ` [PATCHv2 " Nitish Ambastha
2015-06-29 19:56 ` Rafael J. Wysocki
2015-06-29 20:07 ` Rafael J. Wysocki
2015-06-30 19:22 ` Nitish Ambastha
2015-06-30 20:01 ` Rafael J. Wysocki
2015-07-04 18:06 ` Nitish Ambastha
2015-07-13 20:08 ` [PATCHv3 " Nitish Ambastha
2015-07-13 20:24 ` Nitish Ambastha
2015-07-13 23:43 ` Rafael J. Wysocki
2015-07-14 4:04 ` Nitish Ambastha
2015-07-15 22:29 ` Rafael J. Wysocki
2015-07-22 20:11 ` Nitish Ambastha
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=1435581297-20271-1-git-send-email-nitish.a@samsung.com \
--to=nitish.a@samsung.com \
--cc=cpgs@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nits.ambastha@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®