[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 May 2010 21:09:41 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Matthew Garrett <mjg@...hat.com>
Cc: Alan Stern <stern@...land.harvard.edu>,
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>, rebecca@...roid.com
Subject: Re: [PATCH 0/8] Suspend block api (version 6)
On Wed, May 05, 2010 at 09:02:43PM +0100, Matthew Garrett wrote:
> One thing that's been mentioned before is that some vendors can swap the
> kernel much more easily than they can swap userspace, with the added
> constraint that they have little control over the bootloader. So if
> there's a userspace interface, it may well also be helpful to provide a
> kernel hook to allow the platform setup code to configure things. But
Oh, there's definitely going to be a platform-specific hook to configure
things. The platform needs to specify how the devices that make up the
audio subsystem are interconnected on the board, and that's done in
kernel since it depends on the hardware and can potentially lead to
physical damage if done incorrectly.
> otherwise, I think that'd work for audio - the only question is whether
> we need it to be more generic.
Agreed.
--
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