From: mohit.dsor@oss.qualcomm.com
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, boss@oss.qualcomm.com,
qc-display-maintainer@oss.qualcomm.com
Subject: [PATCH 1/5] drm/bridge: lt9611c: fallback to cached HPD status on read failure
Date: Sun, 28 Jun 2026 02:13:53 +0530 [thread overview]
Message-ID: <20260627204357.3336040-2-mohit.dsor@oss.qualcomm.com> (raw)
In-Reply-To: <20260627204357.3336040-1-mohit.dsor@oss.qualcomm.com>
From: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
HPD status is retrieved via an MCU command. In some cases the
command may fail, for example when the MCU is not yet ready,
leading to incorrect disconnect reporting.
Instead of returning an error state, fall back to the last known
HPD status to provide a more stable detection result.
This avoids spurious disconnect events during initialization.
Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>
---
drivers/gpu/drm/bridge/lontium-lt9611c.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/bridge/lontium-lt9611c.c b/drivers/gpu/drm/bridge/lontium-lt9611c.c
index 5d67bb7391fb..81ca9d62eae3 100644
--- a/drivers/gpu/drm/bridge/lontium-lt9611c.c
+++ b/drivers/gpu/drm/bridge/lontium-lt9611c.c
@@ -711,10 +711,12 @@ lt9611c_bridge_detect(struct drm_bridge *bridge, struct drm_connector *connector
guard(mutex)(<9611c->ocm_lock);
ret = lt9611c_read_write_flow(lt9611c, cmd, ARRAY_SIZE(cmd), data, ARRAY_SIZE(data));
- if (ret)
+ if (ret) {
dev_err(dev, "failed to read HPD status (err=%d)\n", ret);
- else
+ connected = lt9611c->hdmi_connected;
+ } else {
connected = (data[4] == 0x02);
+ }
lt9611c->hdmi_connected = connected;
--
2.34.1
next prev parent reply other threads:[~2026-06-27 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 20:43 [PATCH 0/5] drm/bridge: lt9611c: improve HPD handling and driver robustness mohit.dsor
2026-06-27 20:43 ` mohit.dsor [this message]
2026-06-27 20:43 ` [PATCH 2/5] drm/bridge: lt9611c: implement hpd_enable callback mohit.dsor
2026-06-27 20:43 ` [PATCH 3/5] drm/bridge: lt9611c: fix DT parsing and bridge refcount mohit.dsor
2026-06-27 20:43 ` [PATCH 4/5] drm/bridge: lt9611c: fix chip type initialization mohit.dsor
2026-06-27 20:43 ` [PATCH 5/5] drm/bridge: lt9611c: clean up probe error and remove paths mohit.dsor
2026-06-27 21:04 [PATCH 0/5] Subject: [PATCH 0/5] drm/bridge: lt9611c: improve HPD handling and driver robustness Mohit Dsor
2026-06-27 21:04 ` [PATCH 1/5] drm/bridge: lt9611c: fallback to cached HPD status on read failure Mohit Dsor
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=20260627204357.3336040-2-mohit.dsor@oss.qualcomm.com \
--to=mohit.dsor@oss.qualcomm.com \
--cc=boss@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qc-display-maintainer@oss.qualcomm.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
all inboxes | Powered by JetHome®