All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ihar Filipau <thephilips@gmail.com>
To: alsa-devel@alsa-project.org
Subject: dmix produces garbled sound on ARM
Date: Thu, 9 Jun 2016 13:38:19 +0200	[thread overview]
Message-ID: <CAD08gxJmvpJ-DdGpEawmBZ4aZCNj_Gyhqdf7bSbqRrZ4Xa9Lqg@mail.gmail.com> (raw)

Hi All!

When using the dmix on ARM, the sound comes out garbled, with as if
overlapping, increasing-in-number echoes. That happens even with a
single aplay instance.

In a forum discussion, it was suggested that ARM lacks optimized dmix
implementation. But that implies that the generic dmix code is broken,
since it is what is used on ARM/etc, but not on i386/amd64. (The forum
discussion about my particular issue:
http://unix.stackexchange.com/questions/288451/sound-corruption-echo-when-trying-to-use-alsa-dmix
)

Does anybody has any suggestions how to fix/avoid the dmix issue on ARM?

Thanks.

P.S. Versions: Linux v3.18.24, alsa-lib/-utils v1.0.29. The hardware:
FreeScale i.MX35 (ARM1136) with SGTL5000 sound chip (used in 48KHz
mode).

P.P.S. The generic code has outdated functions for the "concurrent"
implementation with cmpxchg. The code probably could be updated, and
revised to use the C11's stdatomic.h when available.

             reply	other threads:[~2016-06-09 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 11:38 Ihar Filipau [this message]
2016-06-09 13:01 ` dmix produces garbled sound on ARM Takashi Iwai
2016-06-09 13:17   ` Ihar Filipau
2016-06-09 13:25     ` Takashi Iwai
     [not found]       ` <CAD08gxKw2UK9JJ80Pp5icxLC_k-8dGykhHd3DbUvjPJXUGzVtQ@mail.gmail.com>
     [not found]         ` <s5hporqe5r2.wl-tiwai@suse.de>
2016-06-10 12:06           ` Ihar Filipau
2016-06-13 12:32           ` Ihar Filipau
2016-06-13 12:42             ` Takashi Iwai
2016-06-13 14:04               ` Ihar Filipau

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=CAD08gxJmvpJ-DdGpEawmBZ4aZCNj_Gyhqdf7bSbqRrZ4Xa9Lqg@mail.gmail.com \
    --to=thephilips@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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.