Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lokowich <lokowich@acdstar.com>
To: Caglar Akyuz <caglarakyuz@gmail.com>
Cc: ALSA-devel <alsa-devel@alsa-project.org>,
	davinci-linux-open-source
	<davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: DaVinci ASoC DMA stalls
Date: Thu, 04 Sep 2008 17:23:57 -0500	[thread overview]
Message-ID: <48C05FFD.4030009@acdstar.com> (raw)
In-Reply-To: <48C015B2.2070401@gmail.com>

I did have to add a getposition accessor to the DaVinci DMA module, 
which is used by the pcm_pointer function.  Other than that, I believe 
the ASoC should build.  My test is simply to run aplay or speaker-test, 
then quit and run it again.  The first run is audible, the second and 
subsequent runs are not audible until I provide a manual DMA event trigger.

Mark

Caglar Akyuz wrote:
> Mark Lokowich wrote:
>
>   
>> I've been using the DaVinci ASoC for a few months and have recently
>> upgraded to the 2.6.26 based DaVinci git kernel.  Now my audio DMA
>> stalls more readily after stopping an active stream.  I can manually
>> trigger the event by poking the ESR to reactivate the stalled stream,
>> suggesting the problem is in the ASP-to-DMA XEVT interface.  This
>> problem is less prevalent in the 2.6.25 based kernel.  Any help?
>>
>>     
>
>
> I don't know if this helps but, I am using ASoC code on my DaVinci board
> with latest git kernel(2.6.27) and I have no visible issues with the ASoC
> code. However, there may be some code-coverage issue with my usage so if you
> have any test method to verify that I really don't have your problem I'll
> be happy to perform some tests.
>
> My real concern is that this code has never been built without any problems here.
> First there was a separate asoc branch in davinci tree which failed to built.
> I tried with 2.6.25 and there was again build issues. Finally I wasn't able to
> build ASoC code with 2.6.27 so I tried to patch it. I think some part of it 
> relies on some dma code which is not present in davinci tree.[1] I don't know
> if everybody else is patching kernel source to build asoc support, maybe I'm
> doing something wrong. I'm not sure, just FYI.
>
> Regards,
> Caglar
>
> [1] http://linux.omap.com/pipermail/davinci-linux-open-source/2008-March/005920.html
>
>
>   

  reply	other threads:[~2008-09-04 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 13:39 DaVinci ASoC DMA stalls Mark Lokowich
     [not found] ` <48BFE50E.3000802-3mWahjwryh5BDgjK7y7TUQ@public.gmane.org>
2008-09-04 17:06   ` Caglar Akyuz
2008-09-04 22:23     ` Mark Lokowich [this message]
     [not found]       ` <48C05FFD.4030009-3mWahjwryh5BDgjK7y7TUQ@public.gmane.org>
2008-09-09 11:52         ` Griffis, Brad
2008-09-19 22:06           ` Mark Lokowich

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=48C05FFD.4030009@acdstar.com \
    --to=lokowich@acdstar.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=caglarakyuz@gmail.com \
    --cc=davinci-linux-open-source@linux.davincidsp.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