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 0/6] dmaengine: remove FSLDMA_EXTERNAL_START
Date: Sat, 11 Oct 2014 21:16:42 +0530 [thread overview]
Message-ID: <1413042408-28491-1-git-send-email-vinod.koul@intel.com> (raw)
FSLDMA_EXTERNAL_START is one of the custom methods in device_control. Since
we are planning to deprecate device_control, we should move this to an API.
This serries adds the fsl_dma_external_start() API for users and also
converts the users.
I would like this to be merged thru dmanegine tree due to new dependency.
Vinod Koul (6):
dmaengine: add dmaengine_prep_dma_sg() helper
dmaengine: freescale: add and export fsl_dma_external_start()
carma-fpga: use dmaengine_xxx() API
carma-fpga: move to fsl_dma_external_start()
dmaengine: freescale: remove FSLDMA_EXTERNAL_START control method
dmaengine: remove FSLDMA_EXTERNAL_START
drivers/dma/fsldma.c | 25 +++++++++++++++----------
drivers/misc/carma/carma-fpga-program.c | 12 ++++++------
include/linux/dmaengine.h | 13 ++++++++++---
include/linux/fsldma.h | 13 +++++++++++++
4 files changed, 44 insertions(+), 19 deletions(-)
create mode 100644 include/linux/fsldma.h
next 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 Vinod Koul [this message]
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 ` [PATCH 5/6] dmaengine: freescale: remove FSLDMA_EXTERNAL_START control method Vinod Koul
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-1-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).