From: gpramod@codeaurora.org
To: Stanimir Varbanov <svarbanov@mm-sol.com>
Cc: andy.gross@linaro.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, dan.j.williams@intel.com,
vinod.koul@intel.com, okaya@codeaurora.org,
architt@codeaurora.org, linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCH 0/2] Bypass BAM init if Remotely controlled
Date: Tue, 22 Mar 2016 16:06:35 +0530 [thread overview]
Message-ID: <bef2b78808a8dc823c0f2eb9f25e73e1@codeaurora.org> (raw)
In-Reply-To: <56F116AC.2000704@mm-sol.com>
On 2016-03-22 15:25, Stanimir Varbanov wrote:
> On 03/22/2016 11:49 AM, Pramod Gurav wrote:
>> On some QOCM platforms(eg 8996) BAM control registers are managed
>> remotely
>> hence can not be accessed by application processor for writes. So skip
>> the bam_init
>> for any such platform if DT property is set.
>>
>> Tested on 8996 (BAM Global control is through remote) and DB410C
>> boards.
>> Tested with i2c DMA on these targets which uses BAM as DMA controller.
>
> I have similar patches at [1] already, could you check them first.
>
>
> [1] https://lkml.org/lkml/2015/12/1/113
Thanks. I should have known them. Will test them and and provide
Tested-by. :)
Regards,
Pramod
next prev parent reply other threads:[~2016-03-22 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 9:49 [PATCH 0/2] Bypass BAM init if Remotely controlled Pramod Gurav
2016-03-22 9:49 ` [PATCH 1/2] dmaengine: qcom_bam_dma: Clear IRQ only if its set Pramod Gurav
2016-03-22 9:49 ` [PATCH 2/2] dmaengine: qcom_bam_dma: Bypass BAM init if not managed locally Pramod Gurav
2016-03-23 15:09 ` Rob Herring
2016-03-22 9:55 ` [PATCH 0/2] Bypass BAM init if Remotely controlled Stanimir Varbanov
2016-03-22 10:36 ` gpramod [this message]
2016-04-05 18:19 ` Vinod Koul
2016-04-05 21:21 ` Andy Gross
2016-04-05 21:27 ` Koul, Vinod
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=bef2b78808a8dc823c0f2eb9f25e73e1@codeaurora.org \
--to=gpramod@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=svarbanov@mm-sol.com \
--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