[alsa-devel] [PATCH v2 2/6] ASoC: Allow the DAPM routes to be stored in device tree

Stephen Warren swarren at nvidia.com
Mon Dec 12 20:34:13 CET 2011

Mark Brown wrote at Saturday, December 10, 2011 5:49 AM:
> On Fri, Dec 09, 2011 at 01:52:00PM -0800, Stephen Warren wrote:
> > This would be a fair bit of work to implement, but what are your thoughts
> > on the binding example below? It's very strongly based on ASoC, but since
> > that's so strongly based on the HW, I think you can consider it a pure
> > HW model rather than something derived from the way the driver works.
> It's starting to get an idiomatic way of representing the external
> nodes, HDA is probably a good source of inspiration :)  We do need to
> have a think about the jacks, though - simple ones are fine but
> multifinction is more fun.

I just wanted to confirm that you're talking about multiple audio
functions here (e.g. mic+headphones), rather than mixing audio with
other features (e.g. s-video + line out). I don't think the latter has
any kind of representation in the kernel right now though? That said,
it might be a good idea to represent jacks outside any audio complex
DT node, so that they could host functionality of different types if
the HW does so...


More information about the Alsa-devel mailing list