All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: [PATCH 0/9] SKL/KBL watermark fixes, v3
Date: Thu, 22 Sep 2016 18:00:26 -0300	[thread overview]
Message-ID: <1474578035-424-1-git-send-email-paulo.r.zanoni@intel.com> (raw)

What's different from v2?
 - Added cc:stable tags for patches 1-7, as discussed with Jani.
 - Added r-b tags provided by Maarten (email on v1, IRC on v2).
 - Only patch 9 changed: fix a typo and add a MISSING_CASE().

Since every patch already has a R-B tag, if no one complains I'll just
push the series so we can move to the next watermarks patches that are
waiting.

Thanks for all the reviews and comments,
Paulo

Paulo Zanoni (9):
  drm/i915: SAGV is not SKL-only, so rename a few things
  drm/i915: introduce intel_has_sagv()
  drm/i915/kbl: KBL also needs to run the SAGV code
  drm/i915/gen9: fix the WaWmMemoryReadLatency implementation
  drm/i915/gen9: minimum scanlines for Y tile is not always 4
  drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations
  drm/i915/gen9: fix the watermark res_blocks value
  drm/i915/gen9: implement missing case for SKL watermarks calculation
  drm/i915/gen9: fail the modeset instead of WARNing on unsupported
    config

 drivers/gpu/drm/i915/i915_drv.h      |  10 +-
 drivers/gpu/drm/i915/intel_display.c |   9 +-
 drivers/gpu/drm/i915/intel_drv.h     |   6 +-
 drivers/gpu/drm/i915/intel_pm.c      | 187 ++++++++++++++++++++---------------
 4 files changed, 119 insertions(+), 93 deletions(-)

-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-09-22 21:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 21:00 Paulo Zanoni [this message]
2016-09-22 21:00 ` [PATCH 1/9] drm/i915: SAGV is not SKL-only, so rename a few things Paulo Zanoni
2016-09-22 21:00 ` [PATCH 2/9] drm/i915: introduce intel_has_sagv() Paulo Zanoni
2016-09-22 21:00   ` Paulo Zanoni
2016-09-22 21:00 ` [PATCH 3/9] drm/i915/kbl: KBL also needs to run the SAGV code Paulo Zanoni
2016-09-22 21:00   ` Paulo Zanoni
2016-09-22 21:00 ` [PATCH 4/9] drm/i915/gen9: fix the WaWmMemoryReadLatency implementation Paulo Zanoni
2016-09-22 21:00   ` Paulo Zanoni
2016-09-22 21:00 ` [PATCH 5/9] drm/i915/gen9: minimum scanlines for Y tile is not always 4 Paulo Zanoni
2016-09-27  7:06   ` [Intel-gfx] " Tvrtko Ursulin
2016-09-27  7:06     ` Tvrtko Ursulin
2016-09-22 21:00 ` [PATCH 6/9] drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations Paulo Zanoni
2016-09-22 21:00   ` Paulo Zanoni
2016-09-27  7:20   ` [Intel-gfx] " Tvrtko Ursulin
2016-09-22 21:00 ` [PATCH 7/9] drm/i915/gen9: fix the watermark res_blocks value Paulo Zanoni
2016-09-22 21:00 ` [PATCH 8/9] drm/i915/gen9: implement missing case for SKL watermarks calculation Paulo Zanoni
2016-09-22 21:00 ` [PATCH 9/9] drm/i915/gen9: fail the modeset instead of WARNing on unsupported config Paulo Zanoni
2016-09-22 21:49 ` ✗ Fi.CI.BAT: warning for SKL/KBL watermark fixes (rev3) Patchwork
2016-09-26 17:57   ` Paulo Zanoni

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=1474578035-424-1-git-send-email-paulo.r.zanoni@intel.com \
    --to=paulo.r.zanoni@intel.com \
    --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 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.