All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/5] drm/i915: Use new atomic iterator macros in wm code
Date: Mon, 13 Mar 2017 11:07:53 +0100	[thread overview]
Message-ID: <20170313100753.ijnryf35xxvx7xgu@phenom.ffwll.local> (raw)
In-Reply-To: <1489071125-917-4-git-send-email-maarten.lankhorst@linux.intel.com>

On Thu, Mar 09, 2017 at 03:52:03PM +0100, Maarten Lankhorst wrote:
> The watermark code needs to look at the new allocations, so use
> for_each_new_crtc_in_state everywhere.
> 
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
>  drivers/gpu/drm/i915/intel_pm.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index 99e09f63d4b3..8670ef7707e7 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -4120,7 +4120,7 @@ pipes_modified(struct drm_atomic_state *state)
>  	struct drm_crtc_state *cstate;
>  	uint32_t i, ret = 0;
>  
> -	for_each_crtc_in_state(state, crtc, cstate, i)
> +	for_each_new_crtc_in_state(state, crtc, cstate, i)
>  		ret |= drm_crtc_mask(crtc);
>  
>  	return ret;
> @@ -4263,7 +4263,7 @@ skl_print_wm_changes(const struct drm_atomic_state *state)
>  	const struct skl_ddb_allocation *new_ddb = &intel_state->wm_results.ddb;
>  	int i;
>  
> -	for_each_crtc_in_state(state, crtc, cstate, i) {
> +	for_each_new_crtc_in_state(state, crtc, cstate, i) {
>  		const struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
>  		enum pipe pipe = intel_crtc->pipe;
>  
> @@ -4305,7 +4305,7 @@ skl_compute_wm(struct drm_atomic_state *state)
>  	 * since any racing commits that want to update them would need to
>  	 * hold _all_ CRTC state mutexes.
>  	 */
> -	for_each_crtc_in_state(state, crtc, cstate, i)
> +	for_each_new_crtc_in_state(state, crtc, cstate, i)
>  		changed = true;
>  	if (!changed)
>  		return 0;
> @@ -4327,7 +4327,7 @@ skl_compute_wm(struct drm_atomic_state *state)
>  	 * should allow skl_update_pipe_wm() to return failure in cases where
>  	 * no suitable watermark values can be found.
>  	 */
> -	for_each_crtc_in_state(state, crtc, cstate, i) {
> +	for_each_new_crtc_in_state(state, crtc, cstate, i) {
>  		struct intel_crtc_state *intel_cstate =
>  			to_intel_crtc_state(cstate);
>  		const struct skl_pipe_wm *old_pipe_wm =
> -- 
> 2.7.4
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-13 10:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 14:52 [PATCH 0/5] drm/i915: Use new atomic iterator macros Maarten Lankhorst
2017-03-09 14:52 ` [PATCH 1/5] drm/i915: Use new atomic iterator macros in ddi Maarten Lankhorst
2017-03-13  8:40   ` Daniel Vetter
2017-03-09 14:52 ` [PATCH 2/5] drm/i915: Use new atomic iterator macros in fbc Maarten Lankhorst
2017-03-13 10:05   ` Daniel Vetter
2017-03-09 14:52 ` [PATCH 3/5] drm/i915: Use new atomic iterator macros in wm code Maarten Lankhorst
2017-03-13 10:07   ` Daniel Vetter [this message]
2017-03-09 14:52 ` [PATCH 4/5] drm/i915: Use new atomic iterator macros in display code Maarten Lankhorst
2017-03-13 10:15   ` Daniel Vetter
2017-03-13 11:08     ` Maarten Lankhorst
2017-03-14  6:50       ` Daniel Vetter
2017-03-15  8:23         ` Maarten Lankhorst
2017-03-16  8:47           ` Daniel Vetter
2017-07-19 11:58             ` Maarten Lankhorst
2017-03-09 14:52 ` [PATCH 5/5] drm/i915: Use new atomic iterator macros in cdclk Maarten Lankhorst
2017-03-13 10:15   ` Daniel Vetter
2017-03-09 18:18 ` ✓ Fi.CI.BAT: success for drm/i915: Use new atomic iterator macros Patchwork
2017-03-09 18:35 ` [PATCH 0/5] " Ville Syrjälä
2017-03-13 11:08   ` 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=20170313100753.ijnryf35xxvx7xgu@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.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.