intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 00/15] Atomic watermark updates (v5)
Date: Wed, 30 Sep 2015 22:21:38 +0000	[thread overview]
Message-ID: <1443651697.2212.55.camel@intel.com> (raw)
In-Reply-To: <20150930152004.GN3383@phenom.ffwll.local>

Em Qua, 2015-09-30 às 17:20 +0200, Daniel Vetter escreveu:
> On Thu, Sep 24, 2015 at 03:53:05PM -0700, Matt Roper wrote:
> > Previous version of the series was here:
> >   http://lists.freedesktop.org/archives/intel-gfx/2015-September/07
> > 5883.html
> > 
> > Pretty minimal changes since the last series:
> >  * General rebasing on di-nightly
> >  * Some minor SKL-specific bugfixes on patch #6 based on Maarten's
> > review of
> >    v4 of this series.
> >  * Added a new patch #14 to try to sanitize watermarks after
> > hardware state
> >    readout.  Once we've read general state out of the hardware, we
> > should
> >    recalculate what we think the watermarks for that state should
> > be and not
> >    just trust whatever the system firmware happens to have
> > programmed them to.
> >  * Added Maarten's r-b to all patches except the new #14; he gave
> > it on his
> >    feedback to patch #6 of the last revision of the series and I
> > didn't notice
> >    that it applied to the whole series until I re-read his
> > feedback.  :-)
> 
> Pulled in all into dinq, thanks!

And it's causing problems on my SKL machine. It gives me a new
DRM_ERROR about DDB state mismatch, and I'm getting FIFO underruns
sometimes (and due to the underruns, FBC works 0% of the times and
gives us nice black screens).

I tried bisecting the underruns but since they don't happen 100% of the
times I got lost very quickly. It *seems* that "drm/i915: Drop
intel_update_sprite_watermarks" is still a good commit, and the
intermittent problems (and DRM_ERROR) start after that, but I'm not
even 100% sure.

In case you want to try to reproduce the problem, my SKL machine has a
3200x1800 eDP panel.

I'm glad we don't have PRTS to catch these things :)

Thanks,
Paulo

> -Daniel
> 
> > 
> > Matt Roper (14):
> >   drm/i915: Drop redundant watermark programming
> >   drm/i915: Eliminate usage of plane_wm_parameters from ILK-style
> > WM
> >     code (v2)
> >   drm/i915: Eliminate usage of pipe_wm_parameters from ILK-style WM
> > (v2)
> >   drm/i915: Determine I915_MAX_PLANES from plane enum
> >   drm/i915/skl: Simplify wm structures slightly (v2)
> >   drm/i915/skl: Eliminate usage of pipe_wm_parameters from SKL
> > -style WM
> >     (v3)
> >   drm/i915/ivb: Move WaCxSRDisabledForSpriteScaling w/a to atomic
> > check
> >   drm/i915: Drop intel_update_sprite_watermarks
> >   drm/i915: Calculate pipe watermarks into CRTC state (v3)
> >   drm/i915: Calculate ILK-style watermarks during atomic check (v3)
> >   drm/i915: Don't set plane visible during HW readout if CRTC is
> > off
> >   drm/i915: Calculate watermark configuration during atomic check
> > (v2)
> >   drm/i915: Sanitize watermarks after hardware state readout
> >   drm/i915: Add two-stage ILK-style watermark programming (v5)
> > 
> > Ville Syrjälä (1):
> >   drm/i915: Refactor ilk_update_wm (v3)
> > 
> >  drivers/gpu/drm/i915/i915_debugfs.c  |   2 +-
> >  drivers/gpu/drm/i915/i915_drv.h      |  41 +-
> >  drivers/gpu/drm/i915/intel_atomic.c  |   2 +
> >  drivers/gpu/drm/i915/intel_display.c | 255 +++++++++--
> >  drivers/gpu/drm/i915/intel_drv.h     |  85 +++-
> >  drivers/gpu/drm/i915/intel_pm.c      | 855 ++++++++++++++++-------
> > ------------
> >  drivers/gpu/drm/i915/intel_sprite.c  |  15 -
> >  7 files changed, 707 insertions(+), 548 deletions(-)
> > 
> > -- 
> > 2.1.4
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-09-30 22:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 22:53 [PATCH 00/15] Atomic watermark updates (v5) Matt Roper
2015-09-24 22:53 ` [PATCH 01/15] drm/i915: Drop redundant watermark programming Matt Roper
2015-09-24 22:53 ` [PATCH 02/15] drm/i915: Eliminate usage of plane_wm_parameters from ILK-style WM code (v2) Matt Roper
2016-01-05 12:49   ` Flicker caused by "drm/i915: Eliminate usage of plane_wm_parameters from ILK-style WM code (v2)" Jan Niehusmann
2016-01-05 21:58     ` Matt Roper
2016-01-06  0:46       ` Jan Niehusmann
2015-09-24 22:53 ` [PATCH 03/15] drm/i915: Eliminate usage of pipe_wm_parameters from ILK-style WM (v2) Matt Roper
2015-09-24 22:53 ` [PATCH 04/15] drm/i915: Determine I915_MAX_PLANES from plane enum Matt Roper
2015-09-24 22:53 ` [PATCH 05/15] drm/i915/skl: Simplify wm structures slightly (v2) Matt Roper
2015-09-30 15:13   ` Daniel Vetter
2015-09-24 22:53 ` [PATCH 06/15] drm/i915/skl: Eliminate usage of pipe_wm_parameters from SKL-style WM (v3) Matt Roper
2015-09-24 22:53 ` [PATCH 07/15] drm/i915/ivb: Move WaCxSRDisabledForSpriteScaling w/a to atomic check Matt Roper
2015-09-24 22:53 ` [PATCH 08/15] drm/i915: Drop intel_update_sprite_watermarks Matt Roper
2015-09-24 22:53 ` [PATCH 09/15] drm/i915: Refactor ilk_update_wm (v3) Matt Roper
2015-09-24 22:53 ` [PATCH 10/15] drm/i915: Calculate pipe watermarks into CRTC state (v3) Matt Roper
2015-09-24 22:53 ` [PATCH 11/15] drm/i915: Calculate ILK-style watermarks during atomic check (v3) Matt Roper
2015-09-24 22:53 ` [PATCH 12/15] drm/i915: Don't set plane visible during HW readout if CRTC is off Matt Roper
2015-09-24 22:53 ` [PATCH 13/15] drm/i915: Calculate watermark configuration during atomic check (v2) Matt Roper
2015-09-24 22:53 ` [PATCH 14/15] drm/i915: Sanitize watermarks after hardware state readout Matt Roper
2015-10-01 13:58   ` Jani Nikula
2015-10-01 16:12     ` Daniel Vetter
2015-10-01 16:53     ` [PATCH] drm/i915: Convert hsw_compute_linetime_wm to use in-flight state Matt Roper
2015-10-06 14:34       ` Jani Nikula
2015-09-24 22:53 ` [PATCH 15/15] drm/i915: Add two-stage ILK-style watermark programming (v5) Matt Roper
2015-09-30 15:20 ` [PATCH 00/15] Atomic watermark updates (v5) Daniel Vetter
2015-09-30 22:21   ` Zanoni, Paulo R [this message]
2015-10-01 23:03     ` [PATCH] fixup! drm/i915/skl: Eliminate usage of pipe_wm_parameters from SKL-style WM (v3) Matt Roper
2015-10-02 18:43       ` Zanoni, Paulo R
2015-10-06 10:13         ` [PATCH] fixup! drm/i915/skl: Eliminate usage of pipe_wm_parameters from SKL-style WM (v3) [regression] Daniel Vetter

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=1443651697.2212.55.camel@intel.com \
    --to=paulo.r.zanoni@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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;
as well as URLs for NNTP newsgroup(s).