From: patchwork-bot+linux-arm-msm@kernel.org
To: Thara Gopinath <thara.gopinath@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] dma: qcom: bam_dma: Manage clocks when controlled_remotely is set
Date: Mon, 01 Mar 2021 19:59:44 +0000 [thread overview]
Message-ID: <161462878441.6187.7566254509554088332.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210126211859.790892-1-thara.gopinath@linaro.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Tue, 26 Jan 2021 16:18:59 -0500 you wrote:
> When bam dma is "controlled remotely", thus far clocks were not controlled
> from the Linux. In this scenario, Linux was disabling runtime pm in bam dma
> driver and not doing any clock management in suspend/resume hooks.
>
> With introduction of crypto engine bam dma, the clock is a rpmh resource
> that can be controlled from both Linux and TZ/remote side. Now bam dma
> clock is getting enabled during probe even though the bam dma can be
> "controlled remotely". But due to clocks not being handled properly,
> bam_suspend generates a unbalanced clk_unprepare warning during system
> suspend.
>
> [...]
Here is the summary with links:
- [v2] dma: qcom: bam_dma: Manage clocks when controlled_remotely is set
https://git.kernel.org/qcom/c/123935a4ca93
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-01 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 21:18 [PATCH v2] dma: qcom: bam_dma: Manage clocks when controlled_remotely is set Thara Gopinath
2021-01-27 1:33 ` Shawn Guo
2021-01-27 5:33 ` Bjorn Andersson
2021-01-27 15:42 ` Vinod Koul
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [this message]
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=161462878441.6187.7566254509554088332.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=thara.gopinath@linaro.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