From: Attila RS <avgrind911@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: soc multi chip support
Date: Mon, 17 May 2010 10:29:57 -0700 [thread overview]
Message-ID: <AANLkTinN_2faDOB01eaRjorFoLI6E_vVXpBBO-XZvrqH@mail.gmail.com> (raw)
In-Reply-To: <1273866350.3069.30.camel@odin>
Thanks. I pulled down the multi-component branch and am looking through it.
I started with TI's latest PSP, which is based on 2.6.32, but as expected
there are numerous changes between it and the the multi-component branch.
Are there any devices in the multi-component branch that are using multiple
audio codecs? Just looking for a good example.
Attila
On Fri, May 14, 2010 at 12:45 PM, Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> On Fri, 2010-05-14 at 10:30 -0700, Attila RS wrote:
> > Hi,
> >
> > I have 2 of the same audio codecs connected to an omap (each codec has
> it's
> > own i2c address and each has its own mcbsp channel). I can configure and
> use
> > each one individually, but have not found a way to configure both at the
> > same time so that each codec shows up as an alsa device. I did some
> > searching and found that this may not be supported yet. Is that the case
> or
> > has anyone done this yet or is working on it?
>
> ASoC multi-component support is working well, although not yet merged
> upstream yet.
>
> Please pull the multi-component branch here for support :-
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lrg/asoc-2.6.git
>
> Liam
> --
> Freelance Developer, SlimLogic Ltd
> ASoC and Voltage Regulator Maintainer.
> http://www.slimlogic.co.uk
>
>
next prev parent reply other threads:[~2010-05-17 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 17:30 soc multi chip support Attila RS
2010-05-14 19:45 ` Liam Girdwood
2010-05-17 17:29 ` Attila RS [this message]
2010-05-17 20:16 ` Liam Girdwood
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=AANLkTinN_2faDOB01eaRjorFoLI6E_vVXpBBO-XZvrqH@mail.gmail.com \
--to=avgrind911@gmail.com \
--cc=alsa-devel@alsa-project.org \
--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).