From: Vinod Koul <vinod.koul@intel.com>
To: dmaengine@vger.kernel.org
Cc: Vinod Koul <vinod.koul@intel.com>, Zhang Wei <zw@zh-kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 5/6] dmaengine: freescale: remove FSLDMA_EXTERNAL_START control method
Date: Sat, 11 Oct 2014 21:16:47 +0530 [thread overview]
Message-ID: <1413042408-28491-6-git-send-email-vinod.koul@intel.com> (raw)
In-Reply-To: <1413042408-28491-1-git-send-email-vinod.koul@intel.com>
since users have been move to fsl_dma_external_start() API, so remove this
now
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
---
drivers/dma/fsldma.c | 9 ---------
1 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
index 0cded86..994bcb2 100644
--- a/drivers/dma/fsldma.c
+++ b/drivers/dma/fsldma.c
@@ -1012,15 +1012,6 @@ static int fsl_dma_device_control(struct dma_chan *dchan,
chan->set_request_count(chan, size);
return 0;
- case FSLDMA_EXTERNAL_START:
-
- /* make sure the channel supports external start */
- if (!chan->toggle_ext_start)
- return -ENXIO;
-
- chan->toggle_ext_start(chan, arg);
- return 0;
-
default:
return -ENXIO;
}
--
1.7.0.4
next prev parent reply other threads:[~2014-10-11 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 15:46 [PATCH 0/6] dmaengine: remove FSLDMA_EXTERNAL_START Vinod Koul
2014-10-11 15:46 ` [PATCH 1/6] dmaengine: add dmaengine_prep_dma_sg() helper Vinod Koul
2014-10-11 15:46 ` [PATCH 2/6] dmaengine: freescale: add and export fsl_dma_external_start() Vinod Koul
2014-10-11 15:46 ` [PATCH 3/6] carma-fpga: use dmaengine_xxx() API Vinod Koul
2014-10-11 15:46 ` [PATCH 4/6] carma-fpga: move to fsl_dma_external_start() Vinod Koul
2014-10-11 15:46 ` Vinod Koul [this message]
2014-10-11 15:46 ` [PATCH 6/6] dmaengine: remove FSLDMA_EXTERNAL_START Vinod Koul
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=1413042408-28491-6-git-send-email-vinod.koul@intel.com \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=zw@zh-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;
as well as URLs for NNTP newsgroup(s).