From: Lars-Peter Clausen <lars@metafoo.de>
To: steve.strobel@link-comm.com
Cc: alsa-devel@alsa-project.org, Steve Strobel <steve.strobel3@gmail.com>
Subject: Re: Driver for daisy-chained AD1938 audio codecs?
Date: Wed, 12 Oct 2011 11:13:24 +0200 [thread overview]
Message-ID: <4E955A34.3020608@metafoo.de> (raw)
In-Reply-To: <CAGrmWbz8v=NoLnQcmBUyiBX=p43UX2o0jOZyf6eWZJtWE9ygtA@mail.gmail.com>
On 10/11/2011 06:04 PM, Steve Strobel wrote:
> I am considering a Blackfin DSP hardware design which would need eight
> channels of audio input/output. I haven't been able to find a single
> audio codec with more than six input channels, so I am looking at
> daisy-chaining AD1938 codecs as described on page 19 of its datasheet
> [1].
>
> In the past I worked on a prototype that used two AD1938 chips on
> separate SPORT interfaces. It worked, but having to deal with two ALSA
> sound devices made the software relatively complicated (error
> recovery, synchronization, etc). It would be nice if all of the
> channels appeared as a single ALSA device. I believe that
> daisy-chained AD1938 chips would work that way, but I haven't found an
> ALSA driver for that configuration.
> Does such a driver already exist? Any suggestions for making one?
> Thanks for any input.
> Steve
> [1] - http://www.analog.com/static/imported-files/data_sheets/AD1938.pdf
Hi,
the existing driver should work fine, at least for daisy-chained ADCs.
Just setup the number of TDM slots using snd_soc_dai_set_tdm_slot. You'll
need to register one of the codecs as primary codec and the other as an
auxdev in your snd_soc_card structure.
- Lars
next prev parent reply other threads:[~2011-10-12 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 16:04 Driver for daisy-chained AD1938 audio codecs? Steve Strobel
2011-10-12 9:13 ` Lars-Peter Clausen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-11 18:23 Steve Strobel
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=4E955A34.3020608@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=steve.strobel3@gmail.com \
--cc=steve.strobel@link-comm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.