From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/bridge: pass down IRQ_HPD to the drivers
Date: Thu, 23 Apr 2026 09:07:43 +1000 [thread overview]
Message-ID: <review-patch2-20260421-hpd-irq-events-v3-2-44d2bf40dfc2@oss.qualcomm.com> (raw)
In-Reply-To: <20260421-hpd-irq-events-v3-2-44d2bf40dfc2@oss.qualcomm.com>
Patch Review
This is the largest patch -- a mechanical update of callback signatures across the bridge subsystem. All the changes are consistent:
- `hpd_notify` funcs pointer: gains `enum drm_connector_status_extra extra_status`
- `hpd_cb` function pointer: same
- `drm_bridge_hpd_enable()`: callback parameter updated
- `oob_hotplug_event` funcs pointer: same
- All bridge driver callbacks updated to accept but ignore the new parameter (correct -- non-DP bridges don't need it)
**Key correctness check** -- In `drm_bridge.c`, the existing `drm_bridge_hpd_notify()` passes `DRM_CONNECTOR_NO_EXTRA_STATUS` to the updated `hpd_cb`:
```c
bridge->hpd_cb(bridge->hpd_data, status, DRM_CONNECTOR_NO_EXTRA_STATUS);
```
This is correct for backward compatibility -- callers that don't know about IRQ_HPD continue to work.
In `drm_bridge_connector.c`, `drm_bridge_connector_detect()` correctly passes `DRM_CONNECTOR_NO_EXTRA_STATUS` since polling-based detection doesn't have IRQ events.
**Minor cosmetic issue:** In `ti-tfp410.c`, a blank line between `drm_bridge_to_tfp410()` and `drm_connector_to_tfp410()` is removed. This is unrelated to the IRQ_HPD changes:
```c
-}
-
-static inline struct tfp410 *
+}
+static inline struct tfp410 *
```
Consider keeping the blank line to avoid unnecessary churn.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-22 23:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 23:33 [PATCH v3 0/6] drm: handle IRQ_HPD events correctly Dmitry Baryshkov
2026-04-20 23:33 ` [PATCH v3 1/6] drm/connector: report IRQ_HPD events to drm_connector_oob_hotplug_event() Dmitry Baryshkov
2026-04-22 23:07 ` Claude review: " Claude Code Review Bot
2026-04-20 23:33 ` [PATCH v3 2/6] drm/bridge: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-04-22 23:07 ` Claude Code Review Bot [this message]
2026-04-20 23:33 ` [PATCH v3 3/6] drm/bridge: aux-hpd: let drivers pass IRQ_HPD events Dmitry Baryshkov
2026-04-22 23:07 ` Claude review: " Claude Code Review Bot
2026-04-20 23:33 ` [PATCH v3 4/6] drm/msm: dp: handle the IRQ_HPD events reported by USB-C Dmitry Baryshkov
2026-04-22 23:07 ` Claude review: " Claude Code Review Bot
2026-04-20 23:33 ` [PATCH v3 5/6] soc: qcom: pmic-glink-altmode: pass down HPD_IRQ events Dmitry Baryshkov
2026-04-21 9:51 ` Konrad Dybcio
2026-04-22 23:07 ` Claude review: " Claude Code Review Bot
2026-04-20 23:33 ` [PATCH v3 6/6] usb: typec: ucsi: huawei-gaokun: " Dmitry Baryshkov
2026-04-22 23:07 ` Claude review: " Claude Code Review Bot
2026-04-22 23:07 ` Claude review: drm: handle IRQ_HPD events correctly Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-20 15:31 [PATCH v2 0/6] " Dmitry Baryshkov
2026-04-20 15:31 ` [PATCH v2 2/6] drm/bridge: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-04-22 23:32 ` 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-patch2-20260421-hpd-irq-events-v3-2-44d2bf40dfc2@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