From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: i2c: qcom-geni: Avoid extra TX DMA TRE for single read message in GPI mode
Date: Sun, 12 Apr 2026 09:50:25 +1000 [thread overview]
Message-ID: <review-overall-20260410101949.2315058-1-aniket.randive@oss.qualcomm.com> (raw)
In-Reply-To: <20260410101949.2315058-1-aniket.randive@oss.qualcomm.com>
Overall Series Review
Subject: i2c: qcom-geni: Avoid extra TX DMA TRE for single read message in GPI mode
Author: Aniket Randive <aniket.randive@oss.qualcomm.com>
Patches: 3
Reviewed: 2026-04-12T09:50:25.095463
---
This is a single-patch series (v4) fixing a real bug in the Qualcomm GENI I2C GPI DMA path. The problem is that when `geni_i2c_gpi_xfer()` handles a read message, it always calls `geni_i2c_gpi()` with `op=I2C_WRITE` first (for the CONFIG+GO TREs on the TX channel), but on the first message (i=0), `peripheral.multi_msg` is initialized to `false`. This causes the GPI DMA driver (`gpi_create_i2c_tre()`) to generate a DMA data TRE alongside the CONFIG+GO TREs, resulting in a spurious write on the I2C bus before the intended read.
The fix is conceptually correct: it sets `multi_msg = true` before `dmaengine_slave_config()` copies the peripheral config, which tells the GPI DMA driver to suppress the DMA data TRE and emit only CONFIG+GO. However, the implementation has some fragility and readability issues worth addressing.
**Verdict:** The fix addresses a real bug but the approach could be cleaner. A few items need attention before merging.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-11 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 10:19 [PATCH V4] i2c: qcom-geni: Avoid extra TX DMA TRE for single read message in GPI mode Aniket Randive
2026-04-10 11:22 ` Mukesh Kumar Savaliya
2026-04-10 21:01 ` Andi Shyti
2026-04-11 23:50 ` Claude Code Review Bot [this message]
2026-04-11 23:50 ` 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-20260410101949.2315058-1-aniket.randive@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