From: Jarkko Nikula <jhnikula@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC] ASoC: multi-component: Add optional kcontrol prefix name for a DAI link
Date: Mon, 16 Aug 2010 13:53:28 +0300 [thread overview]
Message-ID: <20100816135328.077b5ea3.jhnikula@gmail.com> (raw)
In-Reply-To: <20100816100705.GA3276@rakim.wolfsonmicro.main>
On Mon, 16 Aug 2010 11:07:05 +0100
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Mon, Aug 16, 2010 at 10:29:30AM +0300, Jarkko Nikula wrote:
> > This optional kcontrol_prefix allows to specify unique prefix for ALSA
> > control names for each DAI link. This makes possible to have a sound card
> > configuration with multiple DAIs and each of them using the same codec
> > driver without name collision.
>
> This isn't going to work in general - consider what happens for CODECs
> with multiple DAIs, or for devices with no DAIs at all like external
> analogue amps. We do need to do this but it probably needs to be per
> CODEC rather than per link I fear.
Yeah, true, this is not going to work if there are multiple amplifiers
that are registered for a same link.
Multi-DAI codecs are not so clear to me. I thought codecs are exporting
different controls for different DAIs? Like "foo Playback Volume" and
"bar Playback Volume".
But anyway, I'll try to look some better idea.
--
Jarkko
next prev parent reply other threads:[~2010-08-16 10:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 7:29 [RFC] ASoC: multi-component: Add optional kcontrol prefix name for a DAI link Jarkko Nikula
2010-08-16 10:07 ` Mark Brown
2010-08-16 10:53 ` Jarkko Nikula [this message]
2010-08-16 11:09 ` Mark Brown
2010-08-19 11:44 ` Jarkko Nikula
2010-08-19 13:54 ` Mark Brown
2010-08-19 15:20 ` Jarkko Nikula
2010-08-20 8:51 ` Jarkko Nikula
2010-08-23 14:46 ` Jarkko Nikula
2010-08-23 15:21 ` Mark Brown
2010-08-24 7:23 ` Jarkko Nikula
2010-08-24 10:10 ` Mark Brown
2010-08-25 10:59 ` Jarkko Nikula
2010-08-26 13:32 ` Mark Brown
2010-08-30 11:17 ` Jarkko Nikula
2010-09-02 14:25 ` Mark Brown
2010-09-03 7:55 ` Jarkko Nikula
2010-09-03 9:33 ` Mark Brown
2010-09-03 10:00 ` Liam Girdwood
2010-09-03 11:20 ` 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=20100816135328.077b5ea3.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).