From: Frank.Li@oss.nxp.com
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Frank Li <Frank.Li@nxp.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Kees Cook <kees+treewide@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Xu Rao <raoxu@uniontech.com>,
linux-media@vger.kernel.org (open list:MEDIA INPUT
INFRASTRUCTURE (V4L/DVB)),
linux-kernel@vger.kernel.org (open list)
Cc: imx@lists.linux.dev
Subject: [PATCH 1/1] media: m2m-deinterlace: use dmaengine_has_cap() instead of dma_has_cap()
Date: Wed, 11 Nov 2026 12:22:39 -0500 [thread overview]
Message-ID: <20261111172243.3440103-1-Frank.Li@oss.nxp.com> (raw)
From: Frank Li <Frank.Li@nxp.com>
Replace the open-coded dma_has_cap(DMA_INTERLEAVE,
pcdev->dma_chan->device->cap_mask) with the dmaengine_has_cap()
helper, which encapsulates the capability check and takes the
dma_chan pointer directly.
No functional change and prepare to move struct dma_device to private.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
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 df291b5f7501f..33f05d2baed6a 100644
--- a/drivers/media/platform/m2m-deinterlace.c
+++ b/drivers/media/platform/m2m-deinterlace.c
@@ -924,7 +924,7 @@ static int deinterlace_probe(struct platform_device *pdev)
if (!pcdev->dma_chan)
return -ENODEV;
- if (!dma_has_cap(DMA_INTERLEAVE, pcdev->dma_chan->device->cap_mask)) {
+ if (!dmaengine_has_cap(pcdev->dma_chan, DMA_INTERLEAVE)) {
dev_err(&pdev->dev, "DMA does not support INTERLEAVE\n");
ret = -ENODEV;
goto rel_dma;
--
2.43.0
reply other threads:[~2026-11-11 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261111172243.3440103-1-Frank.Li@oss.nxp.com \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=hverkuil+cisco@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kees+treewide@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®