From: Takashi Iwai <tiwai@suse.de>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>,
linux-sh <linuxsh-dev@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
Lee Revell <rlrevell@joe-job.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [linuxsh-dev] Re: [Alsa-devel] [PATCH] Add Dreamcast AICA driver to alsa-driver
Date: Mon, 24 Apr 2006 19:57:15 +0200 [thread overview]
Message-ID: <s5hejzm26x0.wl%tiwai@suse.de> (raw)
In-Reply-To: <1145900695.9243.4.camel@localhost.localdomain>
At Mon, 24 Apr 2006 18:44:55 +0100,
Adrian McMenamin wrote:
>
> >
> > > +static int stereo_buffer_transfer(struct snd_pcm_substream
> > > + *substream, int buffer_size, int period)
> > > +{
> >
> > I feel this transfer-and-wait could be done more efficiently using
> > workq than doing it in timer callback. The trigger(start) and
> > aica_period_elapsed() calls queue_work() at each time.
> >
> > The most work of spu_begin_dma() should be put in the workq, too.
> >
>
> heh. If you remember, a couple of months ago I had this in a kernel
> thread - ie much the same - and you or Lee said I should absolutely not
> use that mechanism :)
Well, a source code tell you better than hundreds words :)
> > You can write a single function for both mono and two-channel
> > streams.
> >
>
> How can I do that given the dma has to be serialised?
The second dma_xfer() can be in if (channels > 1) block (in addition
to different transfer bytes). Something like below:
static int buffer_transfer(struct snd_pcm_substream*substream,
int buffer_size, int period)
{
int transferred;
int dma_countout;
struct snd_pcm_runtime *runtime;
int period_offset;
long dma_flags;
period_offset = period;
period_offset %= (AICA_PERIOD_NUMBER / runtime->channels);
runtime = substream->runtime;
/* transfer left and then right */
dma_flags = claim_dma_lock();
dma_countout = 0;
dma_xfer(0,
runtime->dma_area + (AICA_PERIOD_SIZE * period_offset),
AICA_CHANNEL0_OFFSET +
(AICA_PERIOD_SIZE * period_offset), buffer_size / 2, 5);
/* wait for completion */
do {
udelay(5);
transferred = get_dma_residue(0);
dma_countout++;
if (dma_countout > 0x10000)
break; /* Approx 1/3 sec timeout in case of hardware failure */
}
while (transferred < buffer_size / 2);
if (runtime->channels > 1) {
dma_xfer(0,
AICA_BUFFER_SIZE / 2 + runtime->dma_area +
(AICA_PERIOD_SIZE * period_offset),
AICA_CHANNEL1_OFFSET +
(AICA_PERIOD_SIZE * period_offset), buffer_size / 2, 5);
/* have to wait again */
dma_countout = 0;
do {
udelay(5);
transferred = get_dma_residue(0);
dma_countout++;
if (dma_countout > 0x10000)
break;
}
while (transferred < buffer_size / 2);
}
release_dma_lock(dma_flags);
return 0;
}
Takashi
prev parent reply other threads:[~2006-04-24 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1145831786.9242.38.camel@localhost.localdomain>
[not found] ` <1145832383.9242.41.camel@localhost.localdomain>
2006-04-24 11:10 ` Takashi Iwai
2006-04-24 17:44 ` [linuxsh-dev] " Adrian McMenamin
2006-04-24 17:57 ` Takashi Iwai [this message]
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=s5hejzm26x0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=rlrevell@joe-job.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
all inboxes | Powered by JetHome®