From: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, ankit.k.nautiyal@intel.com,
jani.nikula@intel.com
Subject: [PATCH v3 1/5] drm/i915/scaler: Add and compute scaling factors
Date: Mon, 6 Jan 2025 22:21:07 +0530 [thread overview]
Message-ID: <20250106165111.1672722-2-mitulkumar.ajitkumar.golani@intel.com> (raw)
In-Reply-To: <20250106165111.1672722-1-mitulkumar.ajitkumar.golani@intel.com>
Add scaling factors to scaler_state for a perticular scaler user,
use it later to compute scaler prefill latency. Also to extend this
when either pipe or plane scaler is in use.
Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
---
drivers/gpu/drm/i915/display/intel_display_types.h | 2 ++
drivers/gpu/drm/i915/display/skl_scaler.c | 3 +++
2 files changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
index f230163226d1..67c49a1d0232 100644
--- a/drivers/gpu/drm/i915/display/intel_display_types.h
+++ b/drivers/gpu/drm/i915/display/intel_display_types.h
@@ -711,6 +711,8 @@ struct intel_initial_plane_config {
struct intel_scaler {
u32 mode;
bool in_use;
+ int hscale;
+ int vscale;
};
struct intel_crtc_scaler_state {
diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c b/drivers/gpu/drm/i915/display/skl_scaler.c
index ae21fce534dc..6c69545fe172 100644
--- a/drivers/gpu/drm/i915/display/skl_scaler.c
+++ b/drivers/gpu/drm/i915/display/skl_scaler.c
@@ -424,6 +424,9 @@ static int intel_atomic_setup_scaler(struct intel_crtc_scaler_state *scaler_stat
return -EINVAL;
}
+
+ scaler_state->scalers[*scaler_id].hscale = hscale;
+ scaler_state->scalers[*scaler_id].vscale = vscale;
}
drm_dbg_kms(display->drm, "Attached scaler id %u.%u to %s:%d\n",
--
2.46.0
next prev parent reply other threads:[~2025-01-06 16:54 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 ` Mitul Golani [this message]
2025-01-07 13:00 ` [PATCH v3 1/5] drm/i915/scaler: Add and compute scaling factors 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
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=20250106165111.1672722-2-mitulkumar.ajitkumar.golani@intel.com \
--to=mitulkumar.ajitkumar.golani@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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