public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Syrjala, Ville" <ville.syrjala@intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Peres, Martin" <martin.peres@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2] Return only active connectors for get_resources ioctl
Date: Thu, 29 Nov 2018 08:17:07 +0000	[thread overview]
Message-ID: <096813850b49b14d9aec891c893ca9953176326c.camel@intel.com> (raw)
In-Reply-To: <857864a4de32b1572b1718bb92d18f14fdec67e5.camel@intel.com>

On Thu, 2018-11-29 at 07:37 +0000, Lisovskiy, Stanislav wrote:
> On Wed, 2018-11-28 at 22:21 +0100, Daniel Vetter wrote:
> > 
> > > I tried to read the bug and I have no idea what's going on here.
> > > Userspace
> > > is supposed to shut off outputs that are disconnected, whether
> > > that's DP,
> > > DP MST or something else shouldn't matter. New connectors can
> > > come&go as
> > > they see fit. Also not really something special.
> > > 
> > > Why do we need to dynamically hide an output here? Note that this
> > > also
> > > affects normal DP ports, which I have no idea is actually what
> > > you
> > > want to
> > > do or not.
> 
> This bug is real and easily reproducible with recent drm-tip.
> Unplugging and then quickly plugging back periodically leaves both my
> external displays connected to the docking station blank, there are
> also many duplicate bugs for this, which I simply didn't track. This
> patch at least fixes that annoying thing. 
> The userspace seems to get confused when we are returning two
> different
> connector ids, one in disconnected state and another in connected
> state
> for the same output. This results in userspace believing that nothing
> had changed and drm_mode_setcrtc call is not required( I have done
> traces confirming that theory). 
> 
> This could be also fixed in userspace by checking connectors more
> carefully - that fix I've also implemented for Intel DDX and attached
> to the bug, however seems that this happens also for Wayland.
> 

In addition to what I said above, I checked your changes instead of
proposed(also with locking) - it doesn't help, the displays get blank
after unplug/plug.


> > 
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_dp_mst.c
> > b/drivers/gpu/drm/i915/intel_dp_mst.c
> > index 4de247ddf05f..e1b66396c83b 100644
> > --- a/drivers/gpu/drm/i915/intel_dp_mst.c
> > +++ b/drivers/gpu/drm/i915/intel_dp_mst.c
> > @@ -499,6 +499,8 @@ static void
> > intel_dp_register_mst_connector(struct drm_connector *connector)
> >  		drm_fb_helper_add_one_connector(&dev_priv->fbdev-
> > > helper,
> > 
> >  						connector);
> >  
> > +	list_move(&connector->head, &connector->dev-
> > > mode_config.connector_list);
> > 
> > +
> >  	drm_connector_register(connector);
> >  }
> >  
> 
> -- 
> Best Regards,
> 
> Lisovskiy Stanislav
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
-- 
Best Regards,

Lisovskiy Stanislav

  reply	other threads:[~2018-11-29 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 13:55 [PATCH v2] Return only active connectors for get_resources ioctl Stanislav Lisovskiy
2018-11-28 20:51 ` [Intel-gfx] " Daniel Vetter
2018-11-28 21:21   ` Daniel Vetter
2018-11-28 21:24     ` Daniel Vetter
2018-11-29  7:37     ` Lisovskiy, Stanislav
2018-11-29  8:17       ` Lisovskiy, Stanislav [this message]
2018-11-29  8:48       ` Daniel Vetter
2018-11-29  9:15         ` Lisovskiy, Stanislav

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=096813850b49b14d9aec891c893ca9953176326c.camel@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=martin.peres@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox