From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/mediatek: dsi: Store driver data before invoking mipi_dsi_host_register
Date: Fri, 27 Feb 2026 13:42:15 +1000 [thread overview]
Message-ID: <review-patch1-20260225094047.76780-1-l.scorcia@gmail.com> (raw)
In-Reply-To: <20260225094047.76780-1-l.scorcia@gmail.com>
Patch Review
**Correctness: Good**
The commit message clearly explains the bug with a full crash trace showing the call chain from `mipi_dsi_host_register` → `mtk_dsi_host_attach` → `component_add` → `mtk_dsi_bind` → `dev_get_drvdata` returning NULL. The fix moves `platform_set_drvdata(pdev, dsi)` before the `mipi_dsi_host_register()` call, which is the right thing to do.
**init_waitqueue_head move is also correct (v3 improvement):**
The `init_waitqueue_head(&dsi->irq_wait_queue)` is also moved earlier, before `platform_set_drvdata`. This is important because after `mipi_dsi_host_register` completes and `mtk_dsi_bind` runs successfully, the DSI subsystem could theoretically start operations that use the wait queue. More concretely, the IRQ handler `mtk_dsi_irq()` calls `wake_up_interruptible(&dsi->irq_wait_queue)` — so the wait queue must be initialized before `devm_request_irq()`, which is called right after `mipi_dsi_host_register()`. This was already the case in the original code (init was after request_irq — actually a latent bug!), and this patch fixes that ordering too.
**Minor observation — latent pre-existing bug also fixed:**
Looking at the original code in the drm-next tree:
```c
ret = devm_request_irq(&pdev->dev, irq_num, mtk_dsi_irq, ...); // line 1243
...
init_waitqueue_head(&dsi->irq_wait_queue); // line 1250
```
The original code initializes the wait queue *after* registering the IRQ handler that calls `wake_up_interruptible()` on it. This is a pre-existing race condition. This patch incidentally fixes it by moving `init_waitqueue_head` before both `mipi_dsi_host_register` and `devm_request_irq`. The commit message (v3 note) mentions this was intentional, which is good.
**No error-path concerns:** `platform_set_drvdata` and `init_waitqueue_head` don't need cleanup on failure, so moving them earlier doesn't create any resource leak issues on the error paths.
**Fixes tag:** Correctly references commit `e4732b590a77` which moved `mipi_dsi_host_register` earlier in the probe function without also moving `platform_set_drvdata` ahead of it.
**Verdict:** The patch is correct and well-motivated. No issues found.
Reviewed-by tags present: AngeloGioacchino Del Regno (Collabora) — appropriate reviewer for MediaTek DRM.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 9:38 [PATCH v3] drm/mediatek: dsi: Store driver data before invoking mipi_dsi_host_register Luca Leonardo Scorcia
2026-02-26 9:11 ` CK Hu (胡俊光)
2026-02-27 3:42 ` Claude Code Review Bot [this message]
2026-02-27 3:42 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-20 15:37 [PATCH v3 RESEND] " Luca Leonardo Scorcia
2026-03-21 17:36 ` Claude review: " Claude Code Review Bot
2026-03-21 17:36 ` Claude Code Review Bot
2026-02-23 14:16 [PATCH v2] " Luca Leonardo Scorcia
2026-02-24 0:09 ` Claude review: " Claude Code Review Bot
2026-02-24 0:09 ` 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-patch1-20260225094047.76780-1-l.scorcia@gmail.com \
--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