From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>, <jani.nikula@intel.com>
Subject: Re: [PATCH v3 5/5] drm/i915/dsc: Check if dsc prefill sufficient for vblank
Date: Tue, 7 Jan 2025 19:36:28 +0530 [thread overview]
Message-ID: <3ef0243a-aa73-42bb-b4da-827996398611@intel.com> (raw)
In-Reply-To: <20250106165111.1672722-6-mitulkumar.ajitkumar.golani@intel.com>
On 1/6/2025 10:21 PM, Mitul Golani wrote:
> Check if dsc prefill latency is sufficient for vblank.
>
> --v2:
> - Consider chroma downscaling factor in latency calculation. [Ankit]
> - Replace function name from dsc_prefill_time to dsc_prefill_latency.
>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> ---
> drivers/gpu/drm/i915/display/skl_watermark.c | 25 ++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/skl_watermark.c b/drivers/gpu/drm/i915/display/skl_watermark.c
> index 95f60819fe0a..900e1c54450d 100644
> --- a/drivers/gpu/drm/i915/display/skl_watermark.c
> +++ b/drivers/gpu/drm/i915/display/skl_watermark.c
> @@ -2292,6 +2292,30 @@ static int icl_build_plane_wm(struct intel_crtc_state *crtc_state,
> return 0;
> }
>
> +static int
> +dsc_prefill_latency(const struct intel_crtc_state *crtc_state)
> +{
> + const struct intel_crtc_scaler_state *scaler_state =
> + &crtc_state->scaler_state;
> + int hscale = scaler_state->scalers[0].hscale;
> + int vscale = scaler_state->scalers[0].vscale;
> +
> + if (!crtc_state->dsc.compression_enable)
> + return 0;
> + /*
> + * FIXME: CDCLK Prefill adjustment to add
> + */
I am not sure about this.
> + if (scaler_state->scaler_users) {
> + int chroma_downscaling_factor =
> + crtc_state->output_format == INTEL_OUTPUT_FORMAT_YCBCR444 ? 2 : 1;
Ycbcr420 as mentioned in previous patch.
> +
> + return DIV_ROUND_UP(15 * crtc_state->linetime * hscale * vscale *
This again need to have hscale and vscale right shifted by 16 like the
previous patch.
Also, it would be good to add bspec reference in commit message.
Regards,
Ankit
> + chroma_downscaling_factor, 10);
> + }
> +
> + return 0;
> +}
> +
> static int
> scaler_prefill_latency(const struct intel_crtc_state *crtc_state)
> {
> @@ -2333,6 +2357,7 @@ skl_is_vblank_too_short(const struct intel_crtc_state *crtc_state,
> return crtc_state->framestart_delay +
> intel_usecs_to_scanlines(adjusted_mode, latency) +
> scaler_prefill_latency(crtc_state) +
> + dsc_prefill_latency(crtc_state) +
> wm0_lines >
> adjusted_mode->crtc_vtotal - adjusted_mode->crtc_vblank_start;
> }
next prev parent reply other threads:[~2025-01-07 14:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 16:51 [PATCH v3 0/5] Check Scaler and DSC Prefill Latency Against Vblank Mitul Golani
2025-01-06 16:51 ` [PATCH v3 1/5] drm/i915/scaler: Add and compute scaling factors Mitul Golani
2025-01-07 13:00 ` Nautiyal, Ankit K
2025-01-06 16:51 ` [PATCH v3 2/5] drm/i915/scaler: Use crtc_state to setup plane or pipe scaler Mitul Golani
2025-01-07 13:04 ` Nautiyal, Ankit K
2025-01-06 16:51 ` [PATCH v3 3/5] drm/i915/scaler: Compute scaling factors for " Mitul Golani
2025-01-07 13:54 ` Nautiyal, Ankit K
2025-01-08 8:45 ` Dan Carpenter
2025-01-08 13:29 ` Golani, Mitulkumar Ajitkumar
2025-01-06 16:51 ` [PATCH v3 4/5] drm/i915/scaler: Check if vblank is sufficient for scaler Mitul Golani
2025-01-07 14:01 ` Nautiyal, Ankit K
2025-01-06 16:51 ` [PATCH v3 5/5] drm/i915/dsc: Check if dsc prefill sufficient for vblank Mitul Golani
2025-01-07 14:06 ` Nautiyal, Ankit K [this message]
2025-01-06 17:17 ` ✓ CI.Patch_applied: success for Check Scaler and DSC Prefill Latency Against Vblank Patchwork
2025-01-06 17:17 ` ✓ CI.checkpatch: " Patchwork
2025-01-06 17:19 ` ✓ CI.KUnit: " Patchwork
2025-01-06 17:37 ` ✓ CI.Build: " Patchwork
2025-01-06 17:39 ` ✓ CI.Hooks: " Patchwork
2025-01-06 17:41 ` ✗ CI.checksparse: warning " Patchwork
2025-01-06 18:07 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-07 11:57 ` ✗ Xe.CI.Full: 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=3ef0243a-aa73-42bb-b4da-827996398611@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox