From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't set update_wm_post on g4x+
Date: Wed, 6 Feb 2019 11:19:04 -0800 [thread overview]
Message-ID: <20190206191904.GA14950@intel.com> (raw)
In-Reply-To: <20190206185433.8116-1-ville.syrjala@linux.intel.com>
On Wed, Feb 06, 2019 at 08:54:33PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> update_wm_post is meant for pre-g4x only. Don't ever set
> it on g4x+.
>
> The only effect of a bogus update_wm_post on g4x+ could
> be that we clear the legacy_cursor_update flag in
> intel_atomic_commit(). Since legacy_cursor_update is
> only set for legacy cursor updates (as the name suggests)
> and we only set update_wm_post for a modeset the two
> cases should never occur at the same time. But let's
> be consistent in setting update_wm_post so we don't
> end up confusing so many people.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
as one of the people that got confused with this at
some point as well,
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 4d5ec929f987..91b274ea16c4 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11063,7 +11063,8 @@ static int intel_crtc_atomic_check(struct drm_crtc *crtc,
> int ret;
> bool mode_changed = needs_modeset(crtc_state);
>
> - if (mode_changed && !crtc_state->active)
> + if (INTEL_GEN(dev_priv) < 5 && !IS_G4X(dev_priv) &&
> + mode_changed && !crtc_state->active)
> pipe_config->update_wm_post = true;
>
> if (mode_changed && crtc_state->enable &&
> --
> 2.19.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-06 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 18:54 [PATCH] drm/i915: Don't set update_wm_post on g4x+ Ville Syrjala
2019-02-06 19:19 ` Rodrigo Vivi [this message]
2019-02-06 19:46 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-02-06 22:07 ` ✓ Fi.CI.IGT: " Patchwork
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=20190206191904.GA14950@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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.