From: Jarek <jarek@poczta.srv.pl>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Alsa soc UDA1380 - no duplex
Date: Thu, 05 Apr 2012 09:52:49 +0200 [thread overview]
Message-ID: <1333612369.9929.19.camel@tower.local> (raw)
In-Reply-To: <CA+E=qVfpt-m73SaTE92ASNNLVwE+Q0DNYC-2Z8v26CZ=Ukpp_A@mail.gmail.com>
Dnia 2012-04-03, wto o godzinie 18:09 +0300, Vasily Khoruzhick pisze:
> Probably it's lpc313x limitation (CPU DAI does not support duplex?)
Do you know how to check if this is hardware limitation ? I have
reviewed documentation and from my point of view it should work.
http://ics.nxp.com/products/lpc3000/datasheet/lpc3130.lpc3131.pdf
> Anyway, looks like its code is not upstreamed.
Yes, I didn't notice before, that all code comes from this patch (for
kernel 3.2):
http://www.lpclinux.com/pub/Forums/ForumLPC313x0055/lpc.tar.gz
>
> > The other question is why there are two drivers to the same device.
>
> AFAIK there's only one driver for uda1380 codec.
I've found separete folders for samsung and lpc in sound/soc/ and I
suspected that there are two separate drivers. As I understand now,
there is only separate intermediary layer. The files in those folders
are quite different, so I don't know how to compare them, to find the
difference.
In mean time. I have received the following respone from lpclinux:
=====
As I understand,it is the SW limitation limitation because of which we
can not use playback & capture feature simultaneously. The audio driver
code is based on ALSA framework available in sound/soc/lpc313x. Please
give it a try & let us know about the results
=====
I'll be glad, if can take a look at this code.
or just give me some direction.
next prev parent reply other threads:[~2012-04-05 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 9:34 Alsa soc UDA1380 - no duplex jarek
2012-04-03 15:09 ` Vasily Khoruzhick
2012-04-05 7:52 ` Jarek [this message]
2012-04-05 17:46 ` Jarek
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=1333612369.9929.19.camel@tower.local \
--to=jarek@poczta.srv.pl \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@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).