From: Shaohua Li <shaohua.li@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm <linux-pm@lists.osdl.org>
Subject: Re: [RFC] dynamic device power management proposal
Date: Tue, 20 Mar 2007 09:06:15 +0800 [thread overview]
Message-ID: <1174352775.1665.4.camel@sli10-conroe.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0703191135360.14222-100000@iolanthe.rowland.org>
On Mon, 2007-03-19 at 23:44 +0800, Alan Stern wrote:
> On Mon, 19 Mar 2007, Shaohua Li wrote:
>
> > Runtime device power management or dynamic device power management
> > (dpm).
> >
> > Why dpm:
> > 1. put an idle device into low power state to save power
> > 2. speed up S3/S4. In resume time, we could resume devices only
> as
> > the devices are used. In suspend time, we could skip
> suspended
> > devices. (suspend/resume a device equals to change device
> state)
> >
> > Basically we need device driver support, a kernel framework and a
> policy
> > (determine when to change a device’s power state).
>
> A lot of development along these lines has already been going on in
> the
> USB subsystem. It isn't complete yet, but a lot of the ideas you
> raise
> have already been implemented.
Ok, I'll look at the USB implementation. On the other hand, I think
there should be a generic framework for all bus types.
> > 4. policy position. The idea is policy resides on userspace.
> Dpm
> > framework exports device’s busy timestamp, state info,
> > dependence setting to userspace. According to the info,
> policy
> > suspends a device in specific time. Resuming a device is
> > directly done by dpm framework in kernel.
>
> In USB, we export the idle-time delay value (device is autosuspended
> when it has been idle longer than this) and an administrative
> power-level
> atttribute: on, auto, or suspend. When set to "on" the device will
> not
> autosuspend; when set to "auto" the device will autosuspend and
> autoresume
> according to the delay setting; when set to "suspend" the device will
> be
> suspended and will not autoresume.
Doing suspend in the driver level isn't flexible. See in the case 'close
console if keyboard/mouse hasn't input', it's hard to do in a driver.
Thanks,
Shaohua
_______________________________________________
linux-pm mailing list
linux-pm@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/linux-pm
next prev parent reply other threads:[~2007-03-20 1:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 9:08 [RFC] dynamic device power management proposal Shaohua Li
2007-03-19 15:44 ` Alan Stern
2007-03-20 1:06 ` Shaohua Li [this message]
2007-03-20 14:58 ` Alan Stern
2007-03-21 1:43 ` Shaohua Li
2007-03-21 14:44 ` Alan Stern
2007-03-22 4:42 ` Len Brown
2007-03-22 11:56 ` Jim Gettys
2007-03-22 19:28 ` David Brownell
2007-03-22 13:20 ` Pavel Machek
2007-03-22 13:44 ` Oliver Neukum
2007-03-22 13:56 ` Pavel Machek
2007-03-22 14:18 ` Oliver Neukum
2007-03-22 14:22 ` Pavel Machek
2007-03-22 14:26 ` Oliver Neukum
2007-03-22 14:35 ` Pavel Machek
2007-03-22 19:41 ` David Brownell
2007-03-22 19:58 ` David Brownell
2007-03-20 18:30 ` Pavel Machek
2007-03-21 1:34 ` Shaohua Li
2007-03-21 15:21 ` Amit Kucheria
2007-03-21 21:49 ` Dmitry Krivoschekov
2007-03-21 22:54 ` Pavel Machek
2007-03-21 21:39 ` Pavel Machek
2007-03-22 3:09 ` Shaohua Li
2007-03-22 13:13 ` Pavel Machek
2007-03-22 19:20 ` David Brownell
2007-03-22 20:32 ` Alan Stern
2007-03-22 20:02 ` David Brownell
2007-03-22 22:10 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 20:19 Scott E. Preece
2007-03-21 21:45 ` Pavel Machek
2007-03-26 13:53 ` Amit Kucheria
2007-03-22 13:39 Scott E. Preece
2007-03-22 13:48 ` Oliver Neukum
2007-03-22 14:01 ` Pavel Machek
2007-03-22 14:45 ` Alan Stern
2007-03-22 18:53 ` David Brownell
2007-03-22 19:05 Scott E. Preece
2007-03-27 12:05 ` Pavel Machek
2007-03-27 12:19 ` Oliver Neukum
2007-03-22 19:18 Scott E. Preece
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=1174352775.1665.4.camel@sli10-conroe.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=linux-pm@lists.osdl.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