From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Caleb Crome <caleb@crome.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Need general idea how to architect driver for multi-codec board
Date: Fri, 27 May 2011 02:27:56 +0100 [thread overview]
Message-ID: <20110527012756.GA26768@sirena.org.uk> (raw)
In-Reply-To: <BANLkTi=arRRqPEDS9S=-ynM_1d8N_A=d+w@mail.gmail.com>
On Thu, May 26, 2011 at 02:23:03PM -0700, Caleb Crome wrote:
> You previously indicated that I can instantiate multiple tlv320aic33
> drivers. Can you please give me a clue how to do that? I've been staring
> at this for days, and I still don't really get how it's supposed to be done.
With things like this it's always useful to look for other examples of
whatever it is you're doing - there's systems like speyside and rx51 in
mainline.
> fails because there are already controls with those names, like "Right PGA
> Mixer" etc. The alsa layer doesn't seem to allow multiple registrations of
> the same control. How do I give each instantiation a unique identifier?
Set up a snd_soc_codec_conf for each CODEC and assign a name_prefix to
it.
> Since the tlv320aic33 has about 80 controls, I'm going to end up with over
> 600 controls in alsamixer.
Yes.
next prev parent reply other threads:[~2011-05-27 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:31 Need general idea how to architect driver for multi-codec board Caleb Crome
2011-05-11 17:50 ` Mark Brown
2011-05-11 18:29 ` Caleb Crome
2011-05-11 22:44 ` Caleb Crome
2011-05-26 21:23 ` Caleb Crome
2011-05-27 1:27 ` Mark Brown [this message]
2011-05-27 21:36 ` Caleb Crome
2011-05-28 1:34 ` Mark Brown
2011-06-01 22:17 ` Caleb Crome
2011-06-03 8:48 ` Mark Brown
2011-06-03 23:35 ` Caleb Crome
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=20110527012756.GA26768@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=caleb@crome.org \
/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