alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Crome <caleb@crome.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Proposed changes to soc core to allow multiple codecs bound together on a single bus
Date: Thu, 9 Jun 2011 12:23:22 -0700	[thread overview]
Message-ID: <BANLkTimCfF15KFMHrsCS5AZpTUgT8mg=Xw@mail.gmail.com> (raw)
In-Reply-To: <20110606105115.GB12783@opensource.wolfsonmicro.com>

Thanks for the feedback Liam and Mark.

I'll take a look at the PCM changes, that would be great if it'll work for
my situation, because something similar to what i was thinking would require
major changes (at least as far as my feble brain is concerned).

I've checked out Liam's PCM code base, but haven't taken a look yet -- since
my driver's now more-or-less working, I'm actually testing out my board...

Thanks,
  -Caleb




On Mon, Jun 6, 2011 at 3:51 AM, Mark Brown <
broonie@opensource.wolfsonmicro.com> wrote:

> On Fri, Jun 03, 2011 at 05:04:12PM -0700, Caleb Crome wrote:
>
> > static char *my_codec_dais[] = {
> >      "tlv320aic3x-hifi.0",   <---- in this case, the '.0'
> >      "tlv320aic3x-hifi.1",    ---- means that it's slot 0
> >      "tlv320aic3x-hifi.2",    ---- on the TDM bus.
> >      "tlv320aic3x-hifi.3",
> > };
> > static char *my_codec_names[] = {
> >      "tlv320aic3x-codec.2-0018", <--- codec on i2c bus 2, addr 0x18
> >      "tlv320aic3x-codec.2-0019", <--- codec on i2c bus 2, addr 0x19
> >      "tlv320aic3x-codec.2-001a", <--- codec on i2c bus 2, addr 0x1a
> >      "tlv320aic3x-codec.2-001b", <--- codec on i2c bus 2, addr 0x1b
> > };
>
> I don't like the need to line the two arrays up, and the DAI names
> really ought to be enough anyway (this applies in general, not just
> here).
>
> > The core will parse the dai name for the slot order, and pass it on to
> the
> > codec during hw_params.  Then the codec can properly set the TDM slot on
> the
> > hardware interface.
>
> No, the machine driver needs to own the TDM configuration.  We need to
> have the flexibiltiy for the system to use arbatrary arrangements for
> things like buses with more than two devices on them and we need to be
> able to cope with random layouts of the channels (for example, all the
> left channels on one device, all the right channels on another device).
> We also need to be able to change this dynamically at runtime depending
> on the current needs of the system.
>

      reply	other threads:[~2011-06-09 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04  0:04 Proposed changes to soc core to allow multiple codecs bound together on a single bus Caleb Crome
2011-06-06 10:47 ` Liam Girdwood
2011-06-06 10:51 ` Mark Brown
2011-06-09 19:23   ` Caleb Crome [this message]

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='BANLkTimCfF15KFMHrsCS5AZpTUgT8mg=Xw@mail.gmail.com' \
    --to=caleb@crome.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).