All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>,
	"jadahl@gmail.com" <jadahl@gmail.com>,
	"Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH] Revert "drm/i915: Fix DP-MST crtc_mask"
Date: Wed, 4 Sep 2019 17:02:46 +0300	[thread overview]
Message-ID: <20190904140246.GB7482@intel.com> (raw)
In-Reply-To: <8947f85cce38cdcb3b185af1e187e9e7252c3d82.camel@intel.com>

On Tue, Sep 03, 2019 at 08:10:18PM +0000, Souza, Jose wrote:
> On Tue, 2019-09-03 at 18:40 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > This reverts commit 4eaceea3a00f8e936a7f48dcd0c975a57f88930f.
> > 
> > Several userspace clients (modesetting ddx and mutter+wayland at
> > least)
> > handle encoder.possible_crtcs incorrectly. What they essentially do
> > is
> > the following:
> > 
> > possible_crtcs = ~0;
> > for_each_possible_encoder(connector)
> > 	possible_crtcs &= encoder->possible_crtcs;
> > 
> > Ie. they calculate the intersection of the possible_crtcs
> > for the connector when they really should be calculating the
> > union instead.
> > 
> > In our case each MST encoder now has just one unique bit set,
> > and so the intersection is always zero. The end result is that
> > MST connectors can't be lit up because no crtc can be found to
> > drive them.
> > 
> > I've submitted a fix for the modesetting ddx [1], and complained
> > on #wayland about mutter, so hopefully the situation will improve
> > in the future. In the meantime we have regression, and so must go
> > back to the old way of misconfiguring possible_crtcs in the kernel.
> 
> In the meantime are you planing to send a patch doing:
> 
> for_each_pipe(dev_priv, pipe)
> 		intel_encoder->crtc_mask |= BIT(pipe);
> 
> We had a patch doing that in one of the TGL enabling series but it was
> dropped because of your patch looked better, I can bring it back if you
> are not planning.

Yeah, please resend your version.

> 
> > 
> > [1] https://gitlab.freedesktop.org/xorg/xserver/merge_requests/277
> 
> Just looked to the merge request above, not to the other userspace
> clients
> 
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>

Ta.

> 
> > 
> > Cc: Jonas Ådahl <jadahl@gmail.com>
> > Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> > Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111507
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_dp_mst.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > index 6df240a01b8c..37366f81255b 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > @@ -615,7 +615,7 @@ intel_dp_create_fake_mst_encoder(struct
> > intel_digital_port *intel_dig_port, enum
> >  	intel_encoder->type = INTEL_OUTPUT_DP_MST;
> >  	intel_encoder->power_domain = intel_dig_port-
> > >base.power_domain;
> >  	intel_encoder->port = intel_dig_port->base.port;
> > -	intel_encoder->crtc_mask = BIT(pipe);
> > +	intel_encoder->crtc_mask = 0x7;
> >  	intel_encoder->cloneable = 0;
> >  
> >  	intel_encoder->compute_config = intel_dp_mst_compute_config;

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-09-04 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 15:40 [PATCH] Revert "drm/i915: Fix DP-MST crtc_mask" Ville Syrjala
2019-09-03 17:04 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-09-03 20:10 ` [PATCH] " Souza, Jose
2019-09-04 14:02   ` Ville Syrjälä [this message]
2019-09-03 21:29 ` ✗ Fi.CI.IGT: failure for " Patchwork
2019-09-04 15:57   ` Ville Syrjälä

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=20190904140246.GB7482@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jadahl@gmail.com \
    --cc=jose.souza@intel.com \
    --cc=lucas.demarchi@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.