From: Abhishek Sahu <absahu@codeaurora.org>
To: vinod.koul@intel.com, dan.j.williams@intel.com, andy.gross@linaro.org
Cc: stanimir.varbanov@linaro.org, mcgrof@suse.com,
okaya@codeaurora.org, pramod.gurav@linaro.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Abhishek Sahu <absahu@codeaurora.org>
Subject: [PATCH 0/5] Support for QCA BAM DMA command descriptor
Date: Thu, 15 Dec 2016 15:25:50 +0530 [thread overview]
Message-ID: <1481795755-15302-1-git-send-email-absahu@codeaurora.org> (raw)
These patches mainly adds the support for QCA BAM command
descriptor and per SG flags which are required for implementing
BAM DMA support for some QCA peripherals like QPIC NAND/LCD.
The BAM command descriptors perform all register reads and writes
while data descriptors do data transfer. The QPIC NAND forms the
chain of command and data descriptors for full page read/write and
submit it to BAM DMA.
Following are the limitation of existing DMA mapping function which
forces us to go for separate DMA custom mapping function and SG.
1. BAM descriptor has multiple flags which cannot be mapped with
generic DMA engine flags.
2. For each page code word i.e 512 bytes, approx 10-15 register
read/writes are required. The NAND driver combines all these into
SGL and submit it to BAM. Each register read/writes require
different flags and the current generic SG does not have field to
set dma flags for each SG. We cannot add flag parameter in generic
SG since it is being used by different subsystems across linux
kernel.
So these patches add custom mapping function, QCA specific SG which
has dma flag for each SG and its DMA mapping functions. With these,
peripheral driver can set per SG flag and submit it to custom DMA
mapping function.
Abhishek Sahu (5):
dmaengine: qca: bam_dma: Add header file for bam driver
dmaengine: Add support for custom data mapping
dmaengine: qca: bam_dma: Add support for bam sgl
dmaengine: qca: bam_dma: implement custom data mapping
dmaengine: qca: bam_dma: implement command descriptor
drivers/dma/qcom/bam_dma.c | 98 +++++++++++++++++++++--
include/linux/dma/qcom_bam_dma.h | 162 +++++++++++++++++++++++++++++++++++++++
include/linux/dmaengine.h | 5 ++
3 files changed, 258 insertions(+), 7 deletions(-)
create mode 100644 include/linux/dma/qcom_bam_dma.h
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2016-12-15 9:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 9:55 Abhishek Sahu [this message]
2016-12-15 9:55 ` [PATCH 1/5] dmaengine: qca: bam_dma: Add header file for bam driver Abhishek Sahu
2016-12-15 9:55 ` [PATCH 2/5] dmaengine: Add support for custom data mapping Abhishek Sahu
2016-12-18 16:26 ` Vinod Koul
2016-12-19 5:06 ` Andy Gross
2016-12-19 15:49 ` Vinod Koul
2016-12-19 17:52 ` Andy Gross
2016-12-20 19:28 ` Abhishek Sahu
2016-12-20 20:25 ` Andy Gross
2016-12-21 19:34 ` Abhishek Sahu
2016-12-29 17:54 ` Andy Gross
2017-01-02 14:25 ` Abhishek Sahu
2017-01-02 16:12 ` Andy Gross
2017-01-19 5:01 ` Vinod Koul
2017-01-19 14:13 ` Andy Gross
2017-01-19 14:57 ` Abhishek Sahu
2017-01-20 16:56 ` Vinod Koul
2017-04-07 13:58 ` Abhishek Sahu
2016-12-15 9:55 ` [PATCH 3/5] dmaengine: qca: bam_dma: Add support for bam sgl Abhishek Sahu
2016-12-15 9:55 ` [PATCH 4/5] dmaengine: qca: bam_dma: implement custom data mapping Abhishek Sahu
2016-12-15 9:55 ` [PATCH 5/5] dmaengine: qca: bam_dma: implement command descriptor Abhishek Sahu
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=1481795755-15302-1-git-send-email-absahu@codeaurora.org \
--to=absahu@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=okaya@codeaurora.org \
--cc=pramod.gurav@linaro.org \
--cc=stanimir.varbanov@linaro.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).