From: Vinod Koul <vinod.koul@intel.com>
To: srinivas.kandagatla@linaro.org
Cc: andy.gross@linaro.org, dmaengine@vger.kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com, david.brown@linaro.org,
dan.j.williams@intel.com, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-soc@vger.kernel.org, yanhe@quicinc.com,
ramkri@qti.qualcomm.com, sdharia@quicinc.com
Subject: Re: [PATCH v3 0/5] dmaengine: qcom: bam_dma: fixes for remotely controlled bam
Date: Thu, 1 Mar 2018 14:14:56 +0530 [thread overview]
Message-ID: <20180301084456.GG15443@localhost> (raw)
In-Reply-To: <20180215122511.13517-1-srinivas.kandagatla@linaro.org>
On Thu, Feb 15, 2018 at 12:25:06PM +0000, srinivas.kandagatla@linaro.org wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>
> Hi Andy,
>
> I did hit few issues while trying out SLIMBus BAM on DB820c, this BAM instance
> is remotely controlled and powered up after ADSP is booted using QMI commands.
>
> Firstly some of the master registers are written even when the BAM is remotely
> controlled, and secondly reading registers when bam is not ready yet.
>
> These 4 patches address these issues, there are few more issues like doing PM
> in simillar usecase, these will be addressed soon.
Applied all, thanks
--
~Vinod
next prev parent reply other threads:[~2018-03-01 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 12:25 [PATCH v3 0/5] dmaengine: qcom: bam_dma: fixes for remotely controlled bam srinivas.kandagatla
2018-03-01 8:44 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-15 12:25 [v3,1/5] dmaengine: qcom: bam_dma: make bam clk optional Srinivas Kandagatla
2018-02-15 12:25 ` [PATCH v3 1/5] " srinivas.kandagatla
2018-02-15 12:25 [v3,2/5] dt-bindings: dmaengine: bam_dma: add remote controlled bindings Srinivas Kandagatla
2018-02-15 12:25 ` [PATCH v3 2/5] " srinivas.kandagatla
2018-02-15 12:25 [v3,3/5] dmaengine: qcom: bam_dma: get num-channels and num-ees from dt Srinivas Kandagatla
2018-02-15 12:25 ` [PATCH v3 3/5] " srinivas.kandagatla
2018-02-15 12:25 ` srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A
2018-02-15 12:25 [v3,4/5] dmaengine: qcom: bam_dma: do not write to global regs in remote mode Srinivas Kandagatla
2018-02-15 12:25 ` [PATCH v3 4/5] " srinivas.kandagatla
2018-02-15 12:25 [v3,5/5] dmaengine: qcom: bam_dma: disable runtime pm on remote controlled Srinivas Kandagatla
2018-02-15 12:25 ` [PATCH v3 5/5] " srinivas.kandagatla
2018-02-19 14:35 [v3,2/5] dt-bindings: dmaengine: bam_dma: add remote controlled bindings Rob Herring
2018-02-19 14:35 ` [PATCH v3 2/5] " Rob Herring
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=20180301084456.GG15443@localhost \
--to=vinod.koul@intel.com \
--cc=andy.gross@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ramkri@qti.qualcomm.com \
--cc=robh+dt@kernel.org \
--cc=sdharia@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=yanhe@quicinc.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.