[PATCH] dmaengine: xilinx: zynqmp_dma: fix autosuspend cleanup during teardown
Guangshuo Li
lgs201920130244 at gmail.com
Wed Aug 26 01:14:54 PDT 2026
Hi Krzysztof,
On Thu, 20 Aug 2026 at 22:03, Krzysztof Kozlowski <krzk at kernel.org> wrote:
>
> On 08/08/2026 13:52, Guangshuo Li wrote:
> > zynqmp_dma_probe() calls pm_runtime_use_autosuspend(), but its failure
> > paths and zynqmp_dma_remove() do not call the matching
> > pm_runtime_dont_use_autosuspend().
> >
> > If the autosuspend delay is set to a negative value while autosuspend
> > is enabled, the runtime PM core increments usage_count to prevent
> > runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
> > during teardown, this reference is not dropped and usage_count remains
> > unbalanced.
> >
> > The documentation for pm_runtime_use_autosuspend() also notes that it
> > is important to undo it with pm_runtime_dont_use_autosuspend() at
> > driver exit time, unless runtime PM was initially enabled with
> > devm_pm_runtime_enable().
> >
> > Add the missing pm_runtime_dont_use_autosuspend() calls to the probe
> > failure and remove paths.
> >
> > This issue was found by manual code inspection.
> >
> > Fixes: 64c6f7da8c2c ("dmaengine: zynqmp_dma: Add runtime pm support")
> > Cc: stable at vger.kernel.org
> > Signed-off-by: Guangshuo Li <lgs201920130244 at gmail.com>
>
> You sent vast amount of patches, all separate, making it very difficult
> to track and respond in efficient way. Do not do that.
>
> Group your work per subsystem.
>
> You were asked to clarify and respond to incorrect fixes statement. I do
> not see how you clarified and responded at all.
>
> Best regards,
> Krzysztof
Sorry about that. I should have replied to the earlier review comments
explicitly, and I also should not have sent so many separate patches.
I will group future patches by subsystem and make sure to respond
clearly to review feedback before resending.
Thanks for pointing this out.
Best regards,
Guangshuo
More information about the linux-arm-kernel
mailing list