public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/mediatek: Set dedicated DMA device and drop custom GEM callbacks
Date: Thu, 12 Mar 2026 07:08:42 +1000	[thread overview]
Message-ID: <review-patch3-20260311094929.3393338-4-wenst@chromium.org> (raw)
In-Reply-To: <20260311094929.3393338-4-wenst@chromium.org>

Patch Review

This is the big payoff patch, deleting 231 lines of custom GEM code (`mtk_gem.c` and `mtk_gem.h`). The key change is:

```c
-	for (i = 0; i < private->data->mmsys_dev_num; i++)
-		private->all_drm_private[i]->dma_dev = dma_dev;
+	drm_dev_set_dma_dev(drm, dma_dev);
```

The old code stored the DMA device in every `mtk_drm_private` instance. The new code calls the core API once on the DRM device. The driver ops are simplified to use the standard `DRM_GEM_DMA_DRIVER_OPS` macro, and the custom `mtk_gem_prime_import` / `mtk_gem_prime_import_sg_table` / `mtk_gem_dumb_create` are all dropped.

The commit message honestly documents the behavioral difference: the `VM_DONTDUMP` and `VM_IO` flags that were set by the custom `mtk_gem_object_mmap` will no longer be set by the standard `drm_gem_dma_mmap` helper. The reasoning that `VM_IO` doesn't make sense for `dma_alloc_attrs()` buffers is correct.

No issues. This is a clean simplification.

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-03-11 21:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  9:49 [PATCH v2 0/4] drm/gem-dma: Support dedicated DMA device for allocation Chen-Yu Tsai
2026-03-11  9:49 ` [PATCH v2 1/4] drm/prime: Limit scatter list size with dedicated DMA device Chen-Yu Tsai
2026-03-11 14:40   ` AngeloGioacchino Del Regno
2026-03-11 21:08   ` Claude review: " Claude Code Review Bot
2026-03-11  9:49 ` [PATCH v2 2/4] drm/gem-dma: Support dedicated DMA device for allocation and mapping Chen-Yu Tsai
2026-03-11 14:40   ` AngeloGioacchino Del Regno
2026-03-11 21:08   ` Claude review: " Claude Code Review Bot
2026-03-11  9:49 ` [PATCH v2 3/4] drm/mediatek: Set dedicated DMA device and drop custom GEM callbacks Chen-Yu Tsai
2026-03-11 14:40   ` AngeloGioacchino Del Regno
2026-03-11 21:08   ` Claude Code Review Bot [this message]
2026-03-11  9:49 ` [PATCH v2 4/4] drm/sun4i: Use backend/mixer as dedicated DMA device Chen-Yu Tsai
2026-03-11 21:08   ` Claude review: " Claude Code Review Bot
2026-03-11 21:08 ` Claude review: drm/gem-dma: Support dedicated DMA device for allocation Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-03-10  3:25 [PATCH RESEND 0/4] " Chen-Yu Tsai
2026-03-10  3:25 ` [PATCH RESEND 3/4] drm/mediatek: Set dedicated DMA device and drop custom GEM callbacks Chen-Yu Tsai
2026-03-11  3:45   ` Claude review: " Claude Code Review Bot
2026-03-10  3:20 [PATCH 0/4] drm/gem-dma: Support dedicated DMA device for allocation Chen-Yu Tsai
2026-03-10  3:20 ` [PATCH 3/4] drm/mediatek: Set dedicated DMA device and drop custom GEM callbacks Chen-Yu Tsai
2026-03-11  3:48   ` Claude review: " Claude Code Review Bot

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=review-patch3-20260311094929.3393338-4-wenst@chromium.org \
    --to=claude-review@example.com \
    --cc=dri-devel-reviews@example.com \
    /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