From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add two-stage ILK-style watermark programming (v10)
Date: Thu, 7 Jan 2016 12:29:12 +0100 [thread overview]
Message-ID: <568E4C08.3080600@linux.intel.com> (raw)
In-Reply-To: <1452108870-24204-1-git-send-email-matthew.d.roper@intel.com>
Op 06-01-16 om 20:34 schreef Matt Roper:
> In addition to calculating final watermarks, let's also pre-calculate a
> set of intermediate watermark values at atomic check time. These
> intermediate watermarks are a combination of the watermarks for the old
> state and the new state; they should satisfy the requirements of both
> states which means they can be programmed immediately when we commit the
> atomic state (without waiting for a vblank). Once the vblank does
> happen, we can then re-program watermarks to the more optimal final
> value.
>
> v2: Significant rebasing/rewriting.
>
> v3:
> - Move 'need_postvbl_update' flag to CRTC state (Daniel)
> - Don't forget to check intermediate watermark values for validity
> (Maarten)
> - Don't due async watermark optimization; just do it at the end of the
> atomic transaction, after waiting for vblanks. We do want it to be
> async eventually, but adding that now will cause more trouble for
> Maarten's in-progress work. (Maarten)
> - Don't allocate space in crtc_state for intermediate watermarks on
> platforms that don't need it (gen9+).
> - Move WaCxSRDisabledForSpriteScaling:ivb into intel_begin_crtc_commit
> now that ilk_update_wm is gone.
>
> v4:
> - Add a wm_mutex to cover updates to intel_crtc->active and the
> need_postvbl_update flag. Since we don't have async yet it isn't
> terribly important yet, but might as well add it now.
> - Change interface to program watermarks. Platforms will now expose
> .initial_watermarks() and .optimize_watermarks() functions to do
> watermark programming. These should lock wm_mutex, copy the
> appropriate state values into intel_crtc->active, and then call
> the internal program watermarks function.
>
> v5:
> - Skip intermediate watermark calculation/check during initial hardware
> readout since we don't trust the existing HW values (and don't have
> valid values of our own yet).
> - Don't try to call .optimize_watermarks() on platforms that don't have
> atomic watermarks yet. (Maarten)
>
> v6:
> - Rebase
>
> v7:
> - Further rebase
>
> v8:
> - A few minor indentation and line length fixes
>
> v9:
> - Yet another rebase since Maarten's patches reworked a bunch of the
> code (wm_pre, wm_post, etc.) that this was previously based on.
>
> v10:
> - Move wm_mutex to dev_priv to protect against racing commits against
> disjoint CRTC sets. (Maarten)
> - Drop unnecessary clearing of cstate->wm.need_postvbl_update (Maarten)
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>
Pushed, thanks.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-07 11:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 19:37 [PATCH 0/7] Wrap up ILK-style atomic watermarks (v2) Matt Roper
2015-12-03 19:37 ` [PATCH 1/7] drm/i915: Disable primary plane if we fail to reconstruct BIOS fb (v2) Matt Roper
2015-12-15 17:20 ` Matt Roper
2015-12-03 19:37 ` [PATCH 2/7] drm/i915: Extract plane dumping from intel_dump_pipe_config() Matt Roper
2015-12-03 19:37 ` [PATCH 3/7] drm/i915: Setup clipped src/dest coordinates during FB reconstruction (v2) Matt Roper
2015-12-03 19:37 ` [PATCH 4/7] drm/i915: Convert hsw_compute_linetime_wm to use in-flight state Matt Roper
2015-12-03 19:37 ` [PATCH 5/7] drm/i915: Add extra paranoia to ILK watermark calculations Matt Roper
2015-12-03 19:37 ` [PATCH 6/7] drm/i915: Sanitize watermarks after hardware state readout (v4) Matt Roper
2015-12-03 19:37 ` [PATCH 7/7] drm/i915: Add two-stage ILK-style watermark programming (v8) Matt Roper
2015-12-14 23:51 ` [PATCH 7/7] drm/i915: Add two-stage ILK-style watermark programming (v9) Matt Roper
2016-01-06 10:38 ` Maarten Lankhorst
2016-01-06 18:51 ` Matt Roper
2016-01-06 19:34 ` [PATCH] drm/i915: Add two-stage ILK-style watermark programming (v10) Matt Roper
2016-01-07 11:29 ` Maarten Lankhorst [this message]
2016-01-06 12:58 ` [PATCH 0/7] Wrap up ILK-style atomic watermarks (v2) Maarten Lankhorst
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=568E4C08.3080600@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--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 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.