From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/msm/hdmi: switch to generic PHY subsystem
Date: Sun, 22 Mar 2026 04:56:09 +1000 [thread overview]
Message-ID: <review-patch1-20260319-fd-hdmi-phy-v6-1-cefc08a55470@oss.qualcomm.com> (raw)
In-Reply-To: <20260319-fd-hdmi-phy-v6-1-cefc08a55470@oss.qualcomm.com>
Patch Review
This is the core patch (~5500 lines of diff) that removes the old PHY code from `drivers/gpu/drm/msm/hdmi/` and creates new standalone PHY drivers under `drivers/phy/qualcomm/`.
**Critical: Missing compatible strings**
The old code in `hdmi_phy.c` handled these compatibles:
```
{ .compatible = "qcom,hdmi-phy-8084", .data = &msm_hdmi_phy_8x74_cfg },
{ .compatible = "qcom,hdmi-phy-8998", .data = &msm_hdmi_phy_8998_cfg },
```
The new `phy-qcom-hdmi-28hpm.c` only has:
```c
static const struct of_device_id qcom_hdmi_phy_28hpm_of_match[] = {
{ .compatible = "qcom,hdmi-phy-8974", .data = &msm8974_hdmi_phy_cfg },
{ },
};
```
And the new `phy-qcom-qmp-hdmi-msm8998.c` only has MSM8996 in its match table (if any). The `qcom,hdmi-phy-8084` compatible (which shared the 8x74 PHY config) and `qcom,hdmi-phy-8998` are dropped, breaking those platforms.
**Use `device_get_match_data()` instead of `of_device_get_match_data()`**
In `phy-qcom-hdmi-preqmp.c`:
```c
const struct qcom_hdmi_preqmp_cfg *cfg = of_device_get_match_data(dev);
```
And in `phy-qcom-qmp-hdmi-base.c`:
```c
const struct qmp_hdmi_phy_cfg *cfg = of_device_get_match_data(dev);
```
The kernel community prefers `device_get_match_data()` which works for both OF and ACPI matching, and avoids the `__iomem` casting warnings that `of_device_get_match_data()` can produce.
**Typo in Kconfig help text**
```
config PHY_QCOM_HDMI
...
help
Enable this to support HDMI PHY presend on pre-QMP Qualcomm platforms
```
"presend" should be "present".
**Typo in MODULE_DESCRIPTION**
In `phy-qcom-hdmi-preqmp.c`:
```c
MODULE_DESCRIPTION("Qualcomm MSMpreqmp HDMI PHY driver");
```
Should have a space: "Qualcomm MSM pre-QMP HDMI PHY driver" or similar.
**Duplicated helper functions**
`write16()`, `write24()`, and `read24()` are defined identically in both `phy-qcom-hdmi-28lpm.c` and `phy-qcom-hdmi-28hpm.c`. These could be placed in the shared `phy-qcom-hdmi-preqmp.h` header or a common source file to avoid duplication.
**`pm_runtime_get_sync` vs `pm_runtime_resume_and_get`**
In `phy-qcom-hdmi-preqmp.c`:
```c
ret = pm_runtime_get_sync(dev);
if (ret < 0) {
pm_runtime_put_sync(dev);
return ret;
}
```
`pm_runtime_resume_and_get()` is the preferred pattern — it handles the error path automatically, avoiding the need for the manual `pm_runtime_put_sync()` on failure.
**Bridge code conversion looks correct**
The `hdmi_bridge.c` changes properly sequence the generic PHY calls:
```c
phy_init(hdmi->phy);
phy_configure(hdmi->phy, &opts);
phy_power_on(hdmi->phy);
...
phy_power_off(hdmi->phy);
phy_exit(hdmi->phy);
```
This correctly maps to the old `hdmi->phy->funcs->powerup()` / `powerdown()` flow.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-21 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 3:48 [PATCH v6 0/4] drm/msm/hdmi & phy: use generic PHY framework Dmitry Baryshkov
2026-03-19 3:48 ` [PATCH v6 1/4] drm/msm/hdmi: switch to generic PHY subsystem Dmitry Baryshkov
2026-03-21 18:56 ` Claude Code Review Bot [this message]
2026-03-19 3:48 ` [PATCH v6 2/4] phy: qcom: apq8064-sata: extract UNI PLL register defines Dmitry Baryshkov
2026-03-21 18:56 ` Claude review: " Claude Code Review Bot
2026-03-19 3:48 ` [PATCH v6 3/4] phy: qcom-uniphy: add more registers from display PHYs Dmitry Baryshkov
2026-03-21 18:56 ` Claude review: " Claude Code Review Bot
2026-03-19 3:48 ` [PATCH v6 4/4] phy: qualcomm: add MSM8974 HDMI PHY support Dmitry Baryshkov
2026-03-21 18:56 ` Claude review: " Claude Code Review Bot
2026-03-21 18:56 ` Claude review: drm/msm/hdmi & phy: use generic PHY framework Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-23 22:56 [PATCH v7 0/4] " Dmitry Baryshkov
2026-03-23 22:56 ` [PATCH v7 1/4] drm/msm/hdmi: switch to generic PHY subsystem Dmitry Baryshkov
2026-03-24 21:14 ` Claude review: " Claude Code Review Bot
2026-03-14 5:06 [PATCH v5 0/4] drm/msm/hdmi & phy: use generic PHY framework Dmitry Baryshkov
2026-03-14 5:06 ` [PATCH v5 1/4] drm/msm/hdmi: switch to generic PHY subsystem Dmitry Baryshkov
2026-03-16 2:07 ` 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-patch1-20260319-fd-hdmi-phy-v6-1-cefc08a55470@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