From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCHv2 0/5] *** SUBJECT HERE ***ASoC: tlv320dac33: FIFO caused delay reporting and fixes
Date: Fri, 23 Apr 2010 16:29:25 +0100 [thread overview]
Message-ID: <20100423152925.GF27232@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1272006601-24946-1-git-send-email-peter.ujfalusi@nokia.com>
On Fri, Apr 23, 2010 at 10:09:56AM +0300, Peter Ujfalusi wrote:
> The values reported by the delay call has been verified by using one GPIO as a
> signal, and printout from the kernel at the same time with the delay, than
> based on the time scale on the scope several (>100) cases has been hand
> calculated and the results were compared to the kernel reported values.
> The difference were around (or less) the 10 samples, but during the bursts it
> is much harder to count, but the reported value was reasonable accurate there
> as well.
All these look good to me.
next prev parent reply other threads:[~2010-04-23 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 7:09 [PATCHv2 0/5] *** SUBJECT HERE ***ASoC: tlv320dac33: FIFO caused delay reporting and fixes Peter Ujfalusi
2010-04-23 7:09 ` [PATCHv2 1/5] ASoC: tlv320dac33: Fix for early interrupt in FIFO Mode1 Peter Ujfalusi
2010-04-23 7:09 ` [PATCHv2 2/5] ASoC: tlv320dac33: Skip calculations in FIFO Bypass mode Peter Ujfalusi
2010-04-23 7:09 ` [PATCHv2 3/5] ASoC: tlv320dac33: Change magic numbers used in Mode7 Peter Ujfalusi
2010-04-23 7:10 ` [PATCHv2 4/5] ASoC: tlv320dac33: Calculate the interface speed during bursts Peter Ujfalusi
2010-04-23 7:10 ` [PATCHv2 5/5] ASoC: tlv320dac33: FIFO caused delay reporting Peter Ujfalusi
2010-04-23 15:29 ` Mark Brown [this message]
2010-04-26 14:40 ` [PATCHv2 0/5] *** SUBJECT HERE ***ASoC: tlv320dac33: FIFO caused delay reporting and fixes Liam Girdwood
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=20100423152925.GF27232@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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 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.