From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: kernel list <linux-kernel@vger.kernel.org>, linux-pm@vger.kernel.org
Subject: Re: 32-rc2: runtime_pm is noisy
Date: Tue, 13 Oct 2009 13:04:08 +0200 [thread overview]
Message-ID: <20091013110407.GC31984@elf.ucw.cz> (raw)
In-Reply-To: <200910062342.20910.rjw@sisk.pl>
On Tue 2009-10-06 23:42:20, Rafael J. Wysocki wrote:
> On Tuesday 06 October 2009, Pavel Machek wrote:
> > Hi!
> >
> > Maybe it is my config,
>
> Yes it is.
>
> > but pm_runtime_idle is a bit too noisy on
> > zaurus... ok, I do have pm_debug & pm_verbose
>
> Exactly.
>
> > set... but still, is it useful to print message about devices that do not
> > support it?
>
> It may be useful, because, for example, PCI can put devices without drivers
> into low power states using this mechanism.
>
> Still, perhaps we can drop the debug messages from __pm_runtime_idle().
>
> Care to send a patch?
Yep, something like this?
---
pm_runtime_idle is somewhat noisy. Remove debug prints.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
--- a/drivers/base/power/runtime.c
+++ b/drivers/base/power/runtime.c
@@ -51,8 +51,6 @@ static int __pm_runtime_idle(struct device *dev)
{
int retval = 0;
- dev_dbg(dev, "__pm_runtime_idle()!\n");
-
if (dev->power.runtime_error)
retval = -EINVAL;
else if (dev->power.idle_notification)
@@ -93,8 +91,6 @@ static int __pm_runtime_idle(struct device *dev)
wake_up_all(&dev->power.wait_queue);
out:
- dev_dbg(dev, "__pm_runtime_idle() returns %d!\n", retval);
-
return retval;
}
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-13 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 8:02 Pavel Machek
2009-10-06 21:42 ` Rafael J. Wysocki
2009-10-13 11:04 ` Pavel Machek [this message]
2009-10-28 22:07 ` Rafael J. Wysocki
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=20091013110407.GC31984@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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®