From: "Eric Bénard" <eric@eukrea.com>
To: anilkumar <kollianil2009@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: imx-ssi.c & SND_SOC_DAIFMT_I2S
Date: Wed, 23 Jun 2010 12:28:40 +0200 [thread overview]
Message-ID: <4C21E1D8.3080608@eukrea.com> (raw)
In-Reply-To: <loom.20100623T120433-100@post.gmane.org>
Hi Anil,
Le 23/06/2010 12:15, anilkumar a écrit :
> Please send me the configuration [if any changes] from i.mx ssi slave and
> tlv320aic33.
>
I'm using TLV320AI23 and not the 33 so I don't know the necessary
changes for your codec but this look like you could start from
eukrea-tlv320.c and update it for tlv320aic33.
Eric
prev parent reply other threads:[~2010-06-23 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 9:34 imx-ssi.c & SND_SOC_DAIFMT_I2S Eric Bénard
2010-05-26 10:37 ` Sascha Hauer
2010-05-26 12:41 ` Eric Bénard
2010-05-27 0:56 ` Mark Brown
2010-05-27 1:15 ` Eric Bénard
2010-05-27 1:54 ` Mark Brown
2010-06-23 10:15 ` imx-ssi.c & SND_SOC_DAIFMT_I2S anilkumar
2010-06-23 10:28 ` Eric Bénard [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=4C21E1D8.3080608@eukrea.com \
--to=eric@eukrea.com \
--cc=alsa-devel@alsa-project.org \
--cc=kollianil2009@gmail.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).