[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0902162141190.24097-100000@netrider.rowland.org>
Date: Mon, 16 Feb 2009 21:43:52 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Arjan van de Ven <arjan@...radead.org>
cc: "Rafael J. Wysocki" <rjw@...k.pl>,
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, Arjan van de Ven wrote:
> > 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).
> >
>
> shouldn't idle timeout etc be internal to the driver?
> Yes policy preferences / constraints makes sense to communicate,
> actual settings do not. For one they keep changing fast all the time
> anyway.
Sorry, I don't agree. A single driver may control many different kinds
of device -- it may not even be aware of the distinction! Consider the
SCSI disk driver: It has to handle both traditional rotating media and
solid-state disks. Clearly they should have different runtime PM
parameters. But the driver isn't in a good position to know what those
parameters should be.
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