Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	<intel-xe@lists.freedesktop.org>,
	 <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915/scaler: Use intel_display as argument to skl_scaler_max_src_size
Date: Wed, 9 Jul 2025 08:37:07 +0530	[thread overview]
Message-ID: <b8e11773-71b1-4834-9476-0db1b2bb9daf@intel.com> (raw)
In-Reply-To: <20250708043328.1086192-1-suraj.kandpal@intel.com>


On 7/8/2025 10:03 AM, Suraj Kandpal wrote:
> skl_scaler_max_src_size has really no use of intel_crtc other than
> deriving intel_display. Let's just pass intel_display to it directly.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>


> ---
>   drivers/gpu/drm/i915/display/skl_scaler.c | 6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c b/drivers/gpu/drm/i915/display/skl_scaler.c
> index d77798499c57..a6ba9da03542 100644
> --- a/drivers/gpu/drm/i915/display/skl_scaler.c
> +++ b/drivers/gpu/drm/i915/display/skl_scaler.c
> @@ -91,11 +91,9 @@ static void skl_scaler_min_src_size(const struct drm_format_info *format,
>   	}
>   }
>   
> -static void skl_scaler_max_src_size(struct intel_crtc *crtc,
> +static void skl_scaler_max_src_size(struct intel_display *display,
>   				    int *max_w, int *max_h)
>   {
> -	struct intel_display *display = to_intel_display(crtc);
> -
>   	if (DISPLAY_VER(display) >= 14) {
>   		*max_w = 4096;
>   		*max_h = 8192;
> @@ -201,7 +199,7 @@ skl_update_scaler(struct intel_crtc_state *crtc_state, bool force_detach,
>   	}
>   
>   	skl_scaler_min_src_size(format, modifier, &min_src_w, &min_src_h);
> -	skl_scaler_max_src_size(crtc, &max_src_w, &max_src_h);
> +	skl_scaler_max_src_size(display, &max_src_w, &max_src_h);
>   
>   	skl_scaler_min_dst_size(&min_dst_w, &min_dst_h);
>   	skl_scaler_max_dst_size(crtc, &max_dst_w, &max_dst_h);

      parent reply	other threads:[~2025-07-09  3:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  4:33 [PATCH 1/2] drm/i915/scaler: Use intel_display as argument to skl_scaler_max_src_size Suraj Kandpal
2025-07-08  4:33 ` [PATCH 2/2] drm/i915/xe3lpd: Prune modes for YUV420 Suraj Kandpal
2025-07-09  3:03   ` Nautiyal, Ankit K
2025-07-08  4:48 ` ✓ CI.KUnit: success for series starting with [1/2] drm/i915/scaler: Use intel_display as argument to skl_scaler_max_src_size Patchwork
2025-07-08  5:28 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-08  7:15 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-09  3:07 ` Nautiyal, Ankit K [this message]

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=b8e11773-71b1-4834-9476-0db1b2bb9daf@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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