From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: Mohammed Amine SAYA <amine.saya@rfo.atmel.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: No sound comes out of AC97 codec
Date: Fri, 23 Dec 2005 18:39:48 +0000 [thread overview]
Message-ID: <1135363188.3512.12.camel@localhost.localdomain> (raw)
In-Reply-To: <43AC08ED.9030005@rfo.atmel.com>
On Fri, 2005-12-23 at 15:25 +0100, Mohammed Amine SAYA wrote:
> Hi all,
> I wrote a driver for an AC97 controller on ARM-based platform.
Can you tell us what your target cpu is ?
> I decided to print the
> runtime->dma_addr to
> see what kind of data the dma buffer contains. I only found out
> 0x80008000 patterns and this
> is exactly what I see on AC97_TX in slots 3 and 4 on the scope.
ok, this means the ac97 controller on your cpu is probably running (as
it's sending data out on slots 3 and 4). Your DMA is probably also
working as it looks the buffer is being sent out on slots 3 and 4.
>
> Where did the pcm data generated by mplayer go ?
Out of interest, have you tried using aplay and playing a wav file ?
> Why the dma buffer is empty ? I use
> snd_pcm_lib_preallocate_pages_for_all and snd_pcm_lib_malloc_pages
> to allocate the dma buffer.
>
> The codec is detected correctly but the dma buffer is full of corrupted pcm.
>
> Any lights on this please ?
>
It would probably help if you could post your code somewhere as it
sounds like a complex problem.
Liam
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-23 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 14:25 No sound comes out of AC97 codec Mohammed Amine SAYA
2005-12-23 18:39 ` Liam Girdwood [this message]
2005-12-23 19:02 ` Lee Revell
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=1135363188.3512.12.camel@localhost.localdomain \
--to=liam.girdwood@wolfsonmicro.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=amine.saya@rfo.atmel.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