alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: alsa-devel@alsa-project.org
Subject: Re: ASoC: Hooking a TI CODEC to a i.MX27 MCU
Date: Fri, 28 May 2010 07:55:19 +0200	[thread overview]
Message-ID: <4BFF5AC7.3060409@eukrea.com> (raw)
In-Reply-To: <20100528020621.GA12531@www.longlandclan.yi.org>

Hi Stuart,

Le 28/05/2010 04:06, Stuart Longland a écrit :
> I'll have a look at the Eukrea CPUIMX27 and baseboard SoC support in a
> moment, since it looks very similar to what we're doing (in that it's a
> TI I²S CODEC hooked to an i.MX27 on SSI4) ... this might reveal clues
> as to what I'm doing wrong.

we are using the TLV320AIC23B codec in master mode on the 
CPUIMX27/MBIMX27 (and did the same on an other board using a TLV3204 as 
a master with a 12MHz oscillator on its MCLK: for this one, it's 
necessary to configure several dozens of registers through I2C to get it 
running)

The TLV3204 is wired this way :
- MCK = 12MHz ocillator
- BCLK (pin2) = PC19 (SSI4_CLK) (TLV output / IMX in)
- WCLK (pin3) = PC16 (SSI4_FS) (TLV output / IMX in)
- DIN/MFP1 (pin4) = PC18 (SSI4_TXDAT) (TLV input / IMX out)
- DOUT/MFP2 (pin5) = PC17 (SSI4_RXDAT) (TLV output / IMX in)
- SPI_SELECT (pin12) = pull down to select I2C mode
- SCL & SDA (pins 9 & 10) = I2C2
all the interface between i.MX & TLV is powered in 1.8V.

I'll try to find our I2C init sequence and send it to you as this was 
the hardest part of the thing to get the codec running.

Eric
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-05-28  5:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24  7:49 ASoC: Hooking a TI CODEC to a i.MX27 MCU Stuart Longland
2010-05-24 10:49 ` Liam Girdwood
2010-05-25  0:41   ` Stuart Longland
2010-05-25  2:26     ` Stuart Longland
2010-05-25  3:26       ` Stuart Longland
2010-05-25 16:46       ` gnutoo
2010-05-26 13:21         ` Stuart Longland
2010-05-27  0:47           ` Mark Brown
2010-05-28  2:06             ` Stuart Longland
2010-05-28  5:55               ` Eric Bénard [this message]
2010-05-28 11:08                 ` Mark Brown
2010-05-28 13:10                   ` Eric Bénard
2010-06-01  3:30                 ` Stuart Longland
2010-06-01  5:07                   ` Stuart Longland
2010-06-01 11:32                     ` Stuart Longland
2010-06-03 11:14                       ` Mark Brown
2010-06-03 11:43                         ` Stuart Longland
2010-06-03 11:57                           ` Mark Brown
2010-05-28 12:27               ` Mark Brown
2010-05-29  8:59                 ` Stuart Longland

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=4BFF5AC7.3060409@eukrea.com \
    --to=eric@eukrea.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).