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: phy: qualcomm: add MSM8974 HDMI PHY support
Date: Wed, 25 Mar 2026 07:14:42 +1000	[thread overview]
Message-ID: <review-patch4-20260324-fd-hdmi-phy-v7-4-b41dde8d83b8@oss.qualcomm.com> (raw)
In-Reply-To: <20260324-fd-hdmi-phy-v7-4-b41dde8d83b8@oss.qualcomm.com>

Patch Review

Adds PLL rate calculation and configuration for the MSM8974 HDMI PHY, building on the preqmp framework from Patch 1 and the UniPHY registers from Patches 2-3.

**Bug: Pixel clock comparison values are in wrong units**

In `qcom_hdmi_msm8974_phy_pll_set_rate()`:
```c
	if (pixclk == 297000) {
		...
	} else if (pixclk == 268500) {
		...
```

`pixclk` is `hdmi_phy->hdmi_opts.tmds_char_rate` which is in Hz (`unsigned long long`). These comparisons against 297000 and 268500 will never be true — the values should be `297000000` (297 MHz) and `268500000` (268.5 MHz), or the code should use `HZ_PER_KHZ` multiplier:
```c
	if (pixclk == 297 * HZ_PER_MHZ) {
```

This also applies to the second comparison at line 7074:
```c
	if (pixclk == 268500)
```

**Minor: Duplicate helpers**

`write16()`, `write24()`, `read24()` are defined again here — same as noted in Patch 1. In this file they could share with the `phy-qcom-hdmi-28lpm.c` definitions via a common header.

**Minor: Unused `div` variable**

In `qcom_28lpm_set_rate()`:
```c
	unsigned int div;
	...
	dev_dbg(hdmi_phy->dev, "rate=%u, div = %d, vco = %lu", pixclk, div, vco_freq);
```

`div` is declared and used in the debug print but never assigned a value in this function. It will contain an indeterminate value.

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-03-24 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 22:56 [PATCH v7 0/4] drm/msm/hdmi & phy: use generic PHY framework 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-23 22:56 ` [PATCH v7 2/4] phy: qcom: apq8064-sata: extract UNI PLL register defines Dmitry Baryshkov
2026-03-24 21:14   ` Claude review: " Claude Code Review Bot
2026-03-23 22:56 ` [PATCH v7 3/4] phy: qcom-uniphy: add more registers from display PHYs Dmitry Baryshkov
2026-03-24 21:14   ` Claude review: " Claude Code Review Bot
2026-03-23 22:56 ` [PATCH v7 4/4] phy: qualcomm: add MSM8974 HDMI PHY support Dmitry Baryshkov
2026-03-24 21:14   ` Claude Code Review Bot [this message]
2026-03-24 21:14 ` 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-19  3:48 [PATCH v6 0/4] " Dmitry Baryshkov
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-14  5:06 [PATCH v5 0/4] drm/msm/hdmi & phy: use generic PHY framework Dmitry Baryshkov
2026-03-14  5:06 ` [PATCH v5 4/4] phy: qualcomm: add MSM8974 HDMI PHY support Dmitry Baryshkov
2026-03-16  2:08   ` 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-patch4-20260324-fd-hdmi-phy-v7-4-b41dde8d83b8@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