From: "Dan Williams" <dan.j.williams@intel.com>
To: "Guennadi Liakhovetski" <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] dmaengine redux continued
Date: Thu, 4 Dec 2008 11:52:28 -0700 [thread overview]
Message-ID: <e9c3a7c20812041052l7fa7c148jf0a40318a2fe8cf4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812040937010.5079@axis700.grange>
On Thu, Dec 4, 2008 at 1:51 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> What about the last hunk from the patch at
>
> http://marc.info/?l=linux-arm-kernel&m=122607472721145&w=2
>
> ? Can we add this tx_free pointer? Would you like me to submit it as a
> separate patch? I'd like to be able to reuse tx-descriptors in clients, so
> I then have to explicitly release them in the dmaengine device
> (controller) driver.
>
I took a look but the description does not explain why the driver
needs an explicit release. In what cases is the implied release, when
the descriptor is acked && done, insufficient?
next prev parent reply other threads:[~2008-12-04 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 0:46 Dan Williams
2008-12-04 0:46 ` [PATCH 1/4] dmaengine: add a release for dma class devices and dependent infrastructure Dan Williams
2008-12-04 1:07 ` Stephen Hemminger
2008-12-04 0:46 ` [PATCH 2/4] dmaengine: use idr for registering dma device numbers Dan Williams
2008-12-04 0:46 ` [PATCH 3/4] dmaengine: advertise all channels on a device to dma_filter_fn Dan Williams
2008-12-04 0:47 ` [PATCH 4/4] dmaengine: bump initcall level to arch_initcall Dan Williams
2008-12-04 8:51 ` [PATCH 0/4] dmaengine redux continued Guennadi Liakhovetski
2008-12-04 18:52 ` Dan Williams [this message]
2008-12-04 20:03 ` Guennadi Liakhovetski
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=e9c3a7c20812041052l7fa7c148jf0a40318a2fe8cf4@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@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 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®