From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/msm/a6xx: Limit GXPD votes to recovery in A8x
Date: Sun, 12 Apr 2026 13:46:56 +1000 [thread overview]
Message-ID: <review-patch6-20260407-gfx-clk-fixes-v1-6-4bb5583a5054@oss.qualcomm.com> (raw)
In-Reply-To: <20260407-gfx-clk-fixes-v1-6-4bb5583a5054@oss.qualcomm.com>
Patch Review
This is the most complex patch. The new helper functions cleanly separate the A6xx/A7xx and A8xx behaviors.
**Issue: Unchecked `pm_runtime_get_sync()` in `a6xx_gmu_gxpd_put()`.**
```c
if (adreno_gpu->funcs->gx_is_on(adreno_gpu)) {
pm_runtime_get_sync(gmu->gxpd); // return value unchecked
dev_pm_genpd_synced_poweroff(gmu->gxpd);
pm_runtime_put_sync(gmu->gxpd);
}
```
`pm_runtime_get_sync()` can fail (return negative). If it fails, the subsequent `synced_poweroff` + `put_sync` operate on a device with an incorrect refcount, potentially leaving GX in a bad state. At minimum, check the return value and log a warning, or propagate the error.
**Design observation:** The `a6xx_gmu_gxpd_put()` function returns `int` but the callers at the `a6xx_gmu_stop()` and `rpm_put:` error path in `a6xx_gmu_resume()` do not check the return value. For A6xx/A7xx, it returns the value from `pm_runtime_put_sync()`, which should be checked. For A8xx, it always returns 0 even if the internal `pm_runtime_get_sync()` failed. Consider making this void if return values aren't going to be checked, or actually check them at the call sites.
**Existing error path change:** In the `rpm_put:` label of `a6xx_gmu_resume()`:
```c
- pm_runtime_put(gmu->gxpd);
+ a6xx_gmu_gxpd_put(gmu);
```
The old code called `pm_runtime_put()` (async) on `gmu->gxpd` directly, without NULL checking (the NULL check was only on the get side). If `gmu->gxpd` is NULL/ERR, calling `pm_runtime_put()` on it would crash. The new `a6xx_gmu_gxpd_put()` adds the `IS_ERR_OR_NULL` check, which is actually an improvement for the non-A8xx case too.
**Blank line removed between function definitions:**
```c
+}
+
int a6xx_gmu_resume(struct a6xx_gpu *a6xx_gpu)
```
The diff shows the extra blank line between `gdsc_gx_do_nothing_enable` and `a6xx_gmu_resume` being consumed, which is fine -- one blank line between functions is correct style.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-12 3:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 9:30 [PATCH 0/6] qcom: Refactor GPU GX GDSC handling and IFPC behavior on A8x GPUs Taniya Das
2026-04-07 9:30 ` [PATCH 1/6] clk: qcom: gdsc: Add custom disable callback for GX GDSC Taniya Das
2026-04-07 10:56 ` Konrad Dybcio
2026-04-08 7:26 ` Taniya Das
2026-04-12 3:46 ` Claude review: " Claude Code Review Bot
2026-04-07 9:30 ` [PATCH 2/6] clk: qcom: gxclkctl: Use custom disable callback for gx_gdsc Taniya Das
2026-04-07 10:56 ` Konrad Dybcio
2026-04-12 3:46 ` Claude review: " Claude Code Review Bot
2026-04-07 9:30 ` [PATCH 3/6] clk: qcom: common: ensure runtime PM suspend completes on probe Taniya Das
2026-04-07 10:58 ` Konrad Dybcio
2026-04-08 7:26 ` Taniya Das
2026-04-12 3:46 ` Claude review: " Claude Code Review Bot
2026-04-07 9:30 ` [PATCH 4/6] clk: qcom: gxclkctl: Remove GX/GMxC rail votes to align with IFPC Taniya Das
2026-04-07 11:29 ` Konrad Dybcio
2026-04-08 7:25 ` Taniya Das
2026-04-12 3:46 ` Claude review: " Claude Code Review Bot
2026-04-07 9:30 ` [PATCH 5/6] drm/msm/a8xx: Make a8xx_recover IFPC safe Taniya Das
2026-04-07 11:00 ` Konrad Dybcio
2026-04-12 3:46 ` Claude review: " Claude Code Review Bot
2026-04-07 9:30 ` [PATCH 6/6] drm/msm/a6xx: Limit GXPD votes to recovery in A8x Taniya Das
2026-04-07 11:01 ` Konrad Dybcio
2026-04-07 19:16 ` Akhil P Oommen
2026-04-12 3:46 ` Claude Code Review Bot [this message]
2026-04-12 3:46 ` Claude review: qcom: Refactor GPU GX GDSC handling and IFPC behavior on A8x GPUs 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-patch6-20260407-gfx-clk-fixes-v1-6-4bb5583a5054@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