From: Chris Wilson <chris@chris-wilson.co.uk>
To: Guang Bai <guang.bai@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>, Chris Chiu <chiu@endlessm.com>
Subject: Re: [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure (v3)
Date: Wed, 28 Nov 2018 21:39:04 +0000 [thread overview]
Message-ID: <154344114433.11623.8778228183095492042@skylake-alporthouse-com> (raw)
In-Reply-To: <1543439893-27350-1-git-send-email-guang.bai@intel.com>
Quoting Guang Bai (2018-11-28 21:18:13)
> On some GEN9 platforms, slowly unplugging (wiggling) the HDMI cable makes
> the kernel to believe the HDMI display is still connected. This is because
> the HDMI DDC lines are disconnected a little bit later after the hot-plug
> interrupt triggered thus an immediate edid fetch can be made. Use digital
> port live states to authorize the edid read.
You should at least comment upon why we don't historically do this and
why you now believe that it is safe.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-28 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 21:18 [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure (v3) Guang Bai
2018-11-28 21:39 ` Chris Wilson [this message]
2018-11-29 1:37 ` [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure (v4) Guang Bai
2018-11-29 8:17 ` Jani Nikula
2018-11-29 17:01 ` Guang Bai
2018-12-03 10:38 ` Chris Chiu
2019-01-02 9:29 ` Chris Chiu
2019-01-02 17:34 ` Guang Bai
2019-01-04 4:02 ` Chris Chiu
2019-01-04 15:47 ` Guang Bai
2018-11-29 8:27 ` Chris Chiu
2018-11-28 22:56 ` ✓ Fi.CI.BAT: success for drm/i915: Fix the HDMI hot plug disconnection failure (rev3) Patchwork
2018-11-29 2:50 ` ✓ Fi.CI.BAT: success for drm/i915: Fix the HDMI hot plug disconnection failure (rev4) Patchwork
2018-11-29 15:48 ` ✓ Fi.CI.IGT: " Patchwork
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=154344114433.11623.8778228183095492042@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=chiu@endlessm.com \
--cc=guang.bai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.