intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/skl: Correct other-pipe watermark update condition check
Date: Mon, 19 Oct 2015 16:00:18 +0300	[thread overview]
Message-ID: <20151019130018.GZ26517@intel.com> (raw)
In-Reply-To: <20151019092959.GQ13786@phenom.ffwll.local>

On Mon, Oct 19, 2015 at 11:29:59AM +0200, Daniel Vetter wrote:
> On Mon, Sep 21, 2015 at 11:32:44PM +0530, Kumar, Mahesh wrote:
> > If ddb allocation for planes in current CRTC is changed, that doesn't
> > lead to ddb allocation change for other CRTCs, because our DDB allocation
> > is not dynamic according to plane parameters, ddb is allocated according
> > to number of CRTC enabled, & divided equally among CTRC's.
> > 
> > In current condition check during Watermark calculation, if number of
> > plane/ddb allocation changes for current CRTC, Watermark for other pipes
> > are recalculated. But there is no change in DDB allocation of other pipe
> > so watermark is also not changed, This leads to warning messages.
> > WARN_ON(!wm_changed)
> > 
> > This patch corrects this and check if DDB allocation for pipes is changed,
> > then only recalculate watermarks.
> > 
> > Signed-off-by: Kumar, Mahesh <mahesh1.kumar@intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_pm.c | 12 +++++-------
> >  1 file changed, 5 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index 62de97e..a1ed920 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -3127,14 +3127,12 @@ static bool skl_ddb_allocation_changed(const struct skl_ddb_allocation *new_ddb,
> >  	struct drm_device *dev = intel_crtc->base.dev;
> >  	struct drm_i915_private *dev_priv = dev->dev_private;
> >  	const struct skl_ddb_allocation *cur_ddb = &dev_priv->wm.skl_hw.ddb;
> > -	enum pipe pipe = intel_crtc->pipe;
> > -
> > -	if (memcmp(new_ddb->plane[pipe], cur_ddb->plane[pipe],
> > -		   sizeof(new_ddb->plane[pipe])))
> > -		return true;
> >  
> > -	if (memcmp(&new_ddb->cursor[pipe], &cur_ddb->cursor[pipe],
> > -		    sizeof(new_ddb->cursor[pipe])))
> > +	/*
> > +	 * If ddb allocation of pipes chenged, it may require recalculation of
> > +	 * watermarks
> > +	 */
> > +	if (memcmp(new_ddb->pipe, cur_ddb->pipe, sizeof(new_ddb->pipe)))
> >  		return true;
> 
> I still have the cursor code here, this patch needs to be rebased.

I suppose you mean you have the other cursor code there, cause this one
has it too, just looking a bit different.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-19 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 18:02 [PATCH] drm/i915/skl: Correct other-pipe watermark update condition check Kumar, Mahesh
2015-10-16 16:45 ` Ville Syrjälä
2015-10-19  9:29 ` Daniel Vetter
2015-10-19 13:00   ` Ville Syrjälä [this message]
2015-10-19 13:22     ` Daniel Vetter
2015-10-23 16:41       ` [PATCH] drm/i915/skl: Correct other-pipe watermark update condition check (v2) Matt Roper
2015-10-27  6:16         ` Kumar, Mahesh
2015-11-17 14:16         ` Daniel Vetter
2016-02-22 16:42         ` Lyude

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=20151019130018.GZ26517@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).