All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>
Cc: 'Troy Kisky' <troy.kisky@boundarydevices.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Arun KS <arunks@mistralsolutions.com>
Subject: RE: [alsa-devel] [PATCH] ASoC: AM3517: Fix AIC23 suspend/resume hang
Date: Thu, 26 Nov 2009 20:26:44 +0530	[thread overview]
Message-ID: <5A47E75E594F054BAF48C5E4FC4B92AB030AAC3291@dbde02.ent.ti.com> (raw)
In-Reply-To: <20091126102230.GB27562@rakim.wolfsonmicro.main>

> -----Original Message-----
> From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> Sent: Thursday, November 26, 2009 3:53 PM
> To: Aggarwal, Anuj
> Cc: 'Troy Kisky'; alsa-devel@alsa-project.org; linux-omap@vger.kernel.org;
> Arun KS
> Subject: Re: [alsa-devel] [PATCH] ASoC: AM3517: Fix AIC23 suspend/resume
> hang
> 
> On Thu, Nov 26, 2009 at 08:31:11AM +0530, Aggarwal, Anuj wrote:
> 
> > I have already tried that but it doesn't fix the problem entirely.
> > Still, I was not able to playback properly because the bias settings
> > were not handled correctly and as you can see, it writes to some
> > invalid registers too (all registers don't exist between 0 and
> ARRAY_SIZE).
> 
> Please also note the following patch which is queued for 2.6.32:
> 
> commit 50b6bce59d154b5db137907a5c0ed45a4e7a3829
> Author: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Date:   Mon Nov 23 13:11:53 2009 +0000
> 
>     ASoC: Fix suspend with active audio streams
> 
[Aggarwal, Anuj] I am also seeing one more problem with the original 
driver, although I am not sure if the problem is in the audio driver. 
When tried to capture, using NFS as storage, it gives overrun error and comes out with:
arecord: pcm_read:1617: read error: Input/output error

It happen always after ~20 sec, file size ~5MB. Tried with multiple
configurations in arecord but no use.
When tried: arecord -f cd /dev/null, it works fine. Same issue doesn't 
come too when I try to store the captured audio file on a MMC card.

Any idea what could be the problem? Why arecord goes for a toss after a 
single overrun error and why it is happening always after ~20 sec? Is
there something which can be tried to narrow down the problem?


  reply	other threads:[~2009-11-26 14:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 13:10 [PATCH] ASoC: AM3517: Fix AIC23 suspend/resume hang Anuj Aggarwal
2009-11-25 13:33 ` Mark Brown
2009-11-25 19:19   ` Aggarwal, Anuj
2009-11-25 19:39     ` Mark Brown
2009-11-26  3:19       ` Aggarwal, Anuj
2009-11-25 20:22 ` Troy Kisky
2009-11-26  3:01   ` Aggarwal, Anuj
2009-11-26 10:22     ` [alsa-devel] " Mark Brown
2009-11-26 14:56       ` Aggarwal, Anuj [this message]
2009-11-26 15:11         ` Mark Brown
2009-11-26 15:22           ` Aggarwal, Anuj
2009-11-26 15:24             ` Aggarwal, Anuj
2009-11-26 15:29             ` Mark Brown
2009-11-27  8:07               ` Aggarwal, Anuj
2009-11-27 11:42                 ` [alsa-devel] " Mark Brown
2009-11-27 11:47                 ` Mark Brown
2009-11-26 15:42             ` Philby John

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=5A47E75E594F054BAF48C5E4FC4B92AB030AAC3291@dbde02.ent.ti.com \
    --to=anuj.aggarwal@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arunks@mistralsolutions.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=troy.kisky@boundarydevices.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.