From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Cc: Andy Gross <andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
David Brown <david.brown-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Dan Williams
<dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yanhe-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org,
ramkri-Rm6X0d1/PG5y9aJCnZT0Uw@public.gmane.org,
sdharia-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org
Subject: Re: [PATCH 0/4] dmaengine: qcom: bam_dma: fixes for remotely controlled bam
Date: Wed, 17 Jan 2018 15:48:35 +0530 [thread overview]
Message-ID: <20180117101835.GM18649@localhost> (raw)
In-Reply-To: <20180116190236.14558-1-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Tue, Jan 16, 2018 at 07:02:32PM +0000, srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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.
What do you mean by "remotely controlled" in this series?
>
> 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.
>
> Thanks,
> Srini
>
> Srinivas Kandagatla (4):
> dmaengine: qcom: bam_dma: make bam clk optional
> dmaengine: qcom: bam_dma: add num-channels binding for remotely
> controlled
> dmaengine: qcom: bam_dma: do not write to global regs in remote mode
> dmaengine: qcom: bam_dma: Add num-ees dt binding for remotely
> controlled
>
> .../devicetree/bindings/dma/qcom_bam_dma.txt | 4 ++
> drivers/dma/qcom/bam_dma.c | 56 +++++++++++++++-------
> 2 files changed, 43 insertions(+), 17 deletions(-)
>
> --
> 2.15.1
>
--
~Vinod
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: srinivas.kandagatla@linaro.org
Cc: Andy Gross <andy.gross@linaro.org>,
dmaengine@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
David Brown <david.brown@linaro.org>,
Dan Williams <dan.j.williams@intel.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
yanhe@quicinc.com, ramkri@qti.qualcomm.com, sdharia@quicinc.com
Subject: Re: [PATCH 0/4] dmaengine: qcom: bam_dma: fixes for remotely controlled bam
Date: Wed, 17 Jan 2018 15:48:35 +0530 [thread overview]
Message-ID: <20180117101835.GM18649@localhost> (raw)
In-Reply-To: <20180116190236.14558-1-srinivas.kandagatla@linaro.org>
On Tue, Jan 16, 2018 at 07:02:32PM +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.
What do you mean by "remotely controlled" in this series?
>
> 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.
>
> Thanks,
> Srini
>
> Srinivas Kandagatla (4):
> dmaengine: qcom: bam_dma: make bam clk optional
> dmaengine: qcom: bam_dma: add num-channels binding for remotely
> controlled
> dmaengine: qcom: bam_dma: do not write to global regs in remote mode
> dmaengine: qcom: bam_dma: Add num-ees dt binding for remotely
> controlled
>
> .../devicetree/bindings/dma/qcom_bam_dma.txt | 4 ++
> drivers/dma/qcom/bam_dma.c | 56 +++++++++++++++-------
> 2 files changed, 43 insertions(+), 17 deletions(-)
>
> --
> 2.15.1
>
--
~Vinod
next prev parent reply other threads:[~2018-01-17 10:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 19:02 [PATCH 0/4] dmaengine: qcom: bam_dma: fixes for remotely controlled bam srinivas.kandagatla
[not found] ` <20180116190236.14558-1-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-01-17 10:18 ` Vinod Koul [this message]
2018-01-17 10:18 ` Vinod Koul
2018-01-17 10:55 ` Srinivas Kandagatla
2018-01-17 15:59 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-01-16 19:02 [1/4] dmaengine: qcom: bam_dma: make bam clk optional Srinivas Kandagatla
2018-01-16 19:02 ` [PATCH 1/4] " srinivas.kandagatla
2018-01-16 19:02 [2/4] dmaengine: qcom: bam_dma: add num-channels binding for remotely controlled Srinivas Kandagatla
2018-01-16 19:02 ` [PATCH 2/4] " srinivas.kandagatla
2018-01-16 19:02 ` srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A
2018-01-16 19:02 [3/4] dmaengine: qcom: bam_dma: do not write to global regs in remote mode Srinivas Kandagatla
2018-01-16 19:02 ` [PATCH 3/4] " srinivas.kandagatla
2018-01-16 19:02 [4/4] dmaengine: qcom: bam_dma: Add num-ees dt binding for remotely controlled Srinivas Kandagatla
2018-01-16 19:02 ` [PATCH 4/4] " srinivas.kandagatla
2018-01-16 19:38 [1/4] dmaengine: qcom: bam_dma: make bam clk optional Sagar Dharia
2018-01-16 19:38 ` [PATCH 1/4] " Sagar Dharia
2018-01-17 9:46 [1/4] " Srinivas Kandagatla
2018-01-17 9:46 ` [PATCH 1/4] " Srinivas Kandagatla
2018-01-19 5:52 [1/4] " Vinod Koul
2018-01-19 5:52 ` [PATCH 1/4] " Vinod Koul
2018-01-19 5:55 [2/4] dmaengine: qcom: bam_dma: add num-channels binding for remotely controlled Vinod Koul
2018-01-19 5:55 ` [PATCH 2/4] " Vinod Koul
2018-01-22 9:55 [1/4] dmaengine: qcom: bam_dma: make bam clk optional Srinivas Kandagatla
2018-01-22 9:55 ` [PATCH 1/4] " Srinivas Kandagatla
2018-01-22 9:55 [2/4] dmaengine: qcom: bam_dma: add num-channels binding for remotely controlled Srinivas Kandagatla
2018-01-22 9:55 ` [PATCH 2/4] " Srinivas Kandagatla
2018-01-23 9:19 [1/4] dmaengine: qcom: bam_dma: make bam clk optional Vinod Koul
2018-01-23 9:19 ` [PATCH 1/4] " Vinod Koul
2018-01-23 9:19 ` Vinod Koul
2018-01-23 9:20 [1/4] " Srinivas Kandagatla
2018-01-23 9:20 ` [PATCH 1/4] " Srinivas Kandagatla
2018-01-23 9:20 ` Srinivas Kandagatla
2018-01-29 16:19 [2/4] dmaengine: qcom: bam_dma: add num-channels binding for remotely controlled Rob Herring
2018-01-29 16:19 ` [PATCH 2/4] " Rob Herring
2018-01-29 16:19 ` Rob Herring
2018-01-29 16:21 [4/4] dmaengine: qcom: bam_dma: Add num-ees dt " Rob Herring
2018-01-29 16:21 ` [PATCH 4/4] " Rob Herring
2018-01-29 16:21 ` Rob Herring
2018-01-30 9:18 [4/4] " Srinivas Kandagatla
2018-01-30 9:18 ` [PATCH 4/4] " Srinivas Kandagatla
2018-01-30 9:18 ` Srinivas Kandagatla
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=20180117101835.GM18649@localhost \
--to=vinod.koul-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=david.brown-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=ramkri-Rm6X0d1/PG5y9aJCnZT0Uw@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sdharia-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org \
--cc=srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=yanhe-jfJNa2p1gH1BDgjK7y7TUQ@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 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.