From: Jarkko Nikula <jhnikula@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: ext Mark Brown <broonie@opensource.wolfsonmicro.com>,
Tony Lindgren <tony@atomide.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"Nurkkala Eero.An (EXT-Offcode/Oulu)"
<ext-Eero.Nurkkala@nokia.com>
Subject: Re: [PATCHv2 0/5] FIFO caused playback delay (latency) handling in soc/omap
Date: Fri, 12 Mar 2010 10:30:50 +0200 [thread overview]
Message-ID: <20100312103050.b83db5c4.jhnikula@gmail.com> (raw)
In-Reply-To: <201003120818.30290.peter.ujfalusi@nokia.com>
On Fri, 12 Mar 2010 08:18:30 +0200
Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:
> On Friday 12 March 2010 00:43:41 ext Mark Brown wrote:
>
> > I can do, though there was some debate about how useful the
> > information the hardware returns actually is - could folks confirm
> > what the consensus there was, please?
>
> Yeah, that thread went silent without final go or no go...
>
...
> All in all, I think the usage of the BUFFSTAT register is a good compromise for
> all cases, and it is needed for the cases, where the codec also have buffer of
> it's own.
>
And one point is that the BUFFSTAT use doesn't make things worse than
currently. Now the application doesn't have any information about the
HW buffer caused audio latencies so reporting them makes the things
better than currently.
--
Jarkko
next prev parent reply other threads:[~2010-03-12 8:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 13:08 [PATCHv2 0/5] FIFO caused playback delay (latency) handling in soc/omap Peter Ujfalusi
2010-03-03 13:08 ` [PATCHv2 1/5] ASoC: core: fix tailing whitespace in soc_pcm_apply_symmetry Peter Ujfalusi
2010-03-03 13:27 ` [alsa-devel] " Liam Girdwood
2010-03-03 13:08 ` [PATCH] OMAP3: PM: Enable wake-up from McBSP2, 3 and 4 modules Peter Ujfalusi
2010-03-03 14:08 ` Peter Ujfalusi
2010-03-03 14:46 ` Jarkko Nikula
2010-03-03 13:08 ` [PATCHv2 2/5] ASoC: core: soc level wrapper for pcm_pointer callback Peter Ujfalusi
2010-03-03 13:27 ` [alsa-devel] " Liam Girdwood
2010-03-03 13:08 ` [PATCHv2 3/5] ASoC: core: Add delay operation to snd_soc_dai_ops Peter Ujfalusi
2010-03-03 13:28 ` Liam Girdwood
2010-03-03 13:08 ` [PATCHv2 4/5] OMAP3: McBSP: Add interface for FIFO caused delay query Peter Ujfalusi
2010-03-03 14:38 ` Jarkko Nikula
2010-03-03 13:08 ` [PATCHv2 5/5] ASoC: OMAP3: Report delay caused by the internal FIFO Peter Ujfalusi
2010-03-03 13:28 ` Liam Girdwood
2010-03-03 14:30 ` Jarkko Nikula
2010-03-03 13:38 ` [PATCHv2 0/5] FIFO caused playback delay (latency) handling in soc/omap Mark Brown
2010-03-11 22:26 ` Tony Lindgren
2010-03-11 22:43 ` Mark Brown
2010-03-12 6:18 ` Peter Ujfalusi
2010-03-12 8:30 ` Jarkko Nikula [this message]
2010-03-12 11: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=20100312103050.b83db5c4.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ext-Eero.Nurkkala@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.com \
/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).