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
