mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 0/5] drm/bridge: lt9611c: improve HPD handling and driver robustness
Date: Sun, 28 Jun 2026 02:11:15 +0530	[thread overview]
Message-ID: <20260627204125.3334834-1-mohit.dsor@oss.qualcomm.com> (raw)

From: Mohit Dsor <mohit.dsor@oss.qualcomm.com>

This series improves HPD handling and overall robustness of the
lt9611c bridge driver.

The HPD status read from the internal MCU may fail when the device
is not fully initialized, leading to spurious disconnect events.
This series mitigates such issues by falling back to a cached HPD
state and adds support for explicit HPD enable handling.

Additionally, it fixes DT parsing and bridge refcount handling,
corrects chip type initialization, and cleans up probe and remove
paths.

Tested on LT9611UXD platforms.

Signed-off-by: Mohit Dsor <mohit.dsor@oss.qualcomm.com>

Mohit Dsor (5):
  drm/bridge: lt9611c: fallback to cached HPD status on read failure
  drm/bridge: lt9611c: implement hpd_enable callback
  drm/bridge: lt9611c: fix DT parsing and bridge refcount
  drm/bridge: lt9611c: fix chip type initialization
  drm/bridge: lt9611c: clean up probe error and remove paths

 drivers/gpu/drm/bridge/lontium-lt9611c.c | 39 +++++++++++++++++++-----
 1 file changed, 32 insertions(+), 7 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-06-27 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 20:41 mohit.dsor [this message]
2026-06-27 20:41 ` [PATCH] drm: bridge: add support for lontium LT9611UXD bridge mohit.dsor
2026-06-30 16:57   ` Uwe Kleine-König
2026-06-27 20:43 [PATCH 0/5] drm/bridge: lt9611c: improve HPD handling and driver robustness 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=20260627204125.3334834-1-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®