From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: Runtime PM status sysfs attribute
Date: Thu, 1 Jul 2010 23:13:41 +0200 [thread overview]
Message-ID: <201007012313.41826.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1007011621190.1303-100000@iolanthe.rowland.org>
On Thursday, July 01, 2010, Alan Stern wrote:
> On Thu, 1 Jul 2010, Dominik Brodowski wrote:
>
> > Alan,
> >
> > On Thu, Jul 01, 2010 at 01:16:31PM -0400, Alan Stern wrote:
> > > As runtime PM becomes more and more popular, it seems likely that
> > > people will want to know whether or not their devices are getting
> > > suspended. Or if not people, then programs like powertop.
> > >
> > > For that reason, it seems to make sense to build the runtime_status
> > > sysfs attribute even when CONFIG_PM_ADVANCED_DEBUG isn't enabled. Do
> > > you agree?
> >
> > good idea; haven't looked at any dependencies yet, though...
>
> Reading through the code shows there is a drawback: For subsystems that
> don't implement runtime PM, devices will always show up as "suspended".
> That's not going to be very useful, unfortunately.
>
> Still, for subsystems that _do_ implement runtime PM, there doesn't
> seem to be any other way to learn the current status of a device.
Perhaps we can rework the attribute to show "unknown" for devices that
have power.disable_depth > 0 ?
Rafael
next prev parent reply other threads:[~2010-07-01 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 17:16 Runtime PM status sysfs attribute Alan Stern
2010-07-01 18:54 ` Dominik Brodowski
2010-07-01 20:23 ` Alan Stern
2010-07-01 21:13 ` Rafael J. Wysocki [this message]
2010-07-01 23:16 ` Alan Stern
2010-07-02 5:34 ` Oliver Neukum
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=201007012313.41826.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@dominikbrodowski.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