From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: about dma-sh driver
Date: Wed, 24 Sep 2008 04:54:26 +0000 [thread overview]
Message-ID: <20080924045425.GA6516@linux-sh.org> (raw)
In-Reply-To: <29ab51dc0809232129j2a54662bg1e5ac50161f6cc94@mail.gmail.com>
On Wed, Sep 24, 2008 at 01:29:56PM +0900, Nobuhiro Iwamatsu wrote:
> I'm making driver who used dma-sh.
> I use a dma-sh driver and want to use another interrupt handler.
> I want to use request, get_residue and other dma_ops functions
> and change only dma_tei function.
>
> Dma-sh has a function for IRQ interrupts in dma-sh driver.
> For an IRQ interrupt, we cannot register another interrupt handler.
>
> Is this right?
>
> I think about three suggestion.
>
> 1. Add interrupt handler override function to dma-sh and dma-api.
> I wrote quick hack this suggestion.
>
> 2. Create SuperH driver of dma engine and shift dma engine.
> I hear that dma-sh shifts to dma-engine.
> But I don't know schedule about dma engine.
>
> 3. Do both 1 and 2 in parallelism.
>
#3 is probably the easiest. #1 shouldn't take more than 10 minutes to
hack together, and if you're going to have in-tree stuff making use of
that, it doesn't make any sense to hold that off while the dmaengine work
is happening. We can easily accomodate #1 in 2.6.28.
#2 is on my todo list, but it will likely be at least 2.6.29 or 2.6.30
before I even start looking at it. If you want to start on it before
that, please do. :-)
next prev parent reply other threads:[~2008-09-24 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 4:29 about dma-sh driver Nobuhiro Iwamatsu
2008-09-24 4:54 ` Paul Mundt [this message]
2008-09-24 6:36 ` Nobuhiro Iwamatsu
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=20080924045425.GA6516@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
/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.