Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: media-ci@linuxtv.org, imx@lists.linux.dev, Frank.Li@kernel.org
Subject: Re: [PATCH 1/1] media: m2m-deinterlace: replace direct ->device_prep*() calls with standard DMA engine API
Date: Thu, 17 Sep 2026 19:13:15 +0000	[thread overview]
Message-ID: <20260917191315.85AAA1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917190420.1189246-1-Frank.Li@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] media: m2m-deinterlace: unused variable dmadev
--

commit e18b2f587554971f1ebf19a1e3732c9502cf2d48
Author: Frank Li <Frank.Li@nxp.com>

media: m2m-deinterlace: replace direct ->device_prep*() calls with standard DMA engine API

This commit replaces direct invocations of the DMA engine channel's 
device_prep_*() function pointers with the standard dmaengine wrapper APIs.

> diff --git a/drivers/media/platform/m2m-deinterlace.c b/drivers/media/platform/m2m-deinterlace.c
> index 9dcc4bd6cbdd5..57a91ff2269f2 100644
> --- a/drivers/media/platform/m2m-deinterlace.c
> +++ b/drivers/media/platform/m2m-deinterlace.c
> @@ -330,7 +330,7 @@ static void deinterlace_issue_dma(struct deinterlace_ctx *ctx, int op,
>  	ctx->xt->dst_sgl = true;
>  	flags = DMA_CTRL_ACK | DMA_PREP_INTERRUPT;
>  
> -	tx = dmadev->device_prep_interleaved_dma(chan, ctx->xt, flags);
> +	tx = dmaengine_prep_interleaved_dma(chan, ctx->xt, flags);

[Severity: Low]
Does this change leave dmadev as an unused variable?

Looking at deinterlace_issue_dma(), dmadev is declared and initialized
earlier in the function:

    struct dma_device *dmadev = chan->device;

With this change replacing the direct device_prep_interleaved_dma() 
invocation, it appears dmadev is no longer referenced anywhere else in the 
function, which could result in a build warning.

>  	if (tx == NULL) {
>  		v4l2_warn(&pcdev->v4l2_dev, "DMA interleaved prep error\n");
>  		return;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917190420.1189246-1-Frank.Li@oss.nxp.com?part=1

  reply	other threads:[~2026-09-17 19:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 19:04 [PATCH 1/1] media: m2m-deinterlace: replace direct ->device_prep*() calls with standard DMA engine API Frank.Li
2026-09-17 19:13 ` sashiko-bot [this message]
2026-09-17 20:29 ` Laurent Pinchart
2026-09-17 20:33   ` Frank Li
2026-09-17 20:37     ` Laurent Pinchart
2026-09-17 21:19       ` 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=20260917191315.85AAA1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@oss.nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=media-ci@linuxtv.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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