linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [Update][RFC][PATCH] PM / Runtime: Add sysfs switch for disabling device run-time PM
Date: Tue, 19 Jan 2010 21:32:26 +0100	[thread overview]
Message-ID: <201001192132.26765.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1001191035150.1437-100000@iolanthe.rowland.org>

On Tuesday 19 January 2010, Alan Stern wrote:
> On Mon, 18 Jan 2010, Rafael J. Wysocki wrote:
> 
> > > Ouch.  This does nearly the same thing as the power/level attribute in
> > > the USB subsystem, but in an incompatible and more complicated way.
> > > 
> > > The power/level attribute can contain either "on" or "auto", meaning
> > > that the device is always on or that it is subject to automatic runtime
> > > power management (autosuspend).
> > 
> > It looks like my "disable" is similar to "on", while my "enable" is similar to
> > "auto".  I can use "auto" and "on" just fine.
> 
> Good.
> 
> > > Changing the setting from "auto" to "on" merely does sets a flag and does
> > > pm_runtime_get_sync(); changing it from "on" to "auto" clears the flag and
> > > does pm_runtime_put_sync().
> > 
> > We can do it almost this way in general, although I think the flag should be
> > changed under the power.lock.
> 
> Yes.  I was using the device semaphore, but the power.lock is more 
> appropriate here.
> 
> > Updated patch is appended.
> 
> Why change the name from "level" to "runtime"?

Because it wouldn't be really obvious what "level" applied to.  For example,
some people might expect the values of "level" to correspond to PCI power
states for PCI devices and so on, so it might turn out to be confusing. 

> >  /*
> > + *	runtime - Report/change current runtime PM setting of the device
> > + *
> > + *	Runtime power management of a device can be blocked with the help of
> > + *	this attribute.  All devices have one of the following two values for
> > + *	the power/runtime file:
> > + *
> > + *	 + "auto\n" to allow the device to be power managed at run time;
> > + *	 + "on\n" to prevent the device from being power managemed at run time;
> 
> ---------------------------------------------------------------^^  typo

Ah, thanks

> Don't forget to add an entry to Documentation/ABI/testing/.

OK

Rafael

  reply	other threads:[~2010-01-19 20:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  0:29 [RFC][PATCH] PM / Runtime: Add sysfs switch for disabling device run-time PM Rafael J. Wysocki
2010-01-18 16:10 ` Alan Stern
2010-01-18 22:25   ` [Update][RFC][PATCH] " Rafael J. Wysocki
2010-01-19 15:40     ` Alan Stern
2010-01-19 20:32       ` Rafael J. Wysocki [this message]
2010-01-19 23:27         ` Rafael J. Wysocki
2010-01-20 15:09         ` Alan Stern
2010-01-20 21:09           ` Rafael J. Wysocki
2010-01-20 21:37             ` Alan Stern
2010-01-20 22:17               ` Rafael J. Wysocki
2010-01-20  2:51 ` [RFC][PATCH] " Greg KH
2010-01-20 20:55   ` Rafael J. Wysocki
2010-01-20 22:50     ` Greg KH
2010-01-21 22:57 ` [PATCH 0/2] " Rafael J. Wysocki
2010-01-21 22:59   ` [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device run-time PM (rev. 2) Rafael J. Wysocki
2010-01-22  3:02     ` Alan Stern
2010-01-22 20:56       ` Rafael J. Wysocki
2010-01-22 22:45         ` Alan Stern
2010-01-22 22:55           ` Rafael J. Wysocki
2010-01-23  3:22         ` Alan Stern
2010-01-23 12:14           ` Rafael J. Wysocki
2010-01-23 15:20             ` Alan Stern
2010-01-23 20:08               ` Rafael J. Wysocki
2010-02-04 22:46     ` Pavel Machek
2010-02-04 23:08       ` Rafael J. Wysocki
2010-02-05  6:27         ` Pavel Machek
2010-02-05 15:19           ` Alan Stern
2010-02-05  8:03       ` [linux-pm] " Nigel Cunningham
2010-01-21 23:00   ` [PATCH 2/2] PM: Document device power attributes in sysfs 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=201001192132.26765.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).