All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Wille <audio@cornerbrick.com>
To: alsa-devel@alsa-project.org
Subject: i.MX6 SGTL5000 hangs with EIO error
Date: Wed, 11 May 2016 16:14:29 -0600	[thread overview]
Message-ID: <201605111614.29985.audio@cornerbrick.com> (raw)

Hello,

I am doing an ALSA capture on a Wandboard Quad (i.MX6 quad core with 
SGTL5000 codec chip) from the LINEIN1 jack.  I'm using a 4.6.0-rc3-armv7-x0 
kernel.

Sometimes when the audio glitches (for example, when I plug/unplug the audio 
cable or adjust my signal generator) the snd_pcm_readi() function will 
start returning -5 (EIO).

Once this happens, the only way I've been able to recover is to reboot the 
computer.  Calling snd_pcm_close(), snd_pcm_prepare(), snd_pcm_start(), 
etc. doesn't help.  When in this state, running arecord returns IO errors 
as well.

It's interesting that, on rare occasions, I must do a power cycle in order 
to recover.  When a reboot is not effective I've noticed that the capture 
device doesn't appear in /proc/asound/devices.

I don't believe my specific ALSA settings are important, but I'm calling 
snd_pcm_readi() with ALSA set to a sample rate of 48000, format of S16_LE, 
channels=1, frames per period of 960 (20 mS periods), and 4 periods per 
buffer.

This same problem happens on two different Wandboards, so I don't think it's 
a defective board or chip.  It has happened on older kernels as well.

Any ideas?

Thank you!

Wille

             reply	other threads:[~2016-05-11 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 22:14 Ross Wille [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-12 17:54 i.MX6 SGTL5000 hangs with EIO error Ross Wille
2016-05-12 20:13 ` Caleb Crome
2016-05-13 16:56   ` Ross Wille
2016-05-13 19:23     ` Caleb Crome
2016-05-13 20:45       ` Ross Wille
2016-05-13 22:01         ` Caleb Crome
2016-05-14 20:00           ` Caleb Crome

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=201605111614.29985.audio@cornerbrick.com \
    --to=audio@cornerbrick.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.