From: Frank Li <Frank.li@oss.nxp.com>
To: Joshua Crofts <crofts@kernel.org>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/3] dmaengine: remove redundant pm_runtime_dont_use_autosuspend() calls
Date: Fri, 30 Oct 2026 11:01:02 -0500 [thread overview]
Message-ID: <auS_PrwhMwhc5BNk@SMW015318> (raw)
In-Reply-To: <20261030145901.1393-1-crofts@kernel.org>
On Fri, Oct 30, 2026 at 02:58:58PM +0000, Joshua Crofts wrote:
> [You don't often get email from crofts@kernel.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Since commit d1706f9da9f4 ("PM: runtime: call pm_runtime_dont_use_autosuspend() on reinit()"),
> driver core is now responsible for undoing any
> pm_runtime_use_autosuspend() calls on driver exit.
>
> Remove the redundant function calls.
>
> Joshua Crofts (3):
> dmaengine: at_xdmac: remove redundant
> pm_runtime_dont_use_autosuspend() calls
> dmaengine: qcom: remove redundant pm_runtime_dont_use_autosuspend()
> calls
> dmaengine: ti: remove redundant pm_runtime_dont_use_autosuspend()
> calls
Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> drivers/dma/at_xdmac.c | 2 --
> drivers/dma/qcom/bam_dma.c | 1 -
> drivers/dma/ti/cppi41.c | 5 +----
> 3 files changed, 1 insertion(+), 7 deletions(-)
>
>
> base-commit: d89e1d186ec9271bf78e62771779e9fc03bf0fc3
> --
> 2.47.3
>
prev parent reply other threads:[~2026-10-30 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 14:58 [PATCH 0/3] dmaengine: remove redundant pm_runtime_dont_use_autosuspend() calls Joshua Crofts
2026-10-30 14:58 ` [PATCH 1/3] dmaengine: at_xdmac: " Joshua Crofts
2026-10-30 14:59 ` [PATCH 2/3] dmaengine: qcom: " Joshua Crofts
2026-10-30 14:59 ` [PATCH 3/3] dmaengine: ti: " Joshua Crofts
2026-10-30 16:01 ` Frank Li [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=auS_PrwhMwhc5BNk@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=crofts@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=vkoul@kernel.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