From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stanimir Varbanov Subject: Re: [Patch v9 2/2] dmaengine: add Qualcomm BAM dma driver Date: Thu, 03 Apr 2014 19:42:20 +0300 Message-ID: <533D8F6C.6000606@mm-sol.com> References: <1394487622-1679-1-git-send-email-agross@codeaurora.org> <1394487622-1679-3-git-send-email-agross@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from ns.mm-sol.com ([37.157.136.199]:57282 "EHLO extserv.mm-sol.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752651AbaDCQmW (ORCPT ); Thu, 3 Apr 2014 12:42:22 -0400 In-Reply-To: <1394487622-1679-3-git-send-email-agross@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Andy Gross Cc: Vinod Koul , Dan Williams , 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 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 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 regards, Stan From mboxrd@z Thu Jan 1 00:00:00 1970 From: svarbanov@mm-sol.com (Stanimir Varbanov) Date: Thu, 03 Apr 2014 19:42:20 +0300 Subject: [Patch v9 2/2] dmaengine: add Qualcomm BAM dma driver In-Reply-To: <1394487622-1679-3-git-send-email-agross@codeaurora.org> References: <1394487622-1679-1-git-send-email-agross@codeaurora.org> <1394487622-1679-3-git-send-email-agross@codeaurora.org> Message-ID: <533D8F6C.6000606@mm-sol.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.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 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 regards, Stan