From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: haavard.skinnemoen@atmel.com
Cc: linux-kernel@vger.kernel.org, maciej.sosnowski@intel.com,
dan.j.williams@intel.com
Subject: Re: dw_dmac driver questions
Date: Fri, 09 Jan 2009 23:06:26 +0900 (JST) [thread overview]
Message-ID: <20090109.230626.126760668.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <20090105.230230.132760259.anemo@mba.ocn.ne.jp>
On Mon, 05 Jan 2009 23:02:30 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> On Mon, 29 Dec 2008 23:39:32 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> > Hi. I'm writing a new DMA driver, using dw_dmac driver in kernel
> > 2.6.28 as a reference implementation.
> >
> > I can see an outline of the dw_dmac driver and framework (well,
> > hopefully), but have some questions in details.
>
> One more.
One more again.
5. dwc_issue_pending()
Is this needed? The dwc_tx_submit might queue the descriptor, but it
should be issued automatically after completion of all descriptors in
active list.
It yes, it seems implementation like this would be possible:
* dwc_tx_submit() just always add the descriptor to queue list even if
active list was empty.
* dwc_issue_pending() call dwc_dostart() and move queued descriptor(s)
to active list, if the active list was empty.
But I'm not sure "chain as many as possible at a time" is really
better then "start engine as soon as possible".
---
Atsushi Nemoto
next prev parent reply other threads:[~2009-01-09 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 14:39 Atsushi Nemoto
2009-01-05 14:02 ` Atsushi Nemoto
2009-01-09 14:06 ` Atsushi Nemoto [this message]
2009-01-05 14:30 ` Haavard Skinnemoen
2009-01-05 15:35 ` Atsushi Nemoto
2009-01-05 15:48 ` Haavard Skinnemoen
2009-01-06 1:33 ` Atsushi Nemoto
2009-01-06 10:14 ` Haavard Skinnemoen
2009-01-06 14:31 ` Atsushi Nemoto
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=20090109.230626.126760668.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=dan.j.williams@intel.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.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®