From: Mark Brown <broonie@sirena.org.uk>
To: christian pellegrin <chripell@gmail.com>
Cc: David Anders <dave123_aml@yahoo.com>,
alsa-devel@alsa-project.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: possible problem in s3c24xx-pcm.c in git-devel branch
Date: Fri, 14 Nov 2008 12:46:41 +0000 [thread overview]
Message-ID: <20081114124640.GB25307@sirena.org.uk> (raw)
In-Reply-To: <20081113160936.GH31592@sirena.org.uk>
On Thu, Nov 13, 2008 at 04:09:36PM +0000, Mark Brown wrote:
> AIUI it's a bootstrapping issue: the problem is what happens when the
> first DMA buffer completes if there isn't a new buffer ready. Once
> there's a loaded buffer ready things are happy.
More info provided by Dave on IRC:
15:46 < prpplague> now the big difference between the 2410 and 2440 is ofcourse
the primary clock, the 2410 generally running 200mhz whereas
the 2440 is at 400mhz
...
15:49 < prpplague> i'm wondering if that when on a 200mhz s3c2410 that the
second dma enqueued buffer is done, that it has been long
enough for the dma channel to have started, but on the 2440
running at 400mhz it hasn't had time to start
...
16:38 < prpplague> broonie: i wonder if i clock the my s3c2440 board at 200mhz
and retested if i would see the issue
16:41 < prpplague> broonie: yep, i can recreate christians problem when using
the s3c2440 at 200mhz
16:42 < prpplague> broonie: and also if i use the stock code, i.e. without the
enqueue limit being 1, and running at 200mhz the audio issue
goes away
next prev parent reply other threads:[~2008-11-14 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 14:57 possible problem in s3c24xx-pcm.c in git-devel branch christian pellegrin
2008-11-13 15:17 ` Mark Brown
2008-11-13 15:40 ` christian pellegrin
2008-11-13 16:09 ` Mark Brown
2008-11-14 12:46 ` Mark Brown [this message]
2008-11-14 16:20 ` christian pellegrin
2008-11-17 11:00 ` Mark Brown
2008-11-13 15:44 ` David Anders
2008-11-13 16:02 ` christian pellegrin
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=20081114124640.GB25307@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=chripell@gmail.com \
--cc=dave123_aml@yahoo.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.