From: "Maíra Canal" <mcanal@igalia.com>
To: Frank.Li@oss.nxp.com,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
"open list:DRM DRIVERS FOR TI OMAP"
<dri-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>
Cc: vkoul@kernel.org, imx@lists.linux.dev, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH 1/1] drm: use dmaengine API instead of raw function pointers
Date: Tue, 6 Oct 2026 15:47:39 -0300 [thread overview]
Message-ID: <0bb880c5-2f40-4d63-bc4c-0e4a1c5b4fa6@igalia.com> (raw)
In-Reply-To: <20261002200620.230735-1-Frank.Li@oss.nxp.com>
Hi Frank,
On 02/10/26 17:06, Frank.Li@oss.nxp.com wrote:
> From: Frank Li <Frank.Li@nxp.com>
>
> Replace direct calls through dma_async_tx_descriptor and
> dma_device function pointers with the proper dmaengine API
> wrappers in vc4_dsi and omap_dmm_tiler.
>
> Assisted-by: LLM
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
For VC4:
Reviewed-by: Maíra Canal <mcanal@igalia.com>
Best regards,
- Maíra
> ---
> drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 2 +-
> drivers/gpu/drm/vc4/vc4_dsi.c | 8 +++-----
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c b/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c
> index a2c702b831a7c..c5dd350f937f4 100644
> --- a/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c
> +++ b/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c
> @@ -87,7 +87,7 @@ static int dmm_dma_copy(struct dmm *dmm, dma_addr_t src, dma_addr_t dst)
> return -EIO;
> }
>
> - cookie = tx->tx_submit(tx);
> + cookie = dmaengine_submit(tx);
> if (dma_submit_error(cookie)) {
> dev_err(dmm->dev, "Failed to do DMA tx_submit\n");
> return -EIO;
> diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c
> index 0148f2befed14..b1626c2d3a582 100644
> --- a/drivers/gpu/drm/vc4/vc4_dsi.c
> +++ b/drivers/gpu/drm/vc4/vc4_dsi.c
> @@ -628,16 +628,14 @@ dsi_dma_workaround_write(struct vc4_dsi *dsi, u32 offset, u32 val)
>
> *dsi->reg_dma_mem = val;
>
> - tx = chan->device->device_prep_dma_memcpy(chan,
> - dsi->reg_paddr + offset,
> - dsi->reg_dma_paddr,
> - 4, 0);
> + tx = dmaengine_prep_dma_memcpy(chan, dsi->reg_paddr + offset,
> + dsi->reg_dma_paddr, 4, 0);
> if (!tx) {
> drm_err(drm, "Failed to set up DMA register write\n");
> return;
> }
>
> - cookie = tx->tx_submit(tx);
> + cookie = dmaengine_submit(tx);
> ret = dma_submit_error(cookie);
> if (ret) {
> drm_err(drm, "Failed to submit DMA: %d\n", ret);
prev parent reply other threads:[~2026-10-06 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 20:06 Frank.Li
2026-10-06 18:47 ` Maíra Canal [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=0bb880c5-2f40-4d63-bc4c-0e4a1c5b4fa6@igalia.com \
--to=mcanal@igalia.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=airlied@gmail.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=kernel-list@raspberrypi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--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®