From: Vinod Koul <vinod.koul@intel.com>
To: Abhishek Sahu <absahu@codeaurora.org>
Cc: corbet@lwn.net, dan.j.williams@intel.com, andy.gross@linaro.org,
david.brown@linaro.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Support for QCOM BAM DMA command descriptor
Date: Mon, 28 Aug 2017 16:40:36 +0530 [thread overview]
Message-ID: <20170828111036.GE3053@localhost> (raw)
In-Reply-To: <1501596704-21137-1-git-send-email-absahu@codeaurora.org>
On Tue, Aug 01, 2017 at 07:41:41PM +0530, Abhishek Sahu wrote:
> v3:
>
> 1. Added Documentation for new flag
> 2. Changed the flag description
>
> v2:
>
> 1. Added DMA_PREP_CMD flag and used the same for BAM DMA
> command descriptor
> 2. Removed custom mapping API patches
>
> v1:
>
> https://www.spinics.net/lists/dmaengine/msg12009.html
>
> These patches mainly add the support for QCOM BAM command
> descriptor implementing BAM DMA support for some QCOM
> peripherals like QPIC NAND/LCD.
>
> Currently there is no flag in DMA API which tells the DMA
> controller that the passed data is in command descriptor
> format so added the flag in DMA API for this.
Applied, thanks
> Abhishek Sahu (3):
> dmaengine: add DMA_PREP_CMD for non-Data descriptors.
> dmaengine: qcom: bam_dma: wrapper functions for command descriptor
> dmaengine: qcom: bam_dma: add command descriptor flag
>
> Documentation/dmaengine/provider.txt | 7 ++++
> drivers/dma/qcom/bam_dma.c | 6 ++-
> include/linux/dma/qcom_bam_dma.h | 79 ++++++++++++++++++++++++++++++++++++
> include/linux/dmaengine.h | 4 ++
> 4 files changed, 95 insertions(+), 1 deletion(-)
> create mode 100644 include/linux/dma/qcom_bam_dma.h
>
> --
> QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
>
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
~Vinod
prev parent reply other threads:[~2017-08-28 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 14:11 [PATCH v3 0/3] Support for QCOM BAM DMA command descriptor Abhishek Sahu
2017-08-01 14:11 ` [PATCH v3 1/3] dmaengine: add DMA_PREP_CMD for non-Data descriptors Abhishek Sahu
2017-08-01 14:11 ` [PATCH v3 2/3] dmaengine: qcom: bam_dma: wrapper functions for command descriptor Abhishek Sahu
2017-08-01 14:11 ` [PATCH v3 3/3] dmaengine: qcom: bam_dma: add command descriptor flag Abhishek Sahu
2017-08-28 11:10 ` Vinod Koul [this message]
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=20170828111036.GE3053@localhost \
--to=vinod.koul@intel.com \
--cc=absahu@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=david.brown@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.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