[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100806123515.GF31326@sirena.org.uk>
Date: Fri, 6 Aug 2010 13:35:15 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: david@...g.hm
Cc: Brian Swetland <swetland@...gle.com>, paulmck@...ux.vnet.ibm.com,
kevin granade <kevin.granade@...il.com>,
Arve Hj?nnev?g <arve@...roid.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Arjan van de Ven <arjan@...radead.org>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
pavel@....cz, florian@...kler.org, stern@...land.harvard.edu,
peterz@...radead.org, tglx@...utronix.de, alan@...rguk.ukuu.org.uk
Subject: Re: Attempted summary of suspend-blockers LKML thread
On Fri, Aug 06, 2010 at 01:07:47AM -0700, david@...g.hm wrote:
> on a given piece of hardware, does suspend always leave the same
> peripherals on, or do you sometimes power more things down than other
> times when suspending?
Different bits of hardware get powered down depending on current system
state. In the audio case (which is so far as I know the only case for
this sort of stuff that currently does anything in mainline) we'll keep
alive any active paths (that is, paths carrying live audio) between
endpoints in the audio subsystem which have been explicitly marked as
staying alive during suspend. Other audio paths will be powered down
when the system suspends. During normal run time only paths that are
active will be powered up.
--
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