From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Animesh Manna <animesh.manna@intel.com>
Cc: intel-gfx@lists.freedesktop.org, jani.nikula@intel.com,
jouni.hogander@intel.com, arun.r.murthy@intel.com,
ankit.k.nautiyal@intel.com,
mitulkumar.ajitkumar.golani@intel.com
Subject: Re: [PATCH v10 3/4] drm/i915/vrr: Split vrr-compute-config in two phases
Date: Thu, 12 Sep 2024 03:10:28 +0300 [thread overview]
Message-ID: <ZuIxdIP6P437YvOH@intel.com> (raw)
In-Reply-To: <20240905051841.3012729-4-animesh.manna@intel.com>
On Thu, Sep 05, 2024 at 10:48:40AM +0530, Animesh Manna wrote:
> As vrr guardband calculation is dependent on modified
> vblank start so better to compute late after all
> vblank adjustement.
>
> v1: Initial version.
> v2: Split in a separate patch from panel-replay workaround. [Ankit]
>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 16 ++++++++++++++++
> drivers/gpu/drm/i915/display/intel_vrr.c | 13 -------------
> 2 files changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index b4ef4d59da1a..7fb3d35f7124 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -4794,10 +4794,26 @@ intel_modeset_pipe_config_late(struct intel_atomic_state *state,
> {
> struct intel_crtc_state *crtc_state =
> intel_atomic_get_new_crtc_state(state, crtc);
> + struct drm_display_mode *adjusted_mode = &crtc_state->hw.adjusted_mode;
> struct drm_connector_state *conn_state;
> struct drm_connector *connector;
> int i;
>
> + if (crtc_state->vrr.enable) {
> + /*
> + * For XE_LPD+, we use guardband and pipeline override
> + * is deprecated.
> + */
> + if (DISPLAY_VER(to_i915(crtc->base.dev)) >= 13) {
> + crtc_state->vrr.guardband =
> + crtc_state->vrr.vmin + 1 - adjusted_mode->crtc_vblank_start;
> + } else {
> + crtc_state->vrr.pipeline_full =
> + min(255, crtc_state->vrr.vmin - adjusted_mode->crtc_vblank_start -
> + crtc_state->framestart_delay - 1);
> + }
> + }
Pretty sure I asked that to be a proper function in some earlier reply.
> +
> for_each_new_connector_in_state(&state->base, connector,
> conn_state, i) {
> struct intel_encoder *encoder =
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index 9a51f5bac307..de17a8ae831b 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -239,19 +239,6 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
> (crtc_state->hw.adjusted_mode.crtc_vtotal -
> crtc_state->hw.adjusted_mode.vsync_end);
> }
> -
> - /*
> - * For XE_LPD+, we use guardband and pipeline override
> - * is deprecated.
> - */
> - if (DISPLAY_VER(display) >= 13) {
> - crtc_state->vrr.guardband =
> - crtc_state->vrr.vmin + 1 - adjusted_mode->crtc_vblank_start;
> - } else {
> - crtc_state->vrr.pipeline_full =
> - min(255, crtc_state->vrr.vmin - adjusted_mode->crtc_vblank_start -
> - crtc_state->framestart_delay - 1);
> - }
> }
>
> static u32 trans_vrr_ctl(const struct intel_crtc_state *crtc_state)
> --
> 2.29.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-09-12 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 5:18 [PATCH v10 0/4] Vrr refactoring and panel replay workaround Animesh Manna
2024-09-05 5:18 ` [PATCH v10 1/4] drm/i915/lobf: No need to pass connector-state on lobf-compute-config Animesh Manna
2024-09-12 10:07 ` Jani Nikula
2024-09-13 10:10 ` Manna, Animesh
2024-09-05 5:18 ` [PATCH v10 2/4] drm/i915/lobf: Move Lobf compute config after vblank adjustement Animesh Manna
2024-09-12 0:09 ` Ville Syrjälä
2024-09-13 10:15 ` Manna, Animesh
2024-09-05 5:18 ` [PATCH v10 3/4] drm/i915/vrr: Split vrr-compute-config in two phases Animesh Manna
2024-09-12 0:10 ` Ville Syrjälä [this message]
2024-09-12 6:00 ` Manna, Animesh
2024-09-05 5:18 ` [PATCH v10 4/4] drm/i915/panelreplay: Panel replay workaround with VRR Animesh Manna
2024-09-05 6:14 ` ✓ Fi.CI.BAT: success for Vrr refactoring and panel replay workaround Patchwork
2024-09-06 15:47 ` ✗ 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=ZuIxdIP6P437YvOH@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=animesh.manna@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@intel.com \
--cc=mitulkumar.ajitkumar.golani@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.