[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 May 2010 19:39:54 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Matthew Garrett <mjg@...hat.com>
Cc: Brian Swetland <swetland@...gle.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Kevin Hilman <khilman@...prootsystems.com>,
Arve Hjønnevåg <arve@...roid.com>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>,
Tejun Heo <tj@...nel.org>, Oleg Nesterov <oleg@...hat.com>,
Paul Walmsley <paul@...an.com>, magnus.damm@...il.com,
mark gross <mgross@...ux.intel.com>,
Arjan van de Ven <arjan@...radead.org>,
Geoff Smith <geoffx.smith@...el.com>
Subject: Re: [PATCH 0/8] Suspend block api (version 6)
On Wed, May 05, 2010 at 06:33:37PM +0100, Matthew Garrett wrote:
> We seem to have ended up managing most of our PM infrastructure
> iteratively. If the concern is more about best practices than intrinsic
> incompatibilities, I'd lean towards us being better off merging this now
> and then working things out over the next few releases as we get a
> better understanding of the implications. The main thing that we have to
> get right in the short term is the userspace API - everything else is
> easier to fix up as we go along.
Right, the big issue for me is that there's likely to be some form of
userspace API visible for controlling this. I think I can keep it
mostly in-kernel for audio (by providing new APIs to mark some inputs
and outputs as being live during suspend) but need to check.
--
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