From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH] ALSA: pcm - introduce soc_delay
Date: Mon, 23 Jul 2012 15:16:28 -0500 [thread overview]
Message-ID: <500DB11C.1050007@linux.intel.com> (raw)
In-Reply-To: <20120723200512.GB25707@sirena.org.uk>
> Don't drop CCs from replies.
Sorry.
>
>> Vinod is trying to explain is that due to the bursty nature of data
>> transfers inside the soc, we need to modify how the accounting is
>> done.
> Right, but this depends on the ability of the device to pause reading
> data when it reads up to the point where the application has written.
> This is a separate capability to any latency that's been added by the
> buffering, and most of the systems that have the buffering don't have
> this capability but instead either don't report the buffer or rely on
> the application being a full buffer ahead of the hardware.
>
>
We don't have such fancy hardware (and I don't think anyone has). This
can happen even with simple IP that has an embedded SRAM and bursty
DMA, if the IP buffer amounts to the period size to avoid partial wakes
or transfers, and the application cannot provide more than one period
initially you get an underflow that isn't a true one.
-Pierre
next prev parent reply other threads:[~2012-07-23 20:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 10:06 [PATCH] ALSA: pcm - introduce soc_delay Vinod Koul
2012-07-23 10:18 ` Mark Brown
2012-07-23 10:39 ` Vinod Koul
2012-07-23 10:47 ` Mark Brown
2012-07-23 11:06 ` Vinod Koul
2012-07-23 13:47 ` Mark Brown
2012-07-23 19:51 ` Pierre-Louis Bossart
2012-07-23 20:05 ` Mark Brown
2012-07-23 20:16 ` Pierre-Louis Bossart [this message]
2012-07-23 21:27 ` Mark Brown
2012-07-23 14:21 ` Jassi Brar
2012-07-23 10:19 ` Jassi Brar
2012-07-23 10:39 ` Vinod Koul
2012-07-23 10:50 ` Jassi Brar
2012-07-23 11:17 ` Vinod Koul
2012-07-23 11:23 ` Mark Brown
2012-07-23 13:37 ` Jassi Brar
2012-07-23 10:27 ` Takashi Iwai
2012-07-23 10:47 ` Vinod Koul
2012-07-23 10:47 ` Jaroslav Kysela
2012-07-23 11:14 ` Vinod Koul
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=500DB11C.1050007@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--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.