All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mohammed Amine SAYA <amine.saya@rfo.atmel.com>
To: alsa-devel@lists.sourceforge.net
Subject: No sound comes out of AC97 codec
Date: Fri, 23 Dec 2005 15:25:49 +0100	[thread overview]
Message-ID: <43AC08ED.9030005@rfo.atmel.com> (raw)

Hi all,
I wrote a driver for an AC97 controller on ARM-based platform.
I followed the instructions in "Writing an ALSA Driver" tutorial.
I cross-compiled mplayer and I added some debug lines in my prepare, 
trigger and pointer
functions in the alsa driver. It seems that mplayer uses these functions 
but no sound comes out of
the speaker.
I put a scope to monitor AC97_TX, AC97_RX, AC97_CK and AC97_FS signals.
I was surprised to discover that nothing is sent. 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.

Where did the pcm data generated by mplayer go ?
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 ?


Best regards,

Amine.



-------------------------------------------------------
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

             reply	other threads:[~2005-12-23 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-23 14:25 Mohammed Amine SAYA [this message]
2005-12-23 18:39 ` No sound comes out of AC97 codec Liam Girdwood
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=43AC08ED.9030005@rfo.atmel.com \
    --to=amine.saya@rfo.atmel.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.