All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Guang Bai <guang.bai@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Chris Chiu <chiu@endlessm.com>
Subject: Re: [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure (v4)
Date: Thu, 29 Nov 2018 10:17:49 +0200	[thread overview]
Message-ID: <87a7ls9u1e.fsf@intel.com> (raw)
In-Reply-To: <1543455469-3303-1-git-send-email-guang.bai@intel.com>

On Wed, 28 Nov 2018, Guang Bai <guang.bai@intel.com> wrote:
> 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. This problem
> has been identified by more than one customer recently. Use digital
> port live states to authorize the edid read at HDMI detection point will
> ensure most of the display related software states updated and rest of them
> will be renewed accordingly when the port is connected.
>
> v2: Fix the formatting issue
> v3: Use digital port states to authorize the edid read
> v4: Add comments on issue histories and rationale of the fix (Chris W)

You're not answering Chris Wilson's question.

Why do you think the problems we've historically had with live status
are no longer a problem? We've tried and reverted live status checks at
least twice before because of regressions. Why do you think this time
there won't be regressions? Why do you think this patch makes forward
progress?

I've *repeatedly* said from the beginning that I am very sceptical of
using live status because we've been burned by it so many times
before. I don't much care to repeat this anymore.


BR,
Jani.


>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Chris Chiu <chiu@endlessm.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Guang Bai <guang.bai@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_hdmi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> index e2c6a2b..8cf7c78 100644
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1929,7 +1929,7 @@ intel_hdmi_detect(struct drm_connector *connector, bool force)
>  
>  	intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
>  
> -	if (IS_ICELAKE(dev_priv) &&
> +	if ((IS_ICELAKE(dev_priv) || IS_GEN9_BC(dev_priv)) &&
>  	    !intel_digital_port_connected(encoder))
>  		goto out;

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-11-29  8:17 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
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 [this message]
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=87a7ls9u1e.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chiu@endlessm.com \
    --cc=guang.bai@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.