public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/cnl: Force DDI_A_4_LANES when needed.
Date: Tue, 24 Oct 2017 10:25:03 -0700	[thread overview]
Message-ID: <20171024172503.fdbx4amvgyc46kfc@intel.com> (raw)
In-Reply-To: <20171024092138.GC10981@intel.com>

On Tue, Oct 24, 2017 at 09:21:38AM +0000, Ville Syrjälä wrote:
> On Mon, Oct 23, 2017 at 10:39:20AM -0700, Rodrigo Vivi wrote:
> > As we faced in BXT, on CNL DDI_A_4_LANES is not
> > set as expected when system is boot with multiple
> > monitors connected. This result in wrong lane
> > setup impacting the max data rate available and
> > consequently blocking modeset on eDP, resulting
> > in a blank screen.
> > 
> > Most of CNL SKUs don't support DDI-E.
> > The only SKU that supports DDI-E is the same
> > that supports the full A/E split called DDI-F.
> > 
> > Also when DDI-F is used DDI-E cannot be used because
> > they share Interrupts. So DDI-E is almost useless.
> > Anyways let's consider this is possible and rely on
> > VBT for that.
> > 
> > This patch was initialy start by Clint, but required
> > many changes including full commit message. So
> > Credits entirely to Clint for finding this.
> > 
> > v2: Extract all messy conditions into a helper function
> >     as suggested by Ville.
> >     Along with simplification I removed the debug
> >     message on the working case since now all conditions
> >     are grouped.
> > v3: Split the conditions even more as suggested by Ville.
> >     Get's cleaner and easier to add new cases in the
> >     future.
> > 
> > Suggested-by: Clint Taylor <clinton.a.taylor@intel.com>
> > Cc: Clint Taylor <clinton.a.taylor@intel.com>
> > Cc: Mika Kahola <mika.kahola@intel.com>
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> 
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks for review and all great suggestions.
Merged to dinq.

> 
> > ---
> >  drivers/gpu/drm/i915/intel_ddi.c | 46 ++++++++++++++++++++++++++++++----------
> >  1 file changed, 35 insertions(+), 11 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> > index adf51b328844..38a7088bd39c 100644
> > --- a/drivers/gpu/drm/i915/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/intel_ddi.c
> > @@ -2694,6 +2694,34 @@ intel_ddi_init_hdmi_connector(struct intel_digital_port *intel_dig_port)
> >  	return connector;
> >  }
> >  
> > +static bool intel_ddi_a_force_4_lanes(struct intel_digital_port *dport)
> > +{
> > +	struct drm_i915_private *dev_priv = to_i915(dport->base.base.dev);
> > +
> > +	if (dport->port != PORT_A)
> > +		return false;
> > +
> > +	if (dport->saved_port_bits & DDI_A_4_LANES)
> > +		return false;
> > +
> > +	/* Broxton/Geminilake: Bspec says that DDI_A_4_LANES is the only
> > +	 *                     supported configuration
> > +	 */
> > +	if (IS_GEN9_LP(dev_priv))
> > +		return true;
> > +
> > +	/* Cannonlake: Most of SKUs don't support DDI_E, and the only
> > +	 *             one who does also have a full A/E split called
> > +	 *             DDI_F what makes DDI_E useless. However for this
> > +	 *             case let's trust VBT info.
> > +	 */
> > +	if (IS_CANNONLAKE(dev_priv) &&
> > +	    !intel_bios_is_port_present(dev_priv, PORT_E))
> > +		return true;
> > +
> > +	return false;
> > +}
> > +
> >  void intel_ddi_init(struct drm_i915_private *dev_priv, enum port port)
> >  {
> >  	struct intel_digital_port *intel_dig_port;
> > @@ -2803,18 +2831,14 @@ void intel_ddi_init(struct drm_i915_private *dev_priv, enum port port)
> >  	}
> >  
> >  	/*
> > -	 * Bspec says that DDI_A_4_LANES is the only supported configuration
> > -	 * for Broxton.  Yet some BIOS fail to set this bit on port A if eDP
> > -	 * wasn't lit up at boot.  Force this bit on in our internal
> > -	 * configuration so that we use the proper lane count for our
> > -	 * calculations.
> > +	 * Some BIOS might fail to set this bit on port A if eDP
> > +	 * wasn't lit up at boot.  Force this bit set when needed
> > +	 * so we use the proper lane count for our calculations.
> >  	 */
> > -	if (IS_GEN9_LP(dev_priv) && port == PORT_A) {
> > -		if (!(intel_dig_port->saved_port_bits & DDI_A_4_LANES)) {
> > -			DRM_DEBUG_KMS("BXT BIOS forgot to set DDI_A_4_LANES for port A; fixing\n");
> > -			intel_dig_port->saved_port_bits |= DDI_A_4_LANES;
> > -			max_lanes = 4;
> > -		}
> > +	if (intel_ddi_a_force_4_lanes(intel_dig_port)) {
> > +		DRM_DEBUG_KMS("Forcing DDI_A_4_LANES for port A\n");
> > +		intel_dig_port->saved_port_bits |= DDI_A_4_LANES;
> > +		max_lanes = 4;
> >  	}
> >  
> >  	intel_dig_port->max_lanes = max_lanes;
> > -- 
> > 2.13.5
> 
> -- 
> Ville Syrjälä
> Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-24 17:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 23:11 [PATCH] drm/i915/cnl: Force DDI_A_4_LANES when needed Rodrigo Vivi
2017-10-20 23:30 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-21  0:52 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-23 13:11 ` [PATCH] " Ville Syrjälä
2017-10-23 17:12   ` Rodrigo Vivi
2017-10-23 17:26     ` Ville Syrjälä
2017-10-23 17:39       ` Rodrigo Vivi
2017-10-24  9:21         ` Ville Syrjälä
2017-10-24 17:25           ` Rodrigo Vivi [this message]
2017-10-23 17:31 ` ✓ Fi.CI.BAT: success for drm/i915/cnl: Force DDI_A_4_LANES when needed. (rev2) Patchwork
2017-10-23 17:59 ` ✓ Fi.CI.BAT: success for drm/i915/cnl: Force DDI_A_4_LANES when needed. (rev3) Patchwork
2017-10-23 18:20 ` ✓ Fi.CI.IGT: success for drm/i915/cnl: Force DDI_A_4_LANES when needed. (rev2) Patchwork
2017-10-23 19:06 ` ✓ Fi.CI.IGT: success for drm/i915/cnl: Force DDI_A_4_LANES when needed. (rev3) 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=20171024172503.fdbx4amvgyc46kfc@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=ville.syrjala@linux.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