From: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v7 7/7] drm/i915/dsc: Check if vblank is sufficient for dsc prefill
Date: Fri, 17 Jan 2025 13:14:21 +0530 [thread overview]
Message-ID: <20250117074422.3965519-8-mitulkumar.ajitkumar.golani@intel.com> (raw)
In-Reply-To: <20250117074422.3965519-1-mitulkumar.ajitkumar.golani@intel.com>
High refresh rate panels which may have small line times
and vblank sizes, Check if vblank size is sufficient for
dsc prefill latency.
--v2:
- Consider chroma downscaling factor in latency calculation. [Ankit]
- Replace with appropriate function name.
--v3:
- Remove FIXME tag.[Ankit]
- Replace Ycbcr444 to Ycbcr420.[Anit]
- Correct precision. [Ankit]
- Use some local valiables like linetime_factor and latency to
adjust precision.
- Declare latency to 0 initially to avoid returning any garbage values.
- Account for second scaler downscaling factor as well. [Ankit]
--v4:
- Improvise hscale and vscale calculation. [Ankit]
- Use appropriate name for number of scaler users. [Ankit]
- Update commit message and rebase.
- Add linetime and cdclk prefill adjustment calculation. [Ankit]
--v5:
- Update bspec link in trailer. [Ankit]
- Correct hscale, vscale datatype. [Ankit]
- Use intel_crtc_compute_min_cdclk. [Ankit]
--v6:
- Use cdclk_state->logical.cdclk instead of
intel_crtc_compute_min_cdclk. [Ankit]
Bspec: 70151
Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
---
drivers/gpu/drm/i915/display/skl_watermark.c | 34 +++++++++++++++++++-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/skl_watermark.c b/drivers/gpu/drm/i915/display/skl_watermark.c
index c8e540dd66cc..aacda7f7174c 100644
--- a/drivers/gpu/drm/i915/display/skl_watermark.c
+++ b/drivers/gpu/drm/i915/display/skl_watermark.c
@@ -2307,6 +2307,38 @@ cdclk_prefill_adjustment(const struct intel_crtc_state *crtc_state)
2 * cdclk_state->logical.cdclk));
}
+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 latency = 0;
+ int num_scaler_users = hweight32(scaler_state->scaler_users);
+ int chroma_downscaling_factor =
+ crtc_state->output_format == INTEL_OUTPUT_FORMAT_YCBCR420 ? 2 : 1;
+ u64 hscale_k[2] = {0, 0};
+ u64 vscale_k[2] = {0, 0};
+
+ if (!crtc_state->dsc.compression_enable || !num_scaler_users)
+ return latency;
+
+ for (int i = 0; i < num_scaler_users; i++) {
+ hscale_k[i] =
+ max(1000, mul_u32_u32(scaler_state->scalers[i].hscale, 1000) >> 16);
+ vscale_k[i] =
+ max(1000, mul_u32_u32(scaler_state->scalers[i].vscale, 1000) >> 16);
+ }
+
+ latency = DIV_ROUND_UP_ULL(hscale_k[0] * vscale_k[0], 1000000);
+
+ if (num_scaler_users > 1)
+ latency *= DIV_ROUND_UP_ULL(hscale_k[1] * vscale_k[1], 1000000);
+
+ latency *= DIV_ROUND_UP(15 * crtc_state->linetime, 10) * chroma_downscaling_factor;
+
+ return latency * cdclk_prefill_adjustment(crtc_state);
+}
+
static int
scaler_prefill_latency(const struct intel_crtc_state *crtc_state)
{
@@ -2346,10 +2378,10 @@ skl_is_vblank_too_short(const struct intel_crtc_state *crtc_state,
const struct drm_display_mode *adjusted_mode =
&crtc_state->hw.adjusted_mode;
- /* FIXME missing DSC pre-fill time */
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;
}
--
2.48.1
next prev parent reply other threads:[~2025-01-17 7:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 7:44 [PATCH v7 0/7] Check Scaler and DSC Prefill Latency Against Vblank Mitul Golani
2025-01-17 7:44 ` [PATCH v7 1/7] drm/i915/scaler: Add and compute scaling factors Mitul Golani
2025-01-17 7:44 ` [PATCH v7 2/7] drm/i915/scaler: Use crtc_state to setup plane or pipe scaler Mitul Golani
2025-01-17 7:44 ` [PATCH v7 3/7] drm/i915/scaler: Refactor max_scale computation Mitul Golani
2025-01-17 7:44 ` [PATCH v7 4/7] drm/i915/scaler: Compute scaling factors for pipe scaler Mitul Golani
2025-01-17 7:44 ` [PATCH v7 5/7] drm/i915/scaler: Limit pipe scaler downscaling factors for YUV420 Mitul Golani
2025-01-17 7:44 ` [PATCH v7 6/7] drm/i915/scaler: Check if vblank is sufficient for scaler Mitul Golani
2025-01-17 7:44 ` Mitul Golani [this message]
2025-01-17 8:42 ` ✓ CI.Patch_applied: success for Check Scaler and DSC Prefill Latency Against Vblank (rev5) Patchwork
2025-01-17 8:43 ` ✓ CI.checkpatch: " Patchwork
2025-01-17 8:44 ` ✓ CI.KUnit: " Patchwork
2025-01-17 9:17 ` ✓ CI.Build: " Patchwork
2025-01-17 9:19 ` ✓ CI.Hooks: " Patchwork
2025-01-17 9:21 ` ✗ CI.checksparse: warning " Patchwork
2025-01-17 9:48 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-17 15:31 ` ✗ 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=20250117074422.3965519-8-mitulkumar.ajitkumar.golani@intel.com \
--to=mitulkumar.ajitkumar.golani@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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