From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Andy Gross <agross@codeaurora.org>, Vinod Koul <vinod.koul@intel.com>
Cc: devicetree@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH 0/2] dmaengine: qcom_bam_dma: Add support for v1.3.0
Date: Mon, 18 Aug 2014 07:23:35 +0100 [thread overview]
Message-ID: <53F19BE7.6070300@linaro.org> (raw)
In-Reply-To: <1397684719-30065-1-git-send-email-agross@codeaurora.org>
Hi Andy,
Any plans to respin these patches with Stanimir's comments?
thanks,
srini
On 16/04/14 22:45, Andy Gross wrote:
> This set of patches adds support for the v1.3.0 version of the QCOM BAM
> dmaengine driver. The older version of the BAM is present in the MSM8x64,
> APQ8064, and IPQ8064 processors.
>
> Due to register address space changes between versions, all of the register
> accesses have to be calculated using different offsets and multipliers that are
> specific to that version of the IP block.
>
> Andy Gross (2):
> dmaengine: qcom_bam_dma: Add v1.3.0 driver support
> dmaengine: qcom_bam_dma: Add binding for v1.3.0
>
> .../devicetree/bindings/dma/qcom_bam_dma.txt | 4 +-
> drivers/dma/qcom_bam_dma.c | 177 +++++++++++++-------
> 2 files changed, 117 insertions(+), 64 deletions(-)
>
prev parent reply other threads:[~2014-08-18 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 21:45 [PATCH 0/2] dmaengine: qcom_bam_dma: Add support for v1.3.0 Andy Gross
2014-04-16 21:45 ` [PATCH 1/2] dmaengine: qcom_bam_dma: Add v1.3.0 driver support Andy Gross
2014-04-17 23:01 ` Stanimir Vabanov
2014-04-18 19:41 ` Andy Gross
2014-04-16 21:45 ` [PATCH 2/2] dmaengine: qcom_bam_dma: Add binding for v1.3.0 Andy Gross
2014-08-18 6:23 ` Srinivas Kandagatla [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=53F19BE7.6070300@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=agross@codeaurora.org \
--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).