alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: mx31 snd and mc13783 codec status
Date: Tue, 06 Apr 2010 18:00:27 +0200	[thread overview]
Message-ID: <4BBB5A9B.20004@epfl.ch> (raw)
In-Reply-To: <20100402104241.GC27613@sirena.org.uk>

Mark Brown wrote:
> On Fri, Apr 02, 2010 at 11:53:58AM +0200, Sascha Hauer wrote:
>> On Thu, Apr 01, 2010 at 06:01:38PM +0200, Valentin Longchamp wrote:
> 
> What sample rate are you trying to play and what buffer size?  In my
> testing the FIQ was really struggling with most applications at sample
> rates over ~16kHz since you need each audio period to be long enough to
> at least fill the interval between timer polls but applications wanted
> to select buffer sizes that were consumed faster than the timer tick.
> 
> Using an application like speaker-test which has minimal overhead and no
> I/O to worry about helps too.

OK, I have done some tests with speaker-test and I experienced the same 
as you did: with rates over 16kHz, the FIQ starts to have some problems.

> 
>>> If then it looks like on my system, I have a problem with the  
>>> snd_pcm_update_hw_ptr0 call.
> 
>> You could try reverting b4e82b5b785670b68136765059d1afc65c0ae023. Though
>> I have tested it on my boards it may have some implications.
> 
> I was seeing similar behaviour before and after that patch too, the main
> effect there was to improve the error handling when the FIQ and the
> timer get out of sync with each other.

Mark is right, the behavior is similar with or without this patch, it 
does not improve the FIQ problems with rates over 16 kHz.

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne

  reply	other threads:[~2010-04-06 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 16:23 mx31 snd and mc13783 codec status Valentin Longchamp
2010-03-30 20:40 ` Mark Brown
2010-03-31  8:38   ` Sascha Hauer
2010-03-31  8:34 ` Sascha Hauer
2010-04-01 16:01   ` Valentin Longchamp
2010-04-02  9:53     ` Sascha Hauer
2010-04-02 10:42       ` Mark Brown
2010-04-06 16:00         ` Valentin Longchamp [this message]
2010-04-07 11:03         ` Sascha Hauer
2010-04-07 12:12           ` Mark Brown

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=4BBB5A9B.20004@epfl.ch \
    --to=valentin.longchamp@epfl.ch \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).