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/msm/disp/dpu: consider SSPP line width during mode valid
Date: Tue, 31 Mar 2026 17:55:49 +1000	[thread overview]
Message-ID: <review-overall-20260328-msm-next-v1-1-12ac4e27c670@oss.qualcomm.com> (raw)
In-Reply-To: <20260328-msm-next-v1-1-12ac4e27c670@oss.qualcomm.com>

Overall Series Review

Subject: drm/msm/disp/dpu: consider SSPP line width during mode valid
Author: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Patches: 6
Reviewed: 2026-03-31T17:55:49.647743

---

This is a single patch that adds SSPP (Source Surface Pixel Processor) line width as an additional constraint during mode validation in the DPU CRTC. The intent is correct — several Qualcomm targets (sm6150, sm6125, sm6115, qcm2290, sm6375) have `max_linewidth` smaller than `max_mixer_width` (e.g., sm6150: max_linewidth=2160, max_mixer_width=2560), meaning modes could pass `dpu_crtc_mode_valid()` but fail later in `atomic_check`.

The code change itself is clean and straightforward. However, there is a gap in the fix.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-03-31  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-28 17:15 [PATCH] drm/msm/disp/dpu: consider SSPP line width during mode valid Vishnu Saini
2026-03-29  0:24 ` Dmitry Baryshkov
2026-03-30 18:30   ` Vishnu Saini
2026-03-30 18:39     ` Dmitry Baryshkov
2026-03-30 18:57       ` Vishnu Saini
2026-03-30 19:38         ` Dmitry Baryshkov
2026-03-31  7:55 ` Claude review: " Claude Code Review Bot
2026-03-31  7:55 ` Claude Code Review Bot [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=review-overall-20260328-msm-next-v1-1-12ac4e27c670@oss.qualcomm.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