All of lore.kernel.org
 help / color / mirror / Atom feed
From: jiwang <jiada_wang@mentor.com>
To: alsa-devel@alsa-project.org, perex@perex.cz
Subject: alsa-utils aplay/arecord can't be interrupted when streaming is not active
Date: Wed, 16 Apr 2014 16:54:30 +0900	[thread overview]
Message-ID: <534E3736.6070100@mentor.com> (raw)

Hi All

With latest 1.0.27.2 alsa-utils, I am facing problem to interrupt 
aplay/arecord
when the streaming is not active (no data can be written to or read from 
cards)
further more, if I start aplay/arecord with "-N" nonblocking option,
then aplay/arecord can never exit, unless I do a system reset


I found if I revert the following patch

/commit 1d0042d7e948815f8015c62bc53143eed3b83206//
//Author: Jaroslav Kysela <perex@perex.cz>//
//Date:   Mon Apr 8 13:30:54 2013 +0200//
//
//    aplay/arecord: change the interrupt handling using snd_pcm_abort()//
////
//    It is required (exclude the fatal SIGABRT) to call snd_pcm_close() 
and//
//    the end of work (outside of the interrupt handler). Use new 
snd_pcm_abort()//
//    function to inform alsa-lib to not ignore EINTR and move the 
in_aborting//
//    variable to the global scope to be checked in the i/o loops.//
////
//    Signed-off-by: Jaroslav Kysela <perex@perex.cz>//
/
http://git.alsa-project.org/?p=alsa-utils.git;a=commit;h=1d0042d7e948815f8015c62bc53143eed3b83206

then aplay/arecord can be interrupted correctly

Is it a defect in aplay.c or did I miss something?

Thanks,
Jiada

             reply	other threads:[~2014-04-16  7:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  7:54 jiwang [this message]
2014-04-16  8:06 ` alsa-utils aplay/arecord can't be interrupted when streaming is not active Jaroslav Kysela
2014-04-16  8:34   ` jiwang
2014-04-16  8:58     ` Jaroslav Kysela
2014-04-16 12:00       ` Jiada Wang
2014-04-17  9:03       ` jiwang
2014-04-21  3:01       ` Jiada Wang

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=534E3736.6070100@mentor.com \
    --to=jiada_wang@mentor.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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.