From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Frank Li <Frank.Li@nxp.com>, Xu Rao <raoxu@uniontech.com>,
Kees Cook <kees@kernel.org>,
"open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)"
<linux-media@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev, vkoul@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 23:37:25 +0300 [thread overview]
Message-ID: <20260917203725.GB59058@killaraus.ideasonboard.com> (raw)
In-Reply-To: <aqxOtZdsNR03qmqN@SMW015318>
On Thu, Sep 17, 2026 at 03:33:57PM -0500, Frank Li wrote:
> On Thu, Sep 17, 2026 at 11:29:31PM +0300, Laurent Pinchart wrote:
> > On Thu, Sep 17, 2026 at 03:04:16PM -0400, Frank.Li@oss.nxp.com wrote:
> > > From: Frank Li <Frank.Li@nxp.com>
> > >
> > > DMA engine consumers must not call the channel's device_prep_*() function
> > > pointers directly. Use the standard dmaengine wrapper APIs instead.
> > >
> > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> >
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >
> > I've checked the other DMA operations, and there are a few direct
> > callers of .device_prep_dma_memcpy() and .device_prep_slave_sg(). The
> > former should be easy to address, as the dmaengine_prep_dma_memcpy()
> > wrapper is a drop-in replacement. The latter may be a bit more
> > complicated.
> >
> > Any volunteer to send patches ? :-)
>
> I already sent out and try to cleanup all.
Thank you. A patch for checkpatch.pl to warn about new callers may also
be interesting.
> > > ---
> > > drivers/media/platform/m2m-deinterlace.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > 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);
> > > if (tx == NULL) {
> > > v4l2_warn(&pcdev->v4l2_dev, "DMA interleaved prep error\n");
> > > return;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-09-17 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 19:04 Frank.Li
2026-09-17 20:29 ` Laurent Pinchart
2026-09-17 20:33 ` Frank Li
2026-09-17 20:37 ` Laurent Pinchart [this message]
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=20260917203725.GB59058@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.li@oss.nxp.com \
--cc=hverkuil+cisco@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=raoxu@uniontech.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
all inboxes | Powered by JetHome®