From: Vinod Koul <vinod.koul@linux.intel.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
broonie@opensource.wolfsonmicro.com, lrg@ti.com
Subject: Re: [PATCH] ALSA: pcm - introduce soc_delay
Date: Mon, 23 Jul 2012 16:09:58 +0530 [thread overview]
Message-ID: <1343039998.1726.4833.camel@vkoul-udesk3> (raw)
In-Reply-To: <CABb+yY1-RyuCigCYM-dwsc1D1vSvy+QX1nunrc8G+3bT2n134g@mail.gmail.com>
On Mon, 2012-07-23 at 15:49 +0530, Jassi Brar wrote:
> On Mon, Jul 23, 2012 at 3:36 PM, Vinod Koul <vinod.koul@linux.intel.com> wrote:
> > In many modern SoCs the audio DSP can buffer the PCM ring buffer data. Today we
> > have no means to represent this buffering and ALSA wrongly detects an overrun
> > when hw_ptr reaches app_ptr value, though DSP may still have some buffered data.
> >
> > This patch tries to add a new field "soc_delay" to represent buffering done in
> > DSPs. This value is also used for the xrun calculations in ALSA.
> >
> Couldn't we employ snd_pcm_hw_params.fifo_size for the purpose ?
Nope, that should be used to represent the delay in samples being output
not the sample which are buffered and processed in a DSP
--
~Vinod
next prev parent reply other threads:[~2012-07-23 10:39 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
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 [this message]
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=1343039998.1726.4833.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassisinghbrar@gmail.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.