public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/vlv: assert and de-assert sideband reset on resume
Date: Fri, 11 Apr 2014 21:10:21 +0300	[thread overview]
Message-ID: <20140411181021.GI18465@intel.com> (raw)
In-Reply-To: <20140411103540.55c01292@jbarnes-desktop>

On Fri, Apr 11, 2014 at 10:35:40AM -0700, Jesse Barnes wrote:
> On Fri, 11 Apr 2014 20:26:24 +0300
> Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> 
> > On Fri, Apr 11, 2014 at 10:00:16AM -0700, Jesse Barnes wrote:
> > > This is a bit like the CMN reset de-assert we do in DPIO_CTL, except
> > > that it resets the whole common lane section of the PHY.  This is
> > > required on machines where the BIOS doesn't do this for us on resume to
> > > properly re-calibrate and get the PHY ready to transmit data.
> > > 
> > > Without this patch, such machines won't resume correctly much of the time,
> > > with the symptom being a 'port ready' timeout and/or a link training
> > > failure.
> > > 
> > > I'm open to better suggestions on how to do the power well toggle, with
> > > the existing code it looks like I'd have to walk through a bunch of
> > > power domains looking for a match, then call a generic function which
> > > will warn.  I'd prefer to just expose the specific domains directly for
> > > low level platform code like this.
> > > 
> > > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > > ---
> > >  drivers/gpu/drm/i915/intel_pm.c     |    4 ++--
> > >  drivers/gpu/drm/i915/intel_uncore.c |   19 +++++++++++++++++++
> > >  2 files changed, 21 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > > index fa00185..3afd0bc 100644
> > > --- a/drivers/gpu/drm/i915/intel_pm.c
> > > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > > @@ -5454,8 +5454,8 @@ static bool i9xx_always_on_power_well_enabled(struct drm_i915_private *dev_priv,
> > >  	return true;
> > >  }
> > >  
> > > -static void vlv_set_power_well(struct drm_i915_private *dev_priv,
> > > -			       struct i915_power_well *power_well, bool enable)
> > > +void vlv_set_power_well(struct drm_i915_private *dev_priv,
> > > +			struct i915_power_well *power_well, bool enable)
> > >  {
> > >  	enum punit_power_well power_well_id = power_well->data;
> > >  	u32 mask;
> > > diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> > > index 2a72bab..f1abd2d 100644
> > > --- a/drivers/gpu/drm/i915/intel_uncore.c
> > > +++ b/drivers/gpu/drm/i915/intel_uncore.c
> > > @@ -363,6 +363,9 @@ static void intel_uncore_forcewake_reset(struct drm_device *dev, bool restore)
> > >  	spin_unlock_irqrestore(&dev_priv->uncore.lock, irqflags);
> > >  }
> > >  
> > > +void vlv_set_power_well(struct drm_i915_private *dev_priv,
> > > +			struct i915_power_well *power_well, bool enable);
> > > +
> > >  void intel_uncore_early_sanitize(struct drm_device *dev)
> > >  {
> > >  	struct drm_i915_private *dev_priv = dev->dev_private;
> > > @@ -381,6 +384,22 @@ void intel_uncore_early_sanitize(struct drm_device *dev)
> > >  		DRM_INFO("Found %zuMB of eLLC\n", dev_priv->ellc_size);
> > >  	}
> > >  
> > > +	/*
> > > +	 * From VLV2A0_DP_eDP_HDMI_DPIO_driver_vbios_notes_11.docx:
> > > +	 * Need to assert and de-assert PHY SB reset by gating the common
> > > +	 * lane power, then un-gating it.
> > > +	 * Simply ungating isn't enough to reset the PHY enough to get
> > > +	 * ports and lanes running.
> > > +	 */
> > > +	if (IS_VALLEYVIEW(dev)) {
> > > +		struct i915_power_well cmn_well = {
> > > +			.data = PUNIT_POWER_WELL_DPIO_CMN_BC
> > > +		};
> > > +
> > > +		vlv_set_power_well(dev_priv, &cmn_well, false);
> > > +		vlv_set_power_well(dev_priv, &cmn_well, true);
> > > +	}
> > 
> > Stick this into intel_reset_dpio() instead?
> > 
> > And what about fastboot and whatnot? Should we check if the display is
> > already up and running somehow before we go and kill it with this?
> 
> reset_dpio is too late.

How come? We shouldn't touch the PHY before it. So either reset_dpio is
in the wrong place for some reason, or something else gets called too
soon.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-04-11 18:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11 17:00 [PATCH] drm/i915/vlv: assert and de-assert sideband reset on resume Jesse Barnes
2014-04-11 17:16 ` Daniel Vetter
2014-04-11 17:34   ` Jesse Barnes
2014-04-11 18:06     ` Ville Syrjälä
2014-04-11 18:18       ` Jesse Barnes
2014-04-11 17:23 ` Imre Deak
2014-04-11 17:26 ` Ville Syrjälä
2014-04-11 17:35   ` Jesse Barnes
2014-04-11 18:10     ` Ville Syrjälä [this message]
2014-04-11 18:15       ` Jesse Barnes
2014-04-15 11:39         ` Purushothaman, Vijay A
2014-04-15 13:01           ` Ville Syrjälä
2014-04-15 13:04           ` Imre Deak

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=20140411181021.GI18465@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox