public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/6] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v3
Date: Tue, 27 May 2014 22:24:14 +0200	[thread overview]
Message-ID: <20140527202414.GO14841@phenom.ffwll.local> (raw)
In-Reply-To: <20140527193246.GO27580@intel.com>

On Tue, May 27, 2014 at 10:32:47PM +0300, Ville Syrjälä wrote:
> On Fri, May 23, 2014 at 01:16:40PM -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 boot or
> > 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.
> > 
> > Note that simply asserting reset at suspend and de-asserting at resume
> > is not sufficient, nor is simply de-asserting at boot.  Both of these
> > cases have been tested and have still been found to have failures on
> > some configurations.
> > 
> > v2: extract simpler set_power_well function for use in reset_dpio (Imre)
> >     move to reset_dpio (Daniel & Ville)
> > v3: don't reset if DPIO reset is already de-asserted (Imre)
> > 
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> 
> The series matches my understanding of the limitations of the PHY, so:
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

All merged to dinq, thanks.
 
> But if these limitations are real, then I think we would also need to
> adjust the power domains to power up all the wells whenever even a
> single one is required.
> 
> This should be testable I think by simply:
> 1. disable both ports
> 2. enable one port
> 3. enable the other port
> 
> At step 3. the common well is already up, so the TX wells for the second
> port should come up in some kind of poor state.

Hm, if we need this we might forc a modeset for _all_ pipes on vlv, even
for unchanged ports. At elast as long as we enable something new. That
should make this work properly I hope.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-05-27 20:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 20:16 [PATCH 1/6] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v3 Jesse Barnes
2014-05-23 20:16 ` [PATCH 2/6] drm/i915/vlv: drop power well enable in uncore_sanitize Jesse Barnes
2014-05-23 20:16 ` [PATCH 3/6] drm/i915/vlv: move CRI refclk enable into __vlv_set_power_well Jesse Barnes
2014-05-23 20:16 ` [PATCH 4/6] drm/i915/vlv: re-order power wells so DPIO common comes after TX Jesse Barnes
2014-05-27 20:21   ` Daniel Vetter
2014-05-23 20:16 ` [PATCH 5/6] drm/i915/vlv: move DPIO common reset de-assert into __vlv_set_power_well Jesse Barnes
2014-05-23 20:16 ` [PATCH 6/6] drm/i915/vlv: add pll assertion when disabling DPIO common well Jesse Barnes
2014-05-27 19:32 ` [PATCH 1/6] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v3 Ville Syrjälä
2014-05-27 20:24   ` Daniel Vetter [this message]
2014-05-28  8:00     ` 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=20140527202414.GO14841@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --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