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: Qualcomm Sahara protocol enhancements.
Date: Sun, 22 Mar 2026 04:44:33 +1000	[thread overview]
Message-ID: <review-overall-20260319-sahara_protocol_new_v2-v4-0-47ad79308762@oss.qualcomm.com> (raw)
In-Reply-To: <20260319-sahara_protocol_new_v2-v4-0-47ad79308762@oss.qualcomm.com>

Overall Series Review

Subject: Qualcomm Sahara protocol enhancements.
Author: Kishore Batta <kishore.batta@oss.qualcomm.com>
Patches: 10
Reviewed: 2026-03-22T04:44:33.268433

---

This 9-patch series moves the Qualcomm Sahara protocol driver from the QAIC accelerator tree to `drivers/bus/mhi/sahara/`, generalizes device matching, adds QDU100 support, and introduces DDR training data capture via Sahara command mode with sysfs exposure.

**The architecture is sound** — making the Sahara driver a standalone MHI module is the right approach for reuse. However, the series has several significant bugs that need to be fixed before merging:

1. **Bug in `qaic_init()` error handling** (Patch 2) — goto labels are swapped, leading to unregistering drivers that were never registered.
2. **Unsigned comparison always-false** (Patch 7) — `le32_to_cpu()` returns `u32`, comparing `< 0` is a no-op.
3. **Sleeping in atomic context** (Patch 7) — `mutex_lock()` and `devres_alloc(GFP_KERNEL)` called from MHI DL callback which runs in tasklet context.
4. **Data races** (Patch 7) — `context->is_cmd_mode`, `receiving_trng_data`, etc. accessed from both DL callback and work queue without synchronization.
5. **Unbounded allocation from device-controlled size** (Patch 7) — `kzalloc(resp_len)` with no upper bound check.

The documentation patch (1/9) has numerous typos and copy-paste errors. The cover letter changelog for v4 still says "EDITME".

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-03-21 18:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  6:31 [PATCH v4 0/9] Qualcomm Sahara protocol enhancements Kishore Batta
2026-03-19  6:31 ` [PATCH v4 1/9] Add documentation for Sahara protocol Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 2/9] bus: mhi: Move sahara protocol driver under drivers/bus/mhi Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 3/9] bus: mhi: Match devices exposing the protocol on the SAHARA channel Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 4/9] bus: mhi: Centralize firmware image table selection at probe time Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 5/9] bus: mhi: Add QDU100 variant and image_id firmware fallback Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 6/9] bus: mhi: Load DDR training data using per-device serial number Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 7/9] bus: mhi: Capture DDR training data using command mode Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 8/9] bus: mhi: Expose DDR training data via controller sysfs Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-19  6:31 ` [PATCH v4 9/9] Documentation: ABI: Add sysfs ABI documentation for DDR training data Kishore Batta
2026-03-21 18:44   ` Claude review: " Claude Code Review Bot
2026-03-21 18:44 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-10  7:21 [PATCH v3 0/9] Qualcomm Sahara protocol enhancements Kishore Batta
2026-03-11  3:35 ` Claude review: " Claude Code Review Bot
2026-03-07 11:41 [PATCH v2 0/9] " Kishore Batta
2026-03-08 22: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-overall-20260319-sahara_protocol_new_v2-v4-0-47ad79308762@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