From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [PATCH 13/24] drm/i915: handle DDI-related assertions Date: Mon, 30 Apr 2012 17:07:32 -0700 Message-ID: <20120430170732.6f212527@jbarnes-desktop> References: <1335464479-648-1-git-send-email-eugeni.dodonov@intel.com> <1335464479-648-14-git-send-email-eugeni.dodonov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by gabe.freedesktop.org (Postfix) with SMTP id D00AF9EB4E for ; Mon, 30 Apr 2012 17:07:34 -0700 (PDT) In-Reply-To: <1335464479-648-14-git-send-email-eugeni.dodonov@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Eugeni Dodonov Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Thu, 26 Apr 2012 15:21:08 -0300 Eugeni Dodonov wrote: > Prevent bogus asserts on DDI-related paths. > > Signed-off-by: Eugeni Dodonov > --- > drivers/gpu/drm/i915/intel_display.c | 35 ++++++++++++++++++++++++---------- > 1 file changed, 25 insertions(+), 10 deletions(-) > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c > index ca0edbf..b2d3dc1 100644 > --- a/drivers/gpu/drm/i915/intel_display.c > +++ b/drivers/gpu/drm/i915/intel_display.c > @@ -954,9 +954,16 @@ static void assert_fdi_tx(struct drm_i915_private *dev_priv, > u32 val; > bool cur_state; > > - reg = FDI_TX_CTL(pipe); > - val = I915_READ(reg); > - cur_state = !!(val & FDI_TX_ENABLE); > + if (IS_HASWELL(dev_priv->dev)) { > + /* On Haswell, DDI is used instead of FDI_TX_CTL */ > + reg = DDI_FUNC_CTL(pipe); > + val = I915_READ(reg); > + cur_state = !!(val & PIPE_DDI_FUNC_ENABLE); > + } else { > + reg = FDI_TX_CTL(pipe); > + val = I915_READ(reg); > + cur_state = !!(val & FDI_TX_ENABLE); > + } > WARN(cur_state != state, > "FDI TX state assertion failure (expected %s, current %s)\n", > state_string(state), state_string(cur_state)); > @@ -991,6 +998,10 @@ static void assert_fdi_tx_pll_enabled(struct drm_i915_private *dev_priv, > if (dev_priv->info->gen == 5) > return; > > + /* On Haswell, DDI ports are responsible for the FDI PLL setup */ > + if (IS_HASWELL(dev_priv->dev)) > + return; > + > reg = FDI_TX_CTL(pipe); > val = I915_READ(reg); > WARN(!(val & FDI_TX_PLL_ENABLE), "FDI TX PLL assertion failure, should be active but is disabled\n"); > @@ -2515,14 +2526,18 @@ static void ironlake_fdi_pll_enable(struct drm_crtc *crtc) > POSTING_READ(reg); > udelay(200); > > - /* Enable CPU FDI TX PLL, always on for Ironlake */ > - reg = FDI_TX_CTL(pipe); > - temp = I915_READ(reg); > - if ((temp & FDI_TX_PLL_ENABLE) == 0) { > - I915_WRITE(reg, temp | FDI_TX_PLL_ENABLE); > + /* On Haswell, the PLL configuration for ports and pipes is handled > + * separately, as part of DDI setup */ > + if (!IS_HASWELL(dev)) { > + /* Enable CPU FDI TX PLL, always on for Ironlake */ > + reg = FDI_TX_CTL(pipe); > + temp = I915_READ(reg); > + if ((temp & FDI_TX_PLL_ENABLE) == 0) { > + I915_WRITE(reg, temp | FDI_TX_PLL_ENABLE); > > - POSTING_READ(reg); > - udelay(100); > + POSTING_READ(reg); > + udelay(100); > + } > } > } > Maybe some small helper functions instead? Or possibly separate high level enable/disable functions... -- Jesse Barnes, Intel Open Source Technology Center