From: sashiko-bot@kernel.org
To: "Ian Ray" <ian.ray@gehealthcare.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v1 2/3] drm/bridge: dw-hdmi: optionally ignore rxsense when detecting hotplug
Date: Wed, 02 Sep 2026 13:16:12 +0000 [thread overview]
Message-ID: <20260902131612.74C321F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260902130117.2731-2-ian.ray@gehealthcare.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The `ignore_rxsense` flag is applied too late in the IRQ handler, breaking CEC physical address invalidation and PHY power-down on hotplug disconnect.
- [Low] The commit introduces a new device tree property `ignore-rxsense` without providing the corresponding YAML binding update.
--
commit daf606cf171e0645fecfea5f019e9fab9dd7eb6f
Author: Ian Ray <ian.ray@gehealthcare.com>
drm/bridge: dw-hdmi: optionally ignore rxsense when detecting hotplug
This commit introduces a new optional device tree property 'ignore-rxsense'
to bypass the rxsense state during hotplug detection. It is designed to
handle boards where rxsense is always active, such as when an HDMI to DP
converter is used.
> diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
> index 17d5caedb32e0..5e8f56fba8e96 100644
> --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
> +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
[ ... ]
> @@ -3156,6 +3157,9 @@ static irqreturn_t dw_hdmi_irq(int irq, void *dev_id)
> if (phy_stat & HDMI_PHY_HPD)
> status = connector_status_connected;
>
> + if (hdmi->ignore_rxsense)
> + phy_stat &= ~HDMI_PHY_RX_SENSE;
> +
[Severity: Medium]
Is this modification applied too late in the interrupt handler?
Earlier in dw_hdmi_irq(), the raw phy_stat is passed to
dw_hdmi_setup_rx_sense():
dw_hdmi_setup_rx_sense(hdmi,
phy_stat & HDMI_PHY_HPD,
phy_stat & HDMI_PHY_RX_SENSE);
When the cable is disconnected on a board where RX_SENSE is stuck high,
feeding the unmodified phy_stat into dw_hdmi_setup_rx_sense() prevents
it from clearing hdmi->rxsense, leaving the PHY incorrectly powered on.
Additionally, the raw phy_stat prevents the CEC invalidation block from
executing on disconnect:
if ((phy_stat & (HDMI_PHY_RX_SENSE | HDMI_PHY_HPD)) == 0) {
mutex_lock(&hdmi->cec_notifier_mutex);
cec_notifier_phys_addr_invalidate(hdmi->cec_notifier);
Could the mask be applied to phy_stat earlier in the function, before
it is used by the PHY power management and CEC invalidation logic?
> if (!(phy_stat & (HDMI_PHY_HPD | HDMI_PHY_RX_SENSE)))
> status = connector_status_disconnected;
> }
[ ... ]
> @@ -3362,6 +3366,8 @@ struct dw_hdmi *dw_hdmi_probe(struct platform_device *pdev,
> mutex_init(&hdmi->cec_notifier_mutex);
> spin_lock_init(&hdmi->audio_lock);
>
> + hdmi->ignore_rxsense = of_property_read_bool(np, "ignore-rxsense");
> +
[Severity: Low]
Is there a corresponding yaml binding update for this new property?
This introduces 'ignore-rxsense' as a new device tree property, but the
commit does not seem to include documentation for it. Missing
documentation makes it difficult for other board developers to know the
property exists and how to use it properly.
> ddc_node = of_parse_phandle(np, "ddc-i2c-bus", 0);
> if (ddc_node) {
> hdmi->ddc = of_get_i2c_adapter_by_node(ddc_node);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260902130117.2731-1-ian.ray@gehealthcare.com?part=2
next prev parent reply other threads:[~2026-09-02 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 13:01 [PATCH v1 1/3] dt-bindings: display: synopsys, dw-hdmi: add ignore-rxsense Ian Ray
2026-09-02 13:01 ` [PATCH v1 2/3] drm/bridge: dw-hdmi: optionally ignore rxsense when detecting hotplug Ian Ray
2026-09-02 13:16 ` sashiko-bot [this message]
2026-09-02 15:38 ` Jonas Karlman
2026-09-02 17:08 ` Ian Ray
2026-09-02 17:32 ` [PATCH v1 1/3] dt-bindings: display: synopsys,dw-hdmi: add ignore-rxsense Conor Dooley
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=20260902131612.74C321F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.ray@gehealthcare.com \
--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