[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180117101835.GM18649@localhost>
Date: Wed, 17 Jan 2018 15:48:35 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: srinivas.kandagatla@...aro.org
Cc: Andy Gross <andy.gross@...aro.org>, dmaengine@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
David Brown <david.brown@...aro.org>,
Dan Williams <dan.j.williams@...el.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
yanhe@...cinc.com, ramkri@....qualcomm.com, sdharia@...cinc.com
Subject: Re: [PATCH 0/4] dmaengine: qcom: bam_dma: fixes for remotely
controlled bam
On Tue, Jan 16, 2018 at 07:02:32PM +0000, srinivas.kandagatla@...aro.org wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla@...aro.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
Powered by blists - more mailing lists