From: Logan Gunthorpe <logang@deltatee.com>
To: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>
Cc: Frank Li <Frank.li@nxp.com>, Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH v3 0/6] plx_dma fixes
Date: Tue, 17 Nov 2026 10:51:29 -0600 [thread overview]
Message-ID: <20261117165135.746241-1-logang@deltatee.com> (raw)
This is v3 from my series last week. It uses the new plx_dma_free_desc()
helper in one more place and adds fixes tags through out.
Also, this series is not a high priority to me, I'm just trying to
fix Sashiko warnings. If there's spare review bandwidth I'd prefer
the time spent on my other series[1].
This series is based off of v7.4-rc3.
Thanks,
Logan
[v2] https://lore.kernel.org/all/20261110173927.624629-1-logang@deltatee.com/
[1] https://lore.kernel.org/all/20261110173137.623764-1-logang@deltatee.com/
--
Changes since v2:
* Add Fixes tags to the patches that lacked one (per Sashiko)
* Reuse plx_dma_free_desc() in the plx_dma_alloc_desc() error path
instead of open coding the same cleanup (per Sashiko)
* Rebased on v7.4-rc3
Changes since v1:
* Serialize descriptor completion with a new complete_lock so
callbacks stay in order and can't still be running after
plx_dma_free_chan_resources() returns (per Sashiko)
* Expand the commit message and comment for the dma_rmb() patch to
explain why the barrier is needed (per Frank)
* Collect Frank's Reviewed-by tags
* Rebased onto v7.4-rc2 (no conflicts)
Logan Gunthorpe (6):
dmaengine: plx_dma: don't call pci_irq_vector() under rcu_read_lock()
dmaengine: plx_dma: fix descriptor ring leak in alloc_chan_resources()
dmaengine: plx_dma: use writel() for the 32-bit PLX_REG_CTRL register
dmaengine: plx_dma: add dma_rmb() after observing write-back status
dmaengine: plx_dma: use spin_lock_bh() in plx_dma_process_desc()
dmaengine: plx_dma: don't invoke client callbacks with ring_lock held
drivers/dma/plx_dma.c | 98 +++++++++++++++++++++++++++++++------------
1 file changed, 71 insertions(+), 27 deletions(-)
base-commit: aebb7274476403040d582c61478df8f4a7bf9cd3
--
2.47.3
next reply other threads:[~2026-11-17 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 16:51 Logan Gunthorpe [this message]
2026-11-17 16:51 ` [PATCH v3 1/6] dmaengine: plx_dma: don't call pci_irq_vector() under rcu_read_lock() Logan Gunthorpe
2026-11-17 16:51 ` [PATCH v3 2/6] dmaengine: plx_dma: fix descriptor ring leak in alloc_chan_resources() Logan Gunthorpe
2026-11-17 16:51 ` [PATCH v3 3/6] dmaengine: plx_dma: use writel() for the 32-bit PLX_REG_CTRL register Logan Gunthorpe
2026-11-17 16:51 ` [PATCH v3 4/6] dmaengine: plx_dma: add dma_rmb() after observing write-back status Logan Gunthorpe
2026-11-17 16:51 ` [PATCH v3 5/6] dmaengine: plx_dma: use spin_lock_bh() in plx_dma_process_desc() Logan Gunthorpe
2026-11-17 16:51 ` [PATCH v3 6/6] dmaengine: plx_dma: don't invoke client callbacks with ring_lock held Logan Gunthorpe
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=20261117165135.746241-1-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=Frank.li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®