From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] PM: allow for usage_count > 0 in pm_runtime_get()
Date: Wed, 2 Dec 2009 00:01:28 +0100 [thread overview]
Message-ID: <200912020001.28666.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0912011110210.2983-100000@iolanthe.rowland.org>
On Tuesday 01 December 2009, Alan Stern wrote:
> Rafael:
Hi,
> One other thing I just noticed. The power.timer_expires field is
> supposed to be nonzero when the timer is scheduled. But the code at
> the end of pm_schedule_suspend() doesn't check for the possibility that
> the expiration time might just happen to be 0. If it is, the
> timer_expires value should be bumped up to 1 before the mod_timer()
> call.
Do you mean something like the patch below?
Rafael
---
drivers/base/power/runtime.c | 2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6/drivers/base/power/runtime.c
===================================================================
--- linux-2.6.orig/drivers/base/power/runtime.c
+++ linux-2.6/drivers/base/power/runtime.c
@@ -625,6 +625,8 @@ int pm_schedule_suspend(struct device *d
goto out;
dev->power.timer_expires = jiffies + msecs_to_jiffies(delay);
+ if (!dev->power.timer_expires)
+ dev->power.timer_expires = 1;
mod_timer(&dev->power.suspend_timer, dev->power.timer_expires);
out:
next prev parent reply other threads:[~2009-12-01 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 16:35 [PATCH] PM: allow for usage_count > 0 in pm_runtime_get() Alan Stern
2009-11-30 21:06 ` Rafael J. Wysocki
2009-11-30 22:03 ` Alan Stern
2009-11-30 22:17 ` Rafael J. Wysocki
2009-12-01 23:09 ` Rafael J. Wysocki
2009-12-02 15:15 ` Alan Stern
2009-12-01 16:15 ` Alan Stern
2009-12-01 23:01 ` Rafael J. Wysocki [this message]
2009-12-02 15:13 ` Alan Stern
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=200912020001.28666.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/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