From: Stanimir Varbanov <svarbanov@mm-sol.com>
To: Andy Gross <agross@codeaurora.org>
Cc: Vinod Koul <vinod.koul@intel.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, devicetree@vger.kernel.org
Subject: Re: [Patch v9 2/2] dmaengine: add Qualcomm BAM dma driver
Date: Thu, 03 Apr 2014 19:42:20 +0300 [thread overview]
Message-ID: <533D8F6C.6000606@mm-sol.com> (raw)
In-Reply-To: <1394487622-1679-3-git-send-email-agross@codeaurora.org>
Hi Andy,
On 03/10/2014 11:40 PM, Andy Gross wrote:
> Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA controller
> found in the MSM 8x74 platforms.
>
> Each BAM DMA device is associated with a specific on-chip peripheral. Each
> channel provides a uni-directional data transfer engine that is capable of
> transferring data between the peripheral and system memory (System mode), or
> between two peripherals (BAM2BAM).
>
> The initial release of this driver only supports slave transfers between
> peripherals and system memory.
>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
I tested this driver during wake up of the crypto driver. With your
additions to bam_start_dma() in regards to EOT interrupts I successfully
passed the crypto framework test vectors for the implemented algorithms.
Tested-by: Stanimir Varbanov <svarbanov@mm-sol.com>
regards,
Stan
WARNING: multiple messages have this Message-ID (diff)
From: svarbanov@mm-sol.com (Stanimir Varbanov)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v9 2/2] dmaengine: add Qualcomm BAM dma driver
Date: Thu, 03 Apr 2014 19:42:20 +0300 [thread overview]
Message-ID: <533D8F6C.6000606@mm-sol.com> (raw)
In-Reply-To: <1394487622-1679-3-git-send-email-agross@codeaurora.org>
Hi Andy,
On 03/10/2014 11:40 PM, Andy Gross wrote:
> Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA controller
> found in the MSM 8x74 platforms.
>
> Each BAM DMA device is associated with a specific on-chip peripheral. Each
> channel provides a uni-directional data transfer engine that is capable of
> transferring data between the peripheral and system memory (System mode), or
> between two peripherals (BAM2BAM).
>
> The initial release of this driver only supports slave transfers between
> peripherals and system memory.
>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
I tested this driver during wake up of the crypto driver. With your
additions to bam_start_dma() in regards to EOT interrupts I successfully
passed the crypto framework test vectors for the implemented algorithms.
Tested-by: Stanimir Varbanov <svarbanov@mm-sol.com>
regards,
Stan
next prev parent reply other threads:[~2014-04-03 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 21:40 [Patch v9 0/2] Add Qualcomm BAM dmaengine driver Andy Gross
2014-03-10 21:40 ` Andy Gross
2014-03-10 21:40 ` Andy Gross
2014-03-10 21:40 ` [Patch v9 1/2] dmaengine: qcom_bam_dma: Add device tree binding Andy Gross
2014-03-10 21:40 ` Andy Gross
2014-03-10 21:40 ` [Patch v9 2/2] dmaengine: add Qualcomm BAM dma driver Andy Gross
2014-03-10 21:40 ` Andy Gross
2014-04-03 16:42 ` Stanimir Varbanov [this message]
2014-04-03 16:42 ` Stanimir Varbanov
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=533D8F6C.6000606@mm-sol.com \
--to=svarbanov@mm-sol.com \
--cc=agross@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.