[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 May 2010 21:15:36 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Matthew Garrett <mjg@...hat.com>,
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,
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 04:04:00PM -0400, Alan Stern wrote:
> P.S.: What happens if a suspend occurs while a call is in progress, so
> the codec is left powered up, and then the call ends? Does the system
> wake up at that point? Or does it stay suspended with the codec still
> powered, even though it's not needed any more?
Call end will be a system wake event in pretty much all systems,
userspace will want to do some work when the call goes away anyway.
Anyone who doesn't do that will see the CODEC stay powered, hopefully
the baseband will send it a nice mute signal instead of popping.
--
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