All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Mahesh Kumar <mahesh1.kumar@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Work around for underrun when enabling pipe scaler in GLK
Date: Wed, 24 May 2017 14:38:44 +0300	[thread overview]
Message-ID: <1495625924.4120.12.camel@gmail.com> (raw)
In-Reply-To: <e615587f-caa1-4541-65c7-912a7d1582ff@intel.com>

On Wed, 2017-05-24 at 13:57 +0530, Mahesh Kumar wrote:
> Hi,
> 
> 
> On Monday 08 May 2017 02:20 PM, Ander Conselvan de Oliveira wrote:
> > In Geminilake, a FIFO underrun happens the first time a pipe scaler is
> > enabled after boot/resume from suspend. Disabling DPF clock gating in
> > the respective CLKGATE_DIS_PSL register prior to enabling the scaler
> > works around the issue.
> 
> Is BSpec link or workaround number available for this?

This is not a documented workaround yet, still need input from hw engineers.

Ander


> 
> -Mahesh
> > Signed-off-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
> > ---
> >   drivers/gpu/drm/i915/i915_reg.h      |  8 ++++++++
> >   drivers/gpu/drm/i915/intel_display.c | 17 +++++++++++++++++
> >   2 files changed, 25 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index 524fdfd..3157c39 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -3424,6 +3424,14 @@ enum {
> >   #define   PWM2_GATING_DIS		(1 << 14)
> >   #define   PWM1_GATING_DIS		(1 << 13)
> >   
> > +#define _CLKGATE_DIS_PSL_A		0x46520
> > +#define _CLKGATE_DIS_PSL_B		0x46524
> > +#define _CLKGATE_DIS_PSL_C		0x46528
> > +#define   DPF_GATING_DIS		(1 << 10)
> > +
> > +#define CLKGATE_DIS_PSL(pipe) \
> > +	_MMIO_PIPE(pipe, _CLKGATE_DIS_PSL_A, _CLKGATE_DIS_PSL_B)
> > +
> >   /*
> >    * Display engine regs
> >    */
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 85b9e2f5..c24acdd 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -3176,6 +3176,7 @@ static void skl_detach_scaler(struct intel_crtc *intel_crtc, int id)
> >   static void skl_detach_scalers(struct intel_crtc *intel_crtc)
> >   {
> >   	struct intel_crtc_scaler_state *scaler_state;
> > +	struct drm_i915_private *dev_priv = to_i915(intel_crtc->base.dev);
> >   	int i;
> >   
> >   	scaler_state = &intel_crtc->config->scaler_state;
> > @@ -3185,6 +3186,14 @@ static void skl_detach_scalers(struct intel_crtc *intel_crtc)
> >   		if (!scaler_state->scalers[i].in_use)
> >   			skl_detach_scaler(intel_crtc, i);
> >   	}
> > +
> > +	if (IS_GEMINILAKE(dev_priv)) {
> > +		u32 tmp;
> > +
> > +		tmp = I915_READ(CLKGATE_DIS_PSL(intel_crtc->pipe));
> > +		tmp &= ~DPF_GATING_DIS;
> > +		I915_WRITE(CLKGATE_DIS_PSL(intel_crtc->pipe), tmp);
> > +	}
> >   }
> >   
> >   u32 skl_plane_stride(const struct drm_framebuffer *fb, int plane,
> > @@ -4763,6 +4772,14 @@ static void skylake_pfit_enable(struct intel_crtc *crtc)
> >   		if (WARN_ON(crtc->config->scaler_state.scaler_id < 0))
> >   			return;
> >   
> > +		if (IS_GEMINILAKE(dev_priv)) {
> > +			u32 tmp;
> > +
> > +			tmp = I915_READ(CLKGATE_DIS_PSL(crtc->pipe));
> > +			tmp |= DPF_GATING_DIS;
> > +			I915_WRITE(CLKGATE_DIS_PSL(crtc->pipe), tmp);
> > +		}
> > +
> >   		id = scaler_state->scaler_id;
> >   		I915_WRITE(SKL_PS_CTRL(pipe, id), PS_SCALER_EN |
> >   			PS_FILTER_MEDIUM | scaler_state->scalers[id].mode);
> 
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-05-24 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08  8:50 [PATCH] drm/i915: Work around for underrun when enabling pipe scaler in GLK Ander Conselvan de Oliveira
2017-05-08  9:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-24  8:27 ` [PATCH] " Mahesh Kumar
2017-05-24 11:38   ` Ander Conselvan De Oliveira [this message]
2017-05-25  7:59     ` Mahesh Kumar

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=1495625924.4120.12.camel@gmail.com \
    --to=conselvan2@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mahesh1.kumar@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.