All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: linux-omap-open-source@linux.omap.com
Cc: Yves Godin <Yves.Godin@lyrtech.com>
Subject: Re: Problem with ALSA in 2.6.14-omap2 on OSK
Date: Wed, 23 Nov 2005 17:10:03 +0100	[thread overview]
Message-ID: <4384945B.7050700@de.bosch.com> (raw)
In-Reply-To: <42848A5C5A0D1E47B026E644DD49B08E683708@mail>

Yves Godin wrote:
> 	It seems that something has change in the driver for the DMA in
> 2.6.14-omap2.
> 
> When I play a pure tone (ALSA driver), I ear some glitches in the audio
> every 5-10 secconds. Everithing was correct with 2.6.14-rc1.
> 
> From what I can see with a scope on the serial data sent to the codec,
> it seems that some samples (a complete buffer??) are repeated from time
> to time. It's easier to ear it when playing a pure tone (ex 1Khz).
> 
> Note that my alsa driver is slightly modified to play 24 bits audio
> samples instead of 16 bits (DMA is configured in 32 bits). 
> 
> The files from the alsa driver have not changed between 2.6.14-rc1 and
> 2.6.14-omap2. So I supposed the changes have been made to the OMAP dma
> drivers.

On 2.6.15-rc2-omap1 on OSK I can reproduce this using madplay and mp3. 
All 5-10 seconds a short part is repeated.

Any news or ideas about this?

Thanks

Dirk

       reply	other threads:[~2005-11-23 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42848A5C5A0D1E47B026E644DD49B08E683708@mail>
2005-11-23 16:10 ` Dirk Behme [this message]
2005-11-23 16:36 Problem with ALSA in 2.6.14-omap2 on OSK Menon, Nishanth
2005-11-23 16:45 ` Tony Lindgren
2005-11-27 17:46   ` Dirk Behme
2005-11-28  9:55     ` Dirk Behme
2005-12-12 19:34       ` Daniel Petrini
2005-12-12 19:14     ` Daniel Petrini
2005-12-13 15:47       ` Dirk Behme
  -- strict thread matches above, loose matches on Subject: below --
2005-12-13 16:18 Menon, Nishanth

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=4384945B.7050700@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --cc=Yves.Godin@lyrtech.com \
    --cc=linux-omap-open-source@linux.omap.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 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.