From: "Koul, Vinod" <vinod.koul@intel.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
Dan <dan.j.williams@intel.com>,
Per Forlin <per.forlin@linaro.org>,
Vinod Koul <vinod.koul@intel.com>
Subject: [PATCH 2/2] dmaengine: add TODO items for future work on dma drivers
Date: Wed, 25 May 2011 17:09:30 +0530 [thread overview]
Message-ID: <1306323570-11133-3-git-send-email-vinod.koul@intel.com> (raw)
In-Reply-To: <1306323570-11133-1-git-send-email-vinod.koul@intel.com>
From: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
---
drivers/dma/TODO | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
create mode 100644 drivers/dma/TODO
diff --git a/drivers/dma/TODO b/drivers/dma/TODO
new file mode 100644
index 0000000..b67d184
--- /dev/null
+++ b/drivers/dma/TODO
@@ -0,0 +1,12 @@
+TODO for slave dma
+
+1. Move remaining drivers to use new slave interface
+2. Remove old slave pointer machansim
+3. Make issue_pending to start the transaction in below drivers
+ - mpc512x_dma
+ - imx-dma
+ - imx-sdma
+ - mxs-dma.c
+ - dw_dmac
+ - intel_mid_dma
+ - ste_dma40
--
1.7.0.4
next prev parent reply other threads:[~2011-05-25 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 11:39 [PATCH v2 0/2] dmaengine: add slave documentation Koul, Vinod
2011-05-25 11:39 ` [PATCH 1/2] dmaengine: Add API documentation for slave dma usage Koul, Vinod
2011-05-25 11:39 ` Koul, Vinod [this message]
2011-05-25 12:39 ` [PATCH 2/2] dmaengine: add TODO items for future work on dma drivers Per Forlin
2011-05-25 12:15 ` Koul, Vinod
2011-05-25 12:54 ` Per Forlin
2011-05-25 12:47 ` Linus Walleij
2011-05-25 12:23 ` Koul, Vinod
2011-05-26 7:36 ` Russell King - ARM Linux
2011-05-26 12:25 ` Koul, Vinod
2011-05-26 13:38 ` Russell King - ARM Linux
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=1306323570-11133-3-git-send-email-vinod.koul@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=per.forlin@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®