From: Dan Williams <dan.j.williams@intel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
linux-arm-kernel@lists.infradead.org,
Alan Cox <alan@linux.intel.com>
Subject: [PATCH] dmaengine: add slave-dma maintainer
Date: Mon, 14 Feb 2011 03:58:43 -0800 [thread overview]
Message-ID: <20110214115523.25875.45143.stgit@localhost6.localdomain6> (raw)
Slave-dma has become the predominant usage model for dmaengine and needs
special attention. Memory-to-memory dma usage cases will continue to be
maintained by Dan.
Cc: Alan Cox <alan@linux.intel.com>
Acked-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
Several factors have contributed to the need to add a co-maintainer
to dmaengine. First my time is being consumed in other areas [1].
Also, after Russell's review of amba-pl08x it became clear that the
semantics of the slave interface need to specified [2]. My work on the
iop-adma and ioatdma drivers has been limited to the memory-to-memory
use cases (NET_DMA and ASYNC_TX_DMA). Without direct slave-dma api
experience (client driver or dma driver) it is difficult to parse its
needs outside of its base similarities with the memory-to-memory case.
I have asked my colleague, Vinod Koul, to:
1/ put more definition around the slave api and usages to try to ensure
consistent behavior across drivers (as much as possible)
2/ help review and merge new drivers according to this definition
Vinod wrote the intel_mid_dma driver and expects to be involved with
slave-dma for the foreseeable future.
I will continue to maintain the memory-to-memory and related async_tx
usages of dmaengine (that need fixing [3]), but it is clear that this
usage has become a secondary role for the dmaengine infrastructure.
--
Dan
[1]: http://marc.info/?l=linux-scsi&m=129703780424729&w=2
[2]: http://marc.info/?l=linux-arm-kernel&m=129383280413633&w=2
[3]: http://marc.info/?l=linux-arm-kernel&m=129407269402930&w=2
MAINTAINERS | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 55592f8..e2f0992 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2124,6 +2124,7 @@ S: Supported
F: fs/dlm/
DMA GENERIC OFFLOAD ENGINE SUBSYSTEM
+M: Vinod Koul <vinod.koul@intel.com>
M: Dan Williams <dan.j.williams@intel.com>
S: Supported
F: drivers/dma/
next reply other threads:[~2011-02-14 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 11:58 Dan Williams [this message]
2011-02-15 19:35 ` [PATCH] dmaengine: add slave-dma maintainer 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=20110214115523.25875.45143.stgit@localhost6.localdomain6 \
--to=dan.j.williams@intel.com \
--cc=alan@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=vinod.koul@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;
as well as URLs for NNTP newsgroup(s).