From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 6/9] drm/i915: Fix g4x/vlv/chv CxSR vs. format/tiling/rotation changes
Date: Fri, 7 Oct 2022 08:57:55 +0300 [thread overview]
Message-ID: <Yz+/42F7ie9R+f9m@intel.com> (raw)
In-Reply-To: <20220622155452.32587-7-ville.syrjala@linux.intel.com>
On Wed, Jun 22, 2022 at 06:54:49PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> On g4x/vlv/chv the hardware seems incapable of changing the pixel
> format, rotation, or YUV->RGB CSC matrix while in CxSR.
>
> Additionally on VLV/CHV the sprites seem incapable of tiling
> changes while in CxSR. On g4x CxSR is not even possible with
> the sprite enabled. Curiously the primary plane seems perfectly
> happy when changing tiling during CxSR.
>
> Pimp up the code to account for these when determining whether
> CxSR needs to be disabled. Since it looks like most of the plane
> control register bits are affected let's just compare that.
> But in the name of efficiency we'll make an exception for the
> primary plane tiling changes (avoids some extra vblank waits).
>
> v2: Just use the pre-computed plane control register values
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
> .../gpu/drm/i915/display/intel_atomic_plane.c | 53 ++++++++++++++++---
> 1 file changed, 45 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_atomic_plane.c b/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> index efe8591619e3..e5ad6a437a97 100644
> --- a/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> +++ b/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> @@ -426,6 +426,47 @@ static bool intel_plane_do_async_flip(struct intel_plane *plane,
> return DISPLAY_VER(i915) < 13 || old_crtc_state->uapi.async_flip;
> }
>
> +static bool i9xx_must_disable_cxsr(const struct intel_crtc_state *new_crtc_state,
> + const struct intel_plane_state *old_plane_state,
> + const struct intel_plane_state *new_plane_state)
> +{
> + struct intel_plane *plane = to_intel_plane(new_plane_state->uapi.plane);
> + bool old_visible = old_plane_state->uapi.visible;
> + bool new_visible = new_plane_state->uapi.visible;
> + u32 old_ctl = old_plane_state->ctl;
> + u32 new_ctl = new_plane_state->ctl;
> + bool modeset, turn_on, turn_off;
> +
> + if (plane->id == PLANE_CURSOR)
> + return false;
> +
> + modeset = intel_crtc_needs_modeset(new_crtc_state);
> + turn_off = old_visible && (!new_visible || modeset);
> + turn_on = new_visible && (!old_visible || modeset);
> +
> + /* Must disable CxSR around plane enable/disable */
> + if (turn_on || turn_off)
> + return true;
> +
> + if (!old_visible || !new_visible)
> + return false;
> +
> + /*
> + * Most plane control register updates are blocked while in CxSR.
> + *
> + * Tiling mode is one exception where the primary plane can
> + * apparently handle it, whereas the sprites can not (the
> + * sprite issue being only relevant on VLV/CHV where CxSR
> + * is actually possible with a sprite enabled).
> + */
> + if (plane->id == PLANE_PRIMARY) {
> + old_ctl &= ~DISP_TILED;
> + new_ctl &= ~DISP_TILED;
> + }
> +
> + return old_ctl != new_ctl;
> +}
> +
> static int intel_plane_atomic_calc_changes(const struct intel_crtc_state *old_crtc_state,
> struct intel_crtc_state *new_crtc_state,
> const struct intel_plane_state *old_plane_state,
> @@ -483,17 +524,9 @@ static int intel_plane_atomic_calc_changes(const struct intel_crtc_state *old_cr
> if (turn_on) {
> if (DISPLAY_VER(dev_priv) < 5 && !IS_G4X(dev_priv))
> new_crtc_state->update_wm_pre = true;
> -
> - /* must disable cxsr around plane enable/disable */
> - if (plane->id != PLANE_CURSOR)
> - new_crtc_state->disable_cxsr = true;
> } else if (turn_off) {
> if (DISPLAY_VER(dev_priv) < 5 && !IS_G4X(dev_priv))
> new_crtc_state->update_wm_post = true;
> -
> - /* must disable cxsr around plane enable/disable */
> - if (plane->id != PLANE_CURSOR)
> - new_crtc_state->disable_cxsr = true;
> } else if (intel_wm_need_update(old_plane_state, new_plane_state)) {
> if (DISPLAY_VER(dev_priv) < 5 && !IS_G4X(dev_priv)) {
> /* FIXME bollocks */
> @@ -505,6 +538,10 @@ static int intel_plane_atomic_calc_changes(const struct intel_crtc_state *old_cr
> if (visible || was_visible)
> new_crtc_state->fb_bits |= plane->frontbuffer_bit;
>
> + if (HAS_GMCH(dev_priv) &&
> + i9xx_must_disable_cxsr(new_crtc_state, old_plane_state, new_plane_state))
> + new_crtc_state->disable_cxsr = true;
> +
> /*
> * ILK/SNB DVSACNTR/Sprite Enable
> * IVB SPR_CTL/Sprite Enable
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-10-07 5:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 15:54 [Intel-gfx] [PATCH v2 0/9] drm/i915: g4x/vlv/chv CxSR/wm fixes/cleanups Ville Syrjala
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 1/9] drm/i915: Split g4x_compute_pipe_wm() into two Ville Syrjala
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 2/9] drm/i915: Split vlv_compute_pipe_wm() " Ville Syrjala
2022-09-21 15:07 ` Lisovskiy, Stanislav
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 3/9] drm/i915: Simplify up g4x watermark sanitation Ville Syrjala
2022-09-21 15:10 ` Lisovskiy, Stanislav
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 4/9] drm/i915: Simplify up vlv " Ville Syrjala
2022-09-21 15:13 ` Lisovskiy, Stanislav
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 5/9] drm/i915: Add missing invalidate to g4x wm readout Ville Syrjala
2022-09-21 15:14 ` Lisovskiy, Stanislav
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 6/9] drm/i915: Fix g4x/vlv/chv CxSR vs. format/tiling/rotation changes Ville Syrjala
2022-10-07 5:57 ` Lisovskiy, Stanislav [this message]
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 7/9] drm/i915: Fix pipe gamma enable/disable vs. CxSR on gmch platforms Ville Syrjala
2022-10-07 6:01 ` Lisovskiy, Stanislav
2022-10-07 6:21 ` Ville Syrjälä
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 8/9] drm/i915: Write watermarks for disabled pipes " Ville Syrjala
2022-10-07 6:03 ` Lisovskiy, Stanislav
2022-06-22 15:54 ` [Intel-gfx] [PATCH v2 9/9] drm/i915: Enable atomic by default on ctg/elk Ville Syrjala
2022-06-23 18:34 ` Jani Nikula
2022-06-22 23:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: g4x/vlv/chv CxSR/wm fixes/cleanups (rev3) Patchwork
2022-06-27 11:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=Yz+/42F7ie9R+f9m@intel.com \
--to=stanislav.lisovskiy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox