From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Peter@alsa-project.org,
Ujfalusi <peter.ujfalusi@nokia.com>
Subject: Re: [PATCH] ASoC: Add optional pointer to machine audio routes to snd_soc_card
Date: Mon, 20 Dec 2010 09:24:28 +0000 [thread overview]
Message-ID: <1292837068.3304.2.camel@odin> (raw)
In-Reply-To: <20101217223709.GA28118@sirena.org.uk>
On Fri, 2010-12-17 at 22:37 +0000, Mark Brown wrote:
> On Fri, Dec 17, 2010 at 07:39:40PM +0200, Jarkko Nikula wrote:
> > This is targeted mostly to cross-device setups where single audio map
> > defining routes around and between the codecs looks cleaner than defining
> > and registering maps to each codec separately from machine init callbacks.
> >
> > This could be also used to reduce simple machine init callbacks where only
> > snd_soc_dapm_add_routes and snd_soc_dapm_sync are called. However, this does
> > work only if the widgets names are unique in the system.
> >
> > Idea of common audio map came from Peter Ujfalusi <peter.ujfalusi@nokia.com>.
>
> Good idea. We should probably just do this for CODECs as well, they're
> often doing similar boiler plate type stuff.
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-12-20 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 17:39 [PATCH] ASoC: Add optional pointer to machine audio routes to snd_soc_card Jarkko Nikula
2010-12-17 22:37 ` Mark Brown
2010-12-20 9:24 ` Liam Girdwood [this message]
2010-12-20 11:22 ` Peter Ujfalusi
2010-12-20 12:02 ` Mark Brown
2010-12-21 7:42 ` Peter Ujfalusi
2010-12-21 16:29 ` Mark Brown
2010-12-20 12:17 ` Jarkko Nikula
2010-12-21 7:30 ` Peter Ujfalusi
2010-12-21 8:16 ` Jarkko Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1292837068.3304.2.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=Peter@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@nokia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox