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 2/4] drm/i915/lobf: Move Lobf compute config after vblank adjustement
Date: Thu, 12 Sep 2024 03:09:50 +0300 [thread overview]
Message-ID: <ZuIxTlhkjCNNtlDW@intel.com> (raw)
In-Reply-To: <20240905051841.3012729-3-animesh.manna@intel.com>
On Thu, Sep 05, 2024 at 10:48:39AM +0530, Animesh Manna wrote:
> As lobf compute config is depends upon delayed vbalnk so moved
Actually no.
The code is as follows:
guardband = adjusted_mode->crtc_vtotal - adjusted_mode->crtc_vdisplay - context_latency;
Add context_latency to both sides:
context_latency + guardband = adjusted_mode->crtc_vtotal - adjusted_mode->crtc_vdisplay;
Substitute into:
crtc_state->has_lobf = (context_latency + guardband) >
(first_sdp_position + waketime_in_lines);
and you have no vblank delay anywhere.
Someone should just rewrite that to use that simple formula.
Now, that code is using the non-VRR timings for all this computation
so technically it might not even be computing the correct thing when
using VRR, but I guess that's more of a problem for the "let's use
the VRR timing generator fixed refersh stuff" because we really
should match the non-VRR timings there...
> lobf compute config in encoder late config(). Lobf is only
> for edp connector so introduced intel_dp_late_compute_config().
>
> v1: Initial version.
> v2: Function name modified. [Jani]
>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_ddi.c | 5 +++++
> drivers/gpu/drm/i915/display/intel_dp.c | 9 ++++++++-
> drivers/gpu/drm/i915/display/intel_dp.h | 2 ++
> 3 files changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
> index 00fbe9f8c03a..0d12c94793bf 100644
> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> @@ -4367,6 +4367,11 @@ static int intel_ddi_compute_config_late(struct intel_encoder *encoder,
> port_sync_transcoders & ~BIT(crtc_state->cpu_transcoder);
> }
>
> + if (intel_crtc_has_type(crtc_state, INTEL_OUTPUT_DP) ||
> + intel_crtc_has_type(crtc_state, INTEL_OUTPUT_EDP)) {
> + intel_dp_compute_config_late(encoder, crtc_state);
> + }
> +
> return 0;
> }
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 86bc6d79279f..bc0042a1bc3a 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -3107,7 +3107,6 @@ intel_dp_compute_config(struct intel_encoder *encoder,
> intel_vrr_compute_config(pipe_config, conn_state);
> intel_dp_compute_as_sdp(intel_dp, pipe_config);
> intel_psr_compute_config(intel_dp, pipe_config, conn_state);
> - intel_alpm_lobf_compute_config(intel_dp, pipe_config);
> intel_dp_drrs_compute_config(connector, pipe_config, link_bpp_x16);
> intel_dp_compute_vsc_sdp(intel_dp, pipe_config, conn_state);
> intel_dp_compute_hdr_metadata_infoframe_sdp(intel_dp, pipe_config, conn_state);
> @@ -3116,6 +3115,14 @@ intel_dp_compute_config(struct intel_encoder *encoder,
> pipe_config);
> }
>
> +void intel_dp_compute_config_late(struct intel_encoder *encoder,
> + struct intel_crtc_state *crtc_state)
> +{
> + struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
> +
> + intel_alpm_lobf_compute_config(intel_dp, crtc_state);
> +}
> +
> void intel_dp_set_link_params(struct intel_dp *intel_dp,
> int link_rate, int lane_count)
> {
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.h b/drivers/gpu/drm/i915/display/intel_dp.h
> index 1b9aaddd8c35..411feece9acb 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.h
> +++ b/drivers/gpu/drm/i915/display/intel_dp.h
> @@ -74,6 +74,8 @@ void intel_dp_encoder_flush_work(struct drm_encoder *encoder);
> int intel_dp_compute_config(struct intel_encoder *encoder,
> struct intel_crtc_state *pipe_config,
> struct drm_connector_state *conn_state);
> +void intel_dp_compute_config_late(struct intel_encoder *encoder,
> + struct intel_crtc_state *crtc_state);
> int intel_dp_dsc_compute_config(struct intel_dp *intel_dp,
> struct intel_crtc_state *pipe_config,
> struct drm_connector_state *conn_state,
> --
> 2.29.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-09-12 0:09 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ä [this message]
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ä
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=ZuIxTlhkjCNNtlDW@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.