From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amd/display: Wire up dcn10_dio_construct() for all pre-DCN401 generations
Date: Wed, 25 Mar 2026 07:19:08 +1000 [thread overview]
Message-ID: <review-overall-20260323211343.263909-1-sunlightlinux@gmail.com> (raw)
In-Reply-To: <20260323211343.263909-1-sunlightlinux@gmail.com>
Overall Series Review
Subject: drm/amd/display: Wire up dcn10_dio_construct() for all pre-DCN401 generations
Author: "Ionut Nechita (Sunlight Linux)" <sunlightlinux@gmail.com>
Patches: 3
Reviewed: 2026-03-25T07:19:08.008201
---
This single patch addresses a real regression introduced by commit `b82f0759346617b2` ("drm/amd/display: Migrate DIO registers access from hwseq to dio component"), which created the `dio` abstraction but only wired it up for DCN 4.01. On all older generations, `pool->dio` remains NULL, causing the `DIO_MEM_PWR_CTRL` register write to be silently skipped. This can result in AFMT HDMI memory not being powered on during `init_hw`, leading to HDMI audio failures.
**The fix is conceptually correct** — each DCN generation needs to construct and register a `dio` object. The approach follows the existing DCN 4.01 pattern.
**However, there are several issues:**
1. **DCN21 has a serious bug** — the shift/mask structs are zero-initialized instead of being properly populated, rendering `REG_UPDATE` a no-op.
2. **Extreme code duplication** — ~30 identical lines copied across 17 files. A shared helper would be far better.
3. **The patch should be a series** — 17 modified files in a single patch is hard to review and bisect.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-24 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 21:13 [PATCH] drm/amd/display: Wire up dcn10_dio_construct() for all pre-DCN401 generations Ionut Nechita (Sunlight Linux)
2026-03-24 14:37 ` Alex Deucher
2026-03-24 16:42 ` LIPSKI, IVAN
2026-03-24 21:19 ` Claude Code Review Bot [this message]
2026-03-24 21:19 ` 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-overall-20260323211343.263909-1-sunlightlinux@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