DMA Engine development
 help / color / mirror / Atom feed
From: Rosen Penev <rosenp@gmail.com>
To: dmaengine@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
	Xuelin Shi <xuelin.shi@freescale.com>,
	Harninder Rai <harninder.rai@freescale.com>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCHv2 0/2] dmaengine: fsl_raid: fix resource leaks and simplify drvdata handling
Date: Tue, 21 Jul 2026 12:54:20 -0700	[thread overview]
Message-ID: <20260721195422.353794-1-rosenp@gmail.com> (raw)

This series fixes resource leaks in the FSL RAIDEngine driver and
simplifies drvdata handling:

1) Replace dev_get_drvdata/dev_set_drvdata with platform_get_drvdata/
   platform_set_drvdata, since a platform_device is always used. This
   avoids taking a pointer to a platform device member.

2) Add missing free_irq() in error unwind of fsl_re_chan_probe() and in
   fsl_re_remove_chan(). Also add tasklet_kill() and
   of_platform_device_destroy() to properly release all resources.

v2: split into two patches

Rosen Penev (2):
  dmaengine: fsl_raid: pass platform_device to drvdata
  dmaengine: fsl_raid: free resources in probe

 drivers/dma/fsl_raid.c | 33 ++++++++++++++++++++-------------
 drivers/dma/fsl_raid.h |  1 +
 2 files changed, 21 insertions(+), 13 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-07-21 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 19:54 Rosen Penev [this message]
2026-07-21 19:54 ` [PATCHv2 1/2] dmaengine: fsl_raid: pass platform_device to drvdata Rosen Penev
2026-07-21 21:38   ` Frank Li
2026-07-21 19:54 ` [PATCHv2 2/2] dmaengine: fsl_raid: free resources in probe Rosen Penev
2026-07-21 21:43   ` Frank Li
2026-07-21 21:53     ` Rosen Penev
2026-07-21 23:56       ` Frank Li

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=20260721195422.353794-1-rosenp@gmail.com \
    --to=rosenp@gmail.com \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=harninder.rai@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@kernel.org \
    --cc=xuelin.shi@freescale.com \
    /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