From: gpramod-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
To: Stanimir Varbanov <svarbanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
Cc: andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-arm-msm-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
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
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
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
[not found] ` <1458640151-15150-1-git-send-email-gpramod-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-03-22 9:55 ` [PATCH 0/2] Bypass BAM init if Remotely controlled Stanimir Varbanov
[not found] ` <56F116AC.2000704-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2016-03-22 10:36 ` gpramod-sgV2jX0FEOL9JmXXK+q4OQ [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-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-msm-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=svarbanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org \
--cc=vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).