[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180214144459.29813-1-srinivas.kandagatla@linaro.org>
Date: Wed, 14 Feb 2018 14:44:54 +0000
From: srinivas.kandagatla@...aro.org
To: vinod.koul@...el.com, andy.gross@...aro.org,
dmaengine@...r.kernel.org
Cc: robh+dt@...nel.org, mark.rutland@....com, david.brown@...aro.org,
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,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Subject: [PATCH v2 0/5] dmaengine: qcom: bam_dma: fixes for remotely controlled bam
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.
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
Changes since v1:
- Move dt bindings to separate patch
- merge num-channels and num-ees driver changes
- fixed few typos.
- added runtime pm disable, as suggested by Sagar
Srinivas Kandagatla (5):
dmaengine: qcom: bam_dma: make bam clk optional
dt-bindings: dmaengine: bam_dma: add remote controlled bindings
dmaengine: qcom: bam_dma: get num-channels and num-ees from dt
dmaengine: qcom: bam_dma: do not write to global regs in remote mode
dmaengine: qcom: bam_dma: disable runtime pm on remote controlled
.../devicetree/bindings/dma/qcom_bam_dma.txt | 4 ++
drivers/dma/qcom/bam_dma.c | 66 +++++++++++++++-------
2 files changed, 51 insertions(+), 19 deletions(-)
--
2.15.1
Powered by blists - more mailing lists