From: Golla Nagendra <nagendra.golla@amd.com>
To: <vkoul@kernel.org>, <Frank.Li@kernel.org>, <michal.simek@amd.com>,
<nagendra.golla@amd.com>, <abin.joseph@amd.com>,
<kees@kernel.org>, <ptsm@linux.microsoft.com>,
<sakari.ailus@linux.intel.com>, <radhey.shyam.pandey@amd.com>,
<u.kleine-koenig@pengutronix.de>
Cc: <git@amd.com>, <dmaengine@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] dmaengine: zynqmp_dma: fix race between runtime PM and device removal
Date: Tue, 30 Jun 2026 12:18:42 +0530 [thread overview]
Message-ID: <20260630064844.705173-1-nagendra.golla@amd.com> (raw)
This patch series addresses two issues in the zynqmp_dma_remove() function:
1. Fix the race condition between runtime PM and device removal where
pm_runtime_disable() was called after the power state check, leaving
a window for the runtime PM framework to change state unexpectedly.
2. Update the stale kernel doc comment that still references a return
value after the function was converted to return void.
Golla Nagendra (2):
dmaengine: zynqmp_dma: fix race between runtime PM and device removal
dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove()
drivers/dma/xilinx/zynqmp_dma.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--
2.49.1
next reply other threads:[~2026-06-30 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 6:48 Golla Nagendra [this message]
2026-06-30 6:48 ` [PATCH 1/2] dmaengine: zynqmp_dma: fix race between runtime PM and device removal Golla Nagendra
2026-06-30 7:21 ` Pandey, Radhey Shyam
2026-06-30 6:48 ` [PATCH 2/2] dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove() Golla Nagendra
2026-06-30 7:28 ` Pandey, Radhey Shyam
2026-07-02 16:03 ` [PATCH 0/2] dmaengine: zynqmp_dma: fix race between runtime PM and device removal Vinod Koul
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=20260630064844.705173-1-nagendra.golla@amd.com \
--to=nagendra.golla@amd.com \
--cc=Frank.Li@kernel.org \
--cc=abin.joseph@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=git@amd.com \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=ptsm@linux.microsoft.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=sakari.ailus@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.de \
--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