alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Valentin Longchamp <valentin.longchamp@epfl.ch>
Subject: Re: mx31 snd and mc13783 codec status
Date: Wed, 7 Apr 2010 13:12:07 +0100	[thread overview]
Message-ID: <20100407121206.GC13576@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20100407110350.GD3688@pengutronix.de>

On Wed, Apr 07, 2010 at 01:03:50PM +0200, Sascha Hauer wrote:
> On Fri, Apr 02, 2010 at 11:42:42AM +0100, Mark Brown 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.

> After deleting the file I could play sounds (and record simultaniously)
> with rates up to 44100kHz without visible cpu utilisation.

Yes, if you tweak the buffer sizes (most of the ALSA test utilities
support this) then you can use higher sample rates - pulseaudio's high
latency modes should work great, for example.

> Looking at it I realised that poll_time is 0, so the timer gets reloaded
> with the actual jiffies value which of course is a bad idea. We should
> probably use a hrtimer here.

Yes, by default you're only going to be able to poll at 1ms intervals so
the poll time ends up going down to zero.  I did look at switching over
to a hrtimer when I was fixing up the sample rate slips but I wasn't
able to convince myself that there was a hrtimer offering sufficient
resolution available on i.MX.

      reply	other threads:[~2010-04-07 12:12 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
2010-04-07 11:03         ` Sascha Hauer
2010-04-07 12:12           ` Mark Brown [this message]

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=20100407121206.GC13576@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=valentin.longchamp@epfl.ch \
    /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).