From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Alsa-Devel Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [ASoc] TDM over one SSC channel on AT91 possible?
Date: Fri, 09 Nov 2007 12:54:29 +0000 [thread overview]
Message-ID: <1194612869.3180.412.camel@localhost.localdomain> (raw)
In-Reply-To: <4734465C.4020900@scottygroup.com>
On Fri, 2007-11-09 at 12:37 +0100, Friedrich Lobenstock wrote:
> Hello!
>
> The background: I'm just designing an ATMEL AT91RM9200 based board which
> got two TLV320AIC33 on board. It is either possible
> to hook up the two TLV320AIC33 to a separate SSC (synchronous serial
> control) channel each or use one SSC channel and configure it for TDM (time
> division multiplex) mode. There is already a driver for
> TLV320AIC14k/TLV320AIC2k in the development tree, so adding support for the
> TLV320AIC33 should be feasible.
>
Fwiw, TDM will save you a SSC port but will make similtanious use of
both codecs at different rates/formats difficult. It depends on your use
cases.
> What I'm not sure about is the fact if ASOC is prepared for using channels,
> especially SSC, in TDM mode. Is the core ASOC structure prepared to handle
> that?
It is for some platforms, but I think AT91 SSC and your codec will need
set_tdm_slot() implemented. Your machine driver will call set_tdm_slot
to configure codec/SSC slots.
>
> Would we be better off instantiate one drive twice each time with different
> parameters for the SSC channel?
>
I would instantiate one driver with 3 pcms. This would allow:-
pcm0: 2 channel, slot 0,1
pcm1: 2 channel, slot 2,3
pcm2: 4 channel, slot 0,1,2,3
Giving full flexibility for many use cases. The pcms would be mutually
exclusive (enforced by machine driver).
HTH
Liam
next prev parent reply other threads:[~2007-11-09 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 11:37 [ASoc] TDM over one SSC channel on AT91 possible? Friedrich Lobenstock
2007-11-09 12:54 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-21 17:15 Jason Fox
2011-06-24 6:07 ` 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=1194612869.3180.412.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.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;
as well as URLs for NNTP newsgroup(s).