From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/msm/mdss: Add Shikra support
Date: Thu, 04 Jun 2026 11:45:50 +1000 [thread overview]
Message-ID: <review-patch2-20260603-shikra-display-v1-2-aeac1b94faa7@oss.qualcomm.com> (raw)
In-Reply-To: <20260603-shikra-display-v1-2-aeac1b94faa7@oss.qualcomm.com>
Patch Review
This patch adds one-line match table entries in two files.
**Sorting issue in `dpu_kms.c`**: The new entry is inserted between `qcom,sdm845-dpu` and `qcom,sc7180-dpu`:
```c
{ .compatible = "qcom,sdm845-dpu", .data = &dpu_sdm845_cfg, },
+ { .compatible = "qcom,shikra-dpu", .data = &dpu_qcm2290_cfg, },
{ .compatible = "qcom,sc7180-dpu", .data = &dpu_sc7180_cfg, },
```
The existing table is largely alphabetically sorted (confirmed by checking the tree — it runs `eliza`, `glymur`, `kaanapali`, `msm8917`, ... `qcm2290`, `sa8775p`, `sar2130p`, `sdm630`, `sdm660`, `sdm670`, `sdm845`, then anomalously `sc7180`, `sc7280`, `sc8180x`, ...). The `shikra` entry should go after the `sc8280xp-dpu` entry and before `sm6115-dpu` (since `"sc" < "sh" < "sm"` alphabetically). Currently it perpetuates the existing `sdm/sc` sort anomaly.
**Same issue in `msm_mdss.c`**: The entry goes between `sdm845-mdss` and `sc7180-mdss`, matching the same anomaly. The correct position would be between `sc8280xp-mdss` and `sm6115-mdss`.
**If fallback compatibles are adopted** (per Patch 1 feedback), neither of these driver changes would be needed.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 1:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 14:59 [PATCH 0/5] Subject: [PATCH 0/5] Add Shikra (QCM2290) display support Nabige Aala
2026-06-03 14:59 ` [PATCH 1/5] dt-bindings: display: msm: qcm2290: Add Shikra MDSS Nabige Aala
2026-06-03 23:08 ` Dmitry Baryshkov
2026-06-04 1:45 ` Claude review: " Claude Code Review Bot
2026-06-03 14:59 ` [PATCH 2/5] drm/msm/mdss: Add Shikra support Nabige Aala
2026-06-03 23:09 ` Dmitry Baryshkov
2026-06-04 1:45 ` Claude Code Review Bot [this message]
2026-06-03 14:59 ` [PATCH 3/5] arm64: defconfig: Enable ILI7807S DSI panel driver Nabige Aala
2026-06-03 23:09 ` Dmitry Baryshkov
2026-06-04 1:45 ` Claude review: " Claude Code Review Bot
2026-06-03 14:59 ` [PATCH 4/5] soc: qcom: ubwc: Add Shikra UBWC config Nabige Aala
2026-06-03 23:12 ` Dmitry Baryshkov
2026-06-04 1:45 ` Claude review: " Claude Code Review Bot
2026-06-03 14:59 ` [PATCH 5/5] iommu/arm-smmu: Add qcom,shikra-mdss to Qualcomm SMMU client tables Nabige Aala
2026-06-03 23:11 ` Dmitry Baryshkov
2026-06-04 1:45 ` Claude review: " Claude Code Review Bot
2026-06-04 1:45 ` Claude review: Subject: [PATCH 0/5] Add Shikra (QCM2290) display support 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-patch2-20260603-shikra-display-v1-2-aeac1b94faa7@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