From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Frank.Li@oss.nxp.com
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Michal Simek <michal.simek@amd.com>,
"open list:XILINX VIDEO IP CORES" <linux-media@vger.kernel.org>,
"moderated list:ARM/ZYNQ ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev, vkoul@kernel.org,
Frank Li <Frank.Li@nxp.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH 1/1] media: xilinx: Use dmaengine_get_copy_align() accessor
Date: Thu, 12 Nov 2026 01:15:51 +0200 [thread overview]
Message-ID: <20261111231551.GB449775@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20261111171325.3424645-1-Frank.Li@oss.nxp.com>
On Wed, Nov 11, 2026 at 12:13:24PM -0500, Frank.Li@oss.nxp.com wrote:
> From: Frank Li <Frank.Li@nxp.com>
>
> Replace direct access to dma->dma->device->copy_align with the
> dmaengine_get_copy_align() accessor function.
>
> Prepare move struct dma_device to private.
I didn't see a rationale in the commit that introduced
dmaengine_get_copy_align(), and I then saw it here. Without knowing much
about the greater plan of making dma_device private, this patch looks
OK.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Tomi, will you handle this with any other ongoing work on
media/platform/xilinx/, or should it get merged separately ?
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/media/platform/xilinx/xilinx-dma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/xilinx/xilinx-dma.c b/drivers/media/platform/xilinx/xilinx-dma.c
> index ece2116639fc0..e01bb40bc39c7 100644
> --- a/drivers/media/platform/xilinx/xilinx-dma.c
> +++ b/drivers/media/platform/xilinx/xilinx-dma.c
> @@ -710,7 +710,7 @@ int xvip_dma_init(struct xvip_composite_device *xdev, struct xvip_dma *dma,
> goto error;
> }
>
> - dma->align = 1 << dma->dma->device->copy_align;
> + dma->align = 1 << dmaengine_get_copy_align(dma->dma);
>
> ret = video_register_device(&dma->video, VFL_TYPE_VIDEO, -1);
> if (ret < 0) {
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-11-11 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 17:13 Frank.Li
2026-11-11 23:15 ` Laurent Pinchart [this message]
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=20261111231551.GB449775@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michal.simek@amd.com \
--cc=tomi.valkeinen@ideasonboard.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®