[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0902161736210.21117-100000@netrider.rowland.org>
Date: Mon, 16 Feb 2009 17:40:10 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Arjan van de Ven <arjan@...radead.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Arve Hjønnevåg <arve@...roid.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Pavel Machek <pavel@....cz>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Matthew Garrett <mjg59@...f.ucam.org>,
mark gross <mgross@...ux.intel.com>,
"Woodruff, Richard" <r-woodruff2@...com>,
Uli Luckas <u.luckas@...d.de>,
Igor Stoppa <igor.stoppa@...ia.com>,
Brian Swetland <swetland@...gle.com>,
Len Brown <lenb@...nel.org>
Subject: Re: [RFD] Automatic suspend
On Mon, 16 Feb 2009, Rafael J. Wysocki wrote:
> OK, so I think there are two things that user space may be allowed to do as
> far as putting devices into low power states is concerned:
> * disable/enable the automatic power management of the device (provided that
> the driver supports the automatic PM)
Set the automatic PM parameters (idle timeout, state to go to, etc.).
And disabling automatic PM altogether (effectively the same as setting
the idle timeout to infinity).
> * check what power states devices are in.
What about situations where we want to distinguish between the power
state of the device itself and the power state of the link? For a disk
drive we may want to power the link on and off quite a lot, as that
has low latency, but spinning the disk up and down takes a long time
and so should have a longer idle-time value.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists