From: Andy Gross <agross@codeaurora.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, Andy Gross <agross@codeaurora.org>
Subject: [PATCH 0/2] Add Qualcomm ADM dmaengine driver
Date: Thu, 26 Jun 2014 15:30:14 -0500 [thread overview]
Message-ID: <1403814616-23917-1-git-send-email-agross@codeaurora.org> (raw)
This patch set introduces the dmaengine driver for the Qualcomm Application
Data Mover (ADM) DMA controller present on MSM8960, APQ8064, and IPQ8064
devices.
The initial version of this driver will only support slave DMA operations
between system memory and peripherals. Flow control via the CRCI (client rate
control interface) is supported and can be configured via device tree
configuration. Flow control usage is required for some peripheral devices.
Andy Gross (2):
dmaengine: Add QCOM ADM DMA driver
dmaengine: qcom_adm: Add device tree binding
Documentation/devicetree/bindings/dma/qcom_adm.txt | 60 ++
drivers/dma/Kconfig | 10 +
drivers/dma/Makefile | 1 +
drivers/dma/qcom_adm.c | 872 ++++++++++++++++++++
4 files changed, 943 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/qcom_adm.txt
create mode 100644 drivers/dma/qcom_adm.c
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-06-26 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 20:30 Andy Gross [this message]
2014-06-26 20:30 ` [PATCH 1/2] dmaengine: Add QCOM ADM DMA driver Andy Gross
2014-06-26 20:30 ` [PATCH 2/2] dmaengine: qcom_adm: Add device tree binding Andy Gross
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=1403814616-23917-1-git-send-email-agross@codeaurora.org \
--to=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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).