From: Jyri Sarha <jsarha@ti.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: "Benoît Thébaudeau" <benoit.thebaudeau.dev@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: Differences between tlv320aic3x and tlv320aic31xx
Date: Wed, 1 Oct 2014 10:47:59 +0300 [thread overview]
Message-ID: <542BB1AF.3060501@ti.com> (raw)
In-Reply-To: <20140930183731.GC3907@piout.net>
On 09/30/2014 09:37 PM, Alexandre Belloni wrote:
> Hi,
>
> I'm trying to add support for the tlv320aic3104a present on a
> custom board using an am335x.
>
> I see that Benoit seemed to have been successful when using the
> tlv320aic3x driver with minor modifications.
> http://mailman.alsa-project.org/pipermail/alsa-devel/2013-January/058966.html
>
> On the other hand, in the past, I've used a tlv320aic3100 with the
> tlv320aic31xx driver.
>
> My plan for now is to use the tlv320aic3x driver with snd-soc-evm as
> this is the one it is using (it is using .codec_dai_name =
> "tlv320aic3x-hifi").
>
> I had no luck until now but I still have to review my pinmuxing. But
> before I investigate to much, can you confirm what codecs are supported
> by which driver? I'm pretty sure that would be a nice addition to the
> documentation too.
> 0
Hi Alexandre,
Based on a brief look at the data sheet I am afraid you will not have
any luck using tlv320aic3x driver with tlv320aic3104. tlv320aic31xx is a
better match, but sill not close enough.
Based on the register map you may have a change to get the codec working
using tlv320aic32x4 driver. At least the register map appears to be a
pretty good match. However, I have no experience either with the driver
or the codec.
Best regards,
Jyri
next prev parent reply other threads:[~2014-10-01 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 18:37 Differences between tlv320aic3x and tlv320aic31xx Alexandre Belloni
2014-10-01 7:47 ` Jyri Sarha [this message]
2014-10-01 20:03 ` Benoît Thébaudeau
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=542BB1AF.3060501@ti.com \
--to=jsarha@ti.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=benoit.thebaudeau.dev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.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