From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: misc: fastrpc: Add polling mode support
Date: Thu, 23 Apr 2026 07:50:44 +1000 [thread overview]
Message-ID: <review-overall-20260422092409.4107093-1-ekansh.gupta@oss.qualcomm.com> (raw)
In-Reply-To: <20260422092409.4107093-1-ekansh.gupta@oss.qualcomm.com>
Overall Series Review
Subject: misc: fastrpc: Add polling mode support
Author: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Patches: 8
Reviewed: 2026-04-23T07:50:44.016413
---
This is a v9 series adding DSP polling mode support to the FastRPC driver. The series is logically structured: patch 1 is a minor refactor, patch 2 converts to GENMASK/FIELD_GET, patch 3 expands the context ID mask, and patch 4 adds the polling mode feature itself.
**Key concerns:**
1. **Build-breaking bug in patch 4**: The function `of_machine_get_match()` does not exist in the kernel. The correct API is `of_machine_device_match()` (returns `bool`). This will cause a compilation failure.
2. **`readl_poll_timeout_atomic` on non-MMIO memory**: `readl()` is for memory-mapped I/O registers. The poll address is DMA coherent buffer memory (from `fastrpc_buf`). Using `readl()` on regular RAM is semantically wrong. A simple `READ_ONCE()` loop or `read_poll_timeout` with `READ_ONCE` would be more appropriate.
3. **Atomic busy-wait for 10ms**: `readl_poll_timeout_atomic` uses `udelay()`, holding the CPU in a tight busy loop for up to 10ms. This is a long time to disable preemption. The non-atomic `readl_poll_timeout` (which uses `usleep_range`) would be much better given this isn't an atomic context.
4. **Missing `__maybe_unused` justification**: The `fastrpc_poll_supported_machines` table is marked `__maybe_unused` which suppresses a warning when `CONFIG_OF` is disabled, but the driver already depends on OF via rpmsg/qcom infrastructure. This feels like papering over a warning rather than addressing it properly.
Overall the approach is reasonable but needs the compilation fix and the polling mechanism reviewed for correctness.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-22 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 9:24 [PATCH v9 0/4] misc: fastrpc: Add polling mode support Ekansh Gupta
2026-04-22 9:24 ` [PATCH v9 1/4] misc: fastrpc: Move fdlist to invoke context structure Ekansh Gupta
2026-04-22 15:48 ` Dmitry Baryshkov
2026-04-22 21:50 ` Claude review: " Claude Code Review Bot
2026-04-22 9:24 ` [PATCH v9 2/4] misc: fastrpc: Replace hardcoded ctxid mask with GENMASK Ekansh Gupta
2026-04-22 15:47 ` Dmitry Baryshkov
2026-04-22 21:50 ` Claude review: " Claude Code Review Bot
2026-04-22 9:24 ` [PATCH v9 3/4] misc: fastrpc: Expand context ID mask for DSP polling mode support Ekansh Gupta
2026-04-22 21:50 ` Claude review: " Claude Code Review Bot
2026-04-22 9:24 ` [PATCH v9 4/4] misc: fastrpc: Add polling mode support for fastRPC driver Ekansh Gupta
2026-04-22 15:47 ` Dmitry Baryshkov
2026-04-22 21:50 ` Claude review: " Claude Code Review Bot
2026-04-22 21:50 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-15 18:21 [PATCH v6 0/4] misc: fastrpc: Add polling mode support Ekansh Gupta
2026-02-15 20:40 ` 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-overall-20260422092409.4107093-1-ekansh.gupta@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