All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: "tiwai@suse.de" <tiwai@suse.de>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>,
	"Nurkkala Eero.An (EXT-Offcode/Oulu)"
	<ext-Eero.Nurkkala@nokia.com>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [RFC 3/4] OMAP3: McBSP: Add interface for transmit FIFO state query
Date: Thu, 4 Mar 2010 09:30:47 +0200	[thread overview]
Message-ID: <201003040930.47744.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <201003031701.40016.peter.ujfalusi@nokia.com>

Hello,

On Wednesday 03 March 2010 17:01:39 Ujfalusi Peter (Nokia-D/Tampere) wrote:
> On Wednesday 03 March 2010 16:18:42 ext Jarkko Nikula wrote:
> > On Wed, 3 Mar 2010 12:02:48 +0200
> > 
> > Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:
> > > The command for test:
> > > aplay -fdat -d 1 /dev/urandom
> > 
> > I recommend to use /dev/zero instead since urandom takes CPU time.
> > 
> > > [   96.290924] XBUFFSTAT: 0
> > > [   96.293487] XBUFFSTAT: 0
> > > [   96.296020] XBUFFSTAT: 0
> > > [   96.299774] XBUFFSTAT: 1
> > > 
> > > So the buffer is kept full in element mode, as it is expected.
> > 
> > I was expecting to see more variations. IRCC, the DMA in OMAP is doing
> > transfers over the memory bus using some small bursts but I'm not
> > completely sure. I'm thinking if that could explain the Eero's and
> > Liam's observations?
> 
> I kind of expecting similar result (this).
> In element mode the threshold value is 0 (1 word).
> So if one word is free in McBSP buffer, than it will assert the DMA request
> line, and the DMA will write one word to McBSP.
> So in theory the buffer must be kept full in this mode, with quite minimal
> variation.
> But I might be wrong on this...

Well, to be precise, I expected that the XBUFFSTAT would have been 1 most of the 
time, and not 0.
But in stereo we are still within one sample accuracy, so I think this is OK.

-- 
Péter

  reply	other threads:[~2010-03-04  7:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 13:39 [RFC 0/4] FIFO caused playback delay (latency) handling in soc Peter Ujfalusi
2010-03-02 13:39 ` [RFC 1/4] ASoC: core: soc level wrapper for pcm_pointer callback Peter Ujfalusi
2010-03-02 13:39 ` [RFC 2/4] ASoC: core: Add delay operation to snd_soc_dai_ops Peter Ujfalusi
2010-03-02 13:45   ` Mark Brown
2010-03-02 13:49     ` Peter Ujfalusi
2010-03-02 13:54       ` Mark Brown
2010-03-02 13:39 ` [RFC 3/4] OMAP3: McBSP: Add interface for transmit FIFO state query Peter Ujfalusi
2010-03-02 13:45   ` Mark Brown
2010-03-02 13:52   ` Eero Nurkkala
2010-03-02 13:58     ` Liam Girdwood
2010-03-02 14:02     ` Peter Ujfalusi
2010-03-02 14:06     ` Jarkko Nikula
2010-03-03  6:07       ` Eero Nurkkala
2010-03-03  7:03         ` Jarkko Nikula
2010-03-03 10:02           ` Peter Ujfalusi
2010-03-03 10:07             ` Peter Ujfalusi
2010-03-03 14:18             ` Jarkko Nikula
2010-03-03 15:01               ` Peter Ujfalusi
2010-03-04  7:30                 ` Peter Ujfalusi [this message]
2010-03-03 19:00             ` ext-Eero.Nurkkala
2010-03-03 19:07               ` ext-Eero.Nurkkala
2010-03-04  7:53                 ` Peter Ujfalusi
2010-03-04  8:09               ` Peter Ujfalusi
2010-03-04  8:46                 ` Eero Nurkkala
2010-03-02 13:39 ` [RFC 4/4] ASoC: OMAP3: Report delay on playback caused by the internal FIFO Peter Ujfalusi
2010-03-02 13:47   ` Mark Brown
2010-03-02 13:52     ` Peter Ujfalusi
2010-03-02 14:06       ` Mark Brown
2010-03-02 13:53 ` [RFC 0/4] FIFO caused playback delay (latency) handling in soc Mark Brown
2010-03-02 23:29 ` Raymond Yau
2010-03-03 10:03   ` 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=201003040930.47744.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=ext-Eero.Nurkkala@nokia.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=tiwai@suse.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 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.