From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
linux-kernel@vger.kernel.org, Dan Williams <djbw@fb.com>,
Arnd Bergmann <arnd@arndb.de>, Jon Hunter <jon-hunter@ti.com>,
Stephen Warren <swarren@nvidia.com>,
Benoit Cousson <b-cousson@ti.com>,
Shawn Guo <shawn.guo@linaro.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Sascha Hauer <kernel@pengutronix.de>,
Kukjin Kim <kgene.kim@samsung.com>,
viresh kumar <viresh.kumar@linaro.org>,
Paul Mundt <lethal@linux-sh.org>,
Per Forlin <per.forlin@stericsson.com>,
Rabin VINCENT <rabin.vincent@stericsson.com>
Subject: Re: [PATCH] dmaengine: add dmanegine slave map api's
Date: Tue, 18 Sep 2012 21:52:48 +0100 [thread overview]
Message-ID: <20120918205248.GZ12245@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACRpkdaBiJXowtWm=yTV4_7=6P=SFuVuZo8+icQfE0EN87A23g@mail.gmail.com>
On Tue, Sep 18, 2012 at 02:20:53PM +0200, Linus Walleij wrote:
> But we're probably the odd exception here so nevermind.
> One day we may test to rip out the logical channel handling and
> use Russell's virtual channel lib to run the show as an experiment.
Note that I'm beginning to add support for the async_tx API stuff into
the virtual channel DMA support, so it can handle the inter-dependencies
between descriptors that async_tx needs.
I'm currently trying to get the design of this right, as the async_tx
needs yet-another-list of descriptors which have been submitted, may
have been processed and completed, but for whatever reason have not
been acknowledged. Such descriptors can not be freed because the
async_tx API may hold a reference to them, and may dereference them
at any moment to check the dependency situation.
There's a clue in that paragraph about how the DMA engine TX descriptors
_should_ be handled. "hold a reference" is the clue. Or another way to
say it, a kref should be embedded in the structure, providing us with
proper reference counting - and descriptors should only be 'freed'
(whether that means actually freeing them or placing them into a free
list) when the last reference is dropped. That's _much_ better to
understand than this DMA_CTRL_ACK business...
I think switching stuff over to that may simplify things, but it's
going to be absolute hell modifying all the existing DMA engine drivers,
many of which I have no way to test (and probably as Dan has left Intel,
we have a pile of totally untestable drivers now.)
next prev parent reply other threads:[~2012-09-18 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 9:33 Vinod Koul
2012-09-14 9:39 ` [RFC] " Vinod Koul
2012-09-14 9:41 ` [PATCH] " Russell King - ARM Linux
2012-09-14 10:51 ` Vinod Koul
2012-09-14 11:18 ` Russell King - ARM Linux
2012-09-17 3:40 ` Vinod Koul
2012-09-17 8:36 ` Russell King - ARM Linux
2012-09-17 9:50 ` Vinod Koul
2012-09-17 21:57 ` Russell King - ARM Linux
2012-09-18 3:18 ` Vinod Koul
2012-09-18 12:20 ` Linus Walleij
2012-09-18 20:52 ` Russell King - ARM Linux [this message]
2012-09-18 21:04 ` Linus Walleij
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=20120918205248.GZ12245@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=djbw@fb.com \
--cc=g.liakhovetski@gmx.de \
--cc=jon-hunter@ti.com \
--cc=kernel@pengutronix.de \
--cc=kgene.kim@samsung.com \
--cc=lethal@linux-sh.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=per.forlin@stericsson.com \
--cc=rabin.vincent@stericsson.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.com \
--cc=vinod.koul@linux.intel.com \
--cc=viresh.kumar@linaro.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®