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: Sat, 28 May 2011 09:34:16 +0800 [thread overview]
Message-ID: <20110528013355.GD5971@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <BANLkTinM_MigPxzY4WCBZhjRPwuV15b9gQ@mail.gmail.com>
On Fri, May 27, 2011 at 02:36:58PM -0700, Caleb Crome wrote:
> However, I'm still having problems getting the system set up with more than
> 2 channels. the rx51 and speyside don't quite do the same thing as far as I
> can tell: the rx51 is close -- it very nearly brings up the 'b' codec in
> the aic34, but I don't see how the TDM is set -- it appears to still be a
> stereo configuration.
There's an API for configuring TDM - snd_soc_dai_set_tdm slot.
> Do I need multiple snd_soc_dai_links when configuring? In hw_params, I only
Yes, you will. Or invent a new interface. The current APIs provide
point to point links between interfaces. If you're trying to do
something different then you'll need to extend the core to support what
you need.
> seem to get 1 codec dai_link, so I can't set the TDM slots there.
What makes you say that?
> Or are the extra codecs in the daisy chain considered 'aux' devices? I
No. aux devices have no digital links. In addition to looking at the
existing code you'll also find a lot of background information if you
look through the revision control history...
next prev parent reply other threads:[~2011-05-28 16:44 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
2011-05-27 21:36 ` Caleb Crome
2011-05-28 1:34 ` Mark Brown [this message]
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=20110528013355.GD5971@opensource.wolfsonmicro.com \
--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