mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org,
	linux-amlogic@lists.infradead.org, neil.armstrong@linaro.org
Subject: Re: [PATCH v5 5/8] drm/bridge: pass down IRQ_HPD to the drivers
Date: Sun, 20 Sep 2026 15:10:45 +0000	[thread overview]
Message-ID: <20260920151045.D3BBC1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260920-hpd-irq-events-v5-5-ff1de0090c72@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/omapdrm: hdmi5_bridge_hpd_notify signature mismatch causes build failure
--

commit c12a9be57208a1450c89b7b186ca8f9ff6848995
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>

drm/bridge: pass down IRQ_HPD to the drivers

The DisplayPort standard defines a special kind of HPD events called
IRQ_HPD. These events are used to notify DP Source about the events on
the Sink side. Pass down the extra status to the bridge drivers via the
hpd_notify() callback, letting DP bridges to act accordingly.

> diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h
> index ed9f77a2597a1..2b3cad4bedde9 100644
> --- a/include/drm/drm_bridge.h
> +++ b/include/drm/drm_bridge.h
> @@ -509,7 +509,8 @@ struct drm_bridge_funcs {
>  	 */
>  	void (*hpd_notify)(struct drm_bridge *bridge,
>  			   struct drm_connector *connector,
> -			   enum drm_connector_status status);
> +			   enum drm_connector_status status,
> +			   enum drm_connector_dp_event event);
>  
>  	/**
>  	 * @hpd_enable:

[Severity: Low]
Could this cause a build regression by missing an update in
drivers/gpu/drm/omapdrm/dss/hdmi5.c?

While hdmi4_bridge_hpd_notify() was updated in this patch,
hdmi5_bridge_hpd_notify() in hdmi5.c still retains the old 3-argument
signature. Assigning this incorrectly-typed function pointer to
hdmi5_bridge_funcs.hpd_notify will result in an incompatible pointer type
compiler error when building with CONFIG_DRM_OMAP enabled:

drivers/gpu/drm/omapdrm/dss/hdmi5.c:
static void hdmi5_bridge_hpd_notify(struct drm_bridge *bridge,
                                    struct drm_connector *connector,
                                    enum drm_connector_status status)
{
...
static const struct drm_bridge_funcs hdmi5_bridge_funcs = {
...
        .hpd_notify = hdmi5_bridge_hpd_notify,
...
};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260920-hpd-irq-events-v5-0-ff1de0090c72@oss.qualcomm.com?part=5

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2026-09-20 15:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20 15:01 [PATCH v5 0/8] drm: handle IRQ_HPD events correctly Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 1/8] drm/connector: report out-of-band IRQ_HPD events Dmitry Baryshkov
2026-09-21  1:43   ` Chaoyi Chen
2026-09-20 15:01 ` [PATCH v5 2/8] drm/connector: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-09-21  1:53   ` Chaoyi Chen
2026-09-20 15:01 ` [PATCH v5 3/8] drm/bridge: aux-hpd: let drivers pass IRQ_HPD events Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 4/8] drm/bridge: pass extra events to the HPD callback Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 5/8] drm/bridge: pass down IRQ_HPD to the drivers Dmitry Baryshkov
2026-09-20 15:10   ` sashiko-bot [this message]
2026-09-20 15:01 ` [PATCH v5 6/8] drm/msm: dp: handle the IRQ_HPD events reported by USB-C Dmitry Baryshkov
2026-09-20 15:13   ` sashiko-bot
2026-09-20 15:01 ` [PATCH v5 7/8] soc: qcom: pmic-glink-altmode: pass down HPD_IRQ events Dmitry Baryshkov
2026-09-20 15:01 ` [PATCH v5 8/8] usb: typec: ucsi: huawei-gaokun: " Dmitry Baryshkov

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=20260920151045.D3BBC1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®