From: Paul Mundt <lethal@linux-sh.org>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>,
Alsa-devel <alsa-devel@lists.sourceforge.net>,
linux-sh <linuxsh-dev@lists.sourceforge.net>
Subject: Re: [PATCH] ALSA driver for Yamaa AICA on Sega Dreamcast
Date: Mon, 17 Apr 2006 13:04:12 +0300 [thread overview]
Message-ID: <20060417100412.GB8910@linux-sh.org> (raw)
In-Reply-To: <20060417095226.GA8910@linux-sh.org>
On Mon, Apr 17, 2006 at 12:52:26PM +0300, Paul Mundt wrote:
> Then the G2 DMA ->get_residue() op needs to be fixed, as it's broken.
> Don't work against the subsystem, it knows what it's doing.
>
> You might be better off getting rid of it entirely and seeing about
> getting the TEI working, you can check for completion and wake up
> accordingly in this case, which is what you ideally want anyways. The
> busy-loop in the generic dma_wait_for_completion() is a stupid hack for
> people that haven't fixed up their TEI handling yet, it's not intended
> for widespread use..
>
What about something like this?
diff --git a/arch/sh/drivers/dma/dma-g2.c b/arch/sh/drivers/dma/dma-g2.c
index 5afab6f..277581e 100644
--- a/arch/sh/drivers/dma/dma-g2.c
+++ b/arch/sh/drivers/dma/dma-g2.c
@@ -49,7 +49,14 @@ static volatile struct g2_dma_info *g2_d
static irqreturn_t g2_dma_interrupt(int irq, void *dev_id, struct pt_regs *regs)
{
- /* FIXME: Do some meaningful completion work here.. */
+ struct dma_channel *chan = dev_id;
+ unsigned int chan_nr = chan->chan;
+ unsigned int bytes;
+
+ bytes = g2_dma->channel[chan_nr].size - g2_dma->status[chan_nr].size;
+ if (likely(bytes == 0))
+ wake_up(&chan->wait_queue);
+
return IRQ_HANDLED;
}
@@ -133,10 +140,17 @@ static int g2_xfer_dma(struct dma_channe
g2_dma->channel[chan_nr].xfer_enable);
return 0;
+}
+
+static int g2_get_dma_residue(struct dma_channel *chan)
+{
+ unsigned int chan_nr = chan->chan;
+ return g2_dma->channel[chan_nr].size - g2_dma->status[chan_nr].size;
}
static struct dma_ops g2_dma_ops = {
.xfer = g2_xfer_dma,
+ .get_residue = g2_get_dma_residue,
};
static struct dma_info g2_dma_info = {
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-17 10:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 0:13 [PATCH] ALSA driver for Yamaa AICA on Sega Dreamcast Adrian McMenamin
2006-04-17 1:29 ` Paul Mundt
2006-04-17 1:29 ` [linuxsh-dev] " Paul Mundt
2006-04-17 9:44 ` [Alsa-devel] " Adrian McMenamin
2006-04-17 9:52 ` Paul Mundt
2006-04-17 10:04 ` Paul Mundt [this message]
2006-04-17 11:51 ` [linuxsh-dev] " Adrian McMenamin
2006-04-17 20:40 ` Adrian McMenamin
2006-04-17 20:00 ` Adrian McMenamin
2006-04-17 20:00 ` [linuxsh-dev] " Adrian McMenamin
2006-04-17 21:47 ` [Alsa-devel] " Lee Revell
2006-04-17 22:05 ` Christoph Hellwig
2006-04-17 22:15 ` Lee Revell
2006-04-18 10:17 ` Takashi Iwai
2006-04-18 10:17 ` [Alsa-devel] " Takashi Iwai
2006-04-18 11:52 ` Christoph Hellwig
2006-04-18 11:52 ` [Alsa-devel] " Christoph Hellwig
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=20060417100412.GB8910@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linuxsh-dev@lists.sourceforge.net \
/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.