From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<v5-000intel-xe@lists.freedesktop.org>
Cc: <jani.nikula@intel.com>, <ville.syrjala@intel.com>
Subject: Re: [PATCH v5 3/7] drm/i915/scaler: Refactor max_scale computation
Date: Thu, 16 Jan 2025 17:17:48 +0530 [thread overview]
Message-ID: <b9617f03-dd7d-4600-8794-eeac36f06681@intel.com> (raw)
In-Reply-To: <20250115151714.3665211-4-mitulkumar.ajitkumar.golani@intel.com>
On 1/15/2025 8:47 PM, Mitul Golani wrote:
> Refactor max scaling factor computation into a reusable
> function for scalers.
>
> --v2:
> - Add missing comment. [Ankit]
>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
LGTM.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/skl_scaler.c | 70 +++++++++++++----------
> 1 file changed, 41 insertions(+), 29 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c b/drivers/gpu/drm/i915/display/skl_scaler.c
> index 12efa4008027..a832cdccd9fa 100644
> --- a/drivers/gpu/drm/i915/display/skl_scaler.c
> +++ b/drivers/gpu/drm/i915/display/skl_scaler.c
> @@ -319,6 +319,44 @@ static int intel_allocate_scaler(struct intel_crtc_scaler_state *scaler_state,
> return -1;
> }
>
> +static void
> +calculate_max_scale(struct intel_crtc *crtc,
> + bool is_yuv_semiplanar,
> + int scaler_id,
> + int *max_hscale, int *max_vscale)
> +{
> + struct intel_display *display = to_intel_display(crtc);
> +
> + /*
> + * FIXME: When two scalers are needed, but only one of
> + * them needs to downscale, we should make sure that
> + * the one that needs downscaling support is assigned
> + * as the first scaler, so we don't reject downscaling
> + * unnecessarily.
> + */
> +
> + if (DISPLAY_VER(display) >= 14) {
> + /*
> + * On versions 14 and up, only the first
> + * scaler supports a vertical scaling factor
> + * of more than 1.0, while a horizontal
> + * scaling factor of 3.0 is supported.
> + */
> + *max_hscale = 0x30000 - 1;
> +
> + if (scaler_id == 0)
> + *max_vscale = 0x30000 - 1;
> + else
> + *max_vscale = 0x10000;
> + } else if (DISPLAY_VER(display) >= 10 || !is_yuv_semiplanar) {
> + *max_hscale = 0x30000 - 1;
> + *max_vscale = 0x30000 - 1;
> + } else {
> + *max_hscale = 0x20000 - 1;
> + *max_vscale = 0x20000 - 1;
> + }
> +}
> +
> static int intel_atomic_setup_scaler(struct intel_crtc_state *crtc_state,
> int num_scalers_need, struct intel_crtc *crtc,
> const char *name, int idx,
> @@ -388,35 +426,9 @@ static int intel_atomic_setup_scaler(struct intel_crtc_state *crtc_state,
> const struct drm_rect *dst = &plane_state->uapi.dst;
> int hscale, vscale, max_vscale, max_hscale;
>
> - /*
> - * FIXME: When two scalers are needed, but only one of
> - * them needs to downscale, we should make sure that
> - * the one that needs downscaling support is assigned
> - * as the first scaler, so we don't reject downscaling
> - * unnecessarily.
> - */
> -
> - if (DISPLAY_VER(display) >= 14) {
> - /*
> - * On versions 14 and up, only the first
> - * scaler supports a vertical scaling factor
> - * of more than 1.0, while a horizontal
> - * scaling factor of 3.0 is supported.
> - */
> - max_hscale = 0x30000 - 1;
> - if (*scaler_id == 0)
> - max_vscale = 0x30000 - 1;
> - else
> - max_vscale = 0x10000;
> -
> - } else if (DISPLAY_VER(display) >= 10 ||
> - !intel_format_info_is_yuv_semiplanar(fb->format, fb->modifier)) {
> - max_hscale = 0x30000 - 1;
> - max_vscale = 0x30000 - 1;
> - } else {
> - max_hscale = 0x20000 - 1;
> - max_vscale = 0x20000 - 1;
> - }
> + calculate_max_scale(crtc,
> + intel_format_info_is_yuv_semiplanar(fb->format, fb->modifier),
> + *scaler_id, &max_hscale, &max_vscale);
>
> /*
> * FIXME: We should change the if-else block above to
next prev parent reply other threads:[~2025-01-16 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 15:17 [PATCH v5 0/7] Check Scaler and DSC Prefill Latency Against Vblank Mitul Golani
2025-01-15 15:17 ` [PATCH v5 1/7] drm/i915/scaler: Add and compute scaling factors Mitul Golani
2025-01-15 15:17 ` [PATCH v5 2/7] drm/i915/scaler: Use crtc_state to setup plane or pipe scaler Mitul Golani
2025-01-15 15:17 ` [PATCH v5 3/7] drm/i915/scaler: Refactor max_scale computation Mitul Golani
2025-01-16 11:47 ` Nautiyal, Ankit K [this message]
2025-01-15 15:17 ` [PATCH v5 4/7] drm/i915/scaler: Compute scaling factors for pipe scaler Mitul Golani
2025-01-16 11:51 ` Nautiyal, Ankit K
2025-01-15 15:17 ` [PATCH v5 5/7] drm/i915/scaler: Limit pipe scaler downscaling factors for YUV420 Mitul Golani
2025-01-16 12:02 ` Nautiyal, Ankit K
2025-01-15 15:17 ` [PATCH v5 6/7] drm/i915/scaler: Check if vblank is sufficient for scaler Mitul Golani
2025-01-16 13:01 ` Nautiyal, Ankit K
2025-01-15 15:17 ` [PATCH v5 7/7] drm/i915/dsc: Check if vblank is sufficient for dsc prefill Mitul Golani
2025-01-16 13:04 ` Nautiyal, Ankit K
2025-01-15 15:59 ` [PATCH v5 0/7] Check Scaler and DSC Prefill Latency Against Vblank Golani, Mitulkumar Ajitkumar
2025-01-15 22:07 ` ✗ Fi.CI.SPARSE: warning for Check Scaler and DSC Prefill Latency Against Vblank (rev3) Patchwork
2025-01-15 22:25 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-16 4:03 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-16 7:02 ` ✓ i915.CI.Full: success " 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=b9617f03-dd7d-4600-8794-eeac36f06681@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=v5-000intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@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