intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Guang Bai <guang.bai@intel.com>, Chris Chiu <chiu@endlessm.com>
Cc: intel-gfx@lists.freedesktop.org, linux@endlessm.com
Subject: Re: [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure (v2)
Date: Tue, 13 Nov 2018 13:07:46 +0200	[thread overview]
Message-ID: <87muqdgrr1.fsf@intel.com> (raw)
In-Reply-To: <20181112210737.4d4a38b7@gbai-ub1604-LTS>

On Mon, 12 Nov 2018, Guang Bai <guang.bai@intel.com> wrote:
> Actually I'm still working on it right now with
> DRM_MODE_CONNECTOR_HDMIA/HDMIB, recommended by James, I'm able to
> differentiate the HDMI or DP even the encoder type is the
> "INTEL_OUTPUT_DDI", I still have the "trybot" intermittent test failures
> with new DRM connector types. Even worse, there is phantom
> "intel_encoder_hotplug()" call following the correct one:
> When connecting both DP and HDMI on the platform, unplug the DP, the
> "i915_hotplug_work_func()" first calls the "intel_encoder_hotplug()"
> with DP encoder, then calls again with HDMI encoder.
> I haven't identified if the work function get queued twice or itself
> is incorrectly identifying wrong encoder hotplut status. Will try to
> get everything cleaned up ASAP.

Frankly I liked the simplicity of [1] over the patch in this thread. It
fixed the real-world use case Chris Chiu has, but I understand that it
still failed the slow unplug HDMI test case you have. The problem is, we
have zero visibility to the test case you have. Is it automated or
manual? Can we see the specs or source code for the test case?

If we have to consider the live status unreliable, it's possible to
devise a pathological test case that will always fail, regardless of
what we do in the driver. Does the test case reflect real world usage?

Also Cc: Ville for input.

BR,
Jani.



[1] http://patchwork.freedesktop.org/patch/msgid/20180925071836.24711-1-jani.nikula@intel.com


-- 
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-13 11:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03  5:12 [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure Guang Bai
2018-10-03  5:33 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-10-03  5:57 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-03  9:22 ` [PATCH] " Chris Chiu
2018-10-03 17:57   ` [PATCH] drm/i915: Fix the HDMI hot plug disconnection failure (v2) Guang Bai
2018-10-08 14:35     ` Chris Chiu
2018-10-08 15:56       ` Guang Bai
2018-10-10 17:52         ` Guang Bai
2018-10-23  9:14           ` Chris Chiu
2018-10-29 17:12             ` Guang Bai
2018-11-13  1:04               ` Chris Chiu
2018-11-13  5:07                 ` Guang Bai
2018-11-13 11:07                   ` Jani Nikula [this message]
2018-11-28 22:58                     ` Guang Bai
2018-11-20  3:11                   ` Chris Chiu
2018-10-03  9:34 ` ✗ Fi.CI.IGT: failure for drm/i915: Fix the HDMI hot plug disconnection failure Patchwork
2018-10-03  9:52   ` Martin Peres
2018-10-03 18:41 ` ✗ Fi.CI.BAT: failure for drm/i915: Fix the HDMI hot plug disconnection failure (rev2) 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=87muqdgrr1.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chiu@endlessm.com \
    --cc=guang.bai@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux@endlessm.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;
as well as URLs for NNTP newsgroup(s).