All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [RFC v2 3/6] drm/i915/scaler: Use crtc_state to setup plane or pipe scaler
Date: Mon, 23 Dec 2024 14:39:09 +0530	[thread overview]
Message-ID: <43d6dbbd-5b5e-422c-bf1d-e3b7550fa011@intel.com> (raw)
In-Reply-To: <20241217180710.1048355-4-mitulkumar.ajitkumar.golani@intel.com>


On 12/17/2024 11:37 PM, Mitul Golani wrote:
> Parse crtc_state to intel_atomic_setup_scaler, this will help to

I think you mean 'pass' here.

Regards,

Ankit

> check if pch_pfit enabled or not and also will be useful to parse
> scaler_state with the same.
>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> ---
>   drivers/gpu/drm/i915/display/skl_scaler.c | 8 +++++---
>   1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c b/drivers/gpu/drm/i915/display/skl_scaler.c
> index e113c6ba4de7..1c65b53b45f0 100644
> --- a/drivers/gpu/drm/i915/display/skl_scaler.c
> +++ b/drivers/gpu/drm/i915/display/skl_scaler.c
> @@ -308,13 +308,15 @@ static int intel_allocate_scaler(struct intel_crtc_scaler_state *scaler_state,
>   	return -1;
>   }
>   
> -static int intel_atomic_setup_scaler(struct intel_crtc_scaler_state *scaler_state,
> +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,
>   				     struct intel_plane_state *plane_state,
>   				     int *scaler_id)
>   {
>   	struct intel_display *display = to_intel_display(crtc);
> +	struct intel_crtc_scaler_state *scaler_state =
> +					&crtc_state->scaler_state;
>   	struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
>   	u32 mode;
>   
> @@ -444,7 +446,7 @@ static int setup_crtc_scaler(struct intel_atomic_state *state,
>   	struct intel_crtc_scaler_state *scaler_state =
>   		&crtc_state->scaler_state;
>   
> -	return intel_atomic_setup_scaler(scaler_state,
> +	return intel_atomic_setup_scaler(crtc_state,
>   					 hweight32(scaler_state->scaler_users),
>   					 crtc, "CRTC", crtc->base.base.id,
>   					 NULL, &scaler_state->scaler_id);
> @@ -479,7 +481,7 @@ static int setup_plane_scaler(struct intel_atomic_state *state,
>   	if (IS_ERR(plane_state))
>   		return PTR_ERR(plane_state);
>   
> -	return intel_atomic_setup_scaler(scaler_state,
> +	return intel_atomic_setup_scaler(crtc_state,
>   					 hweight32(scaler_state->scaler_users),
>   					 crtc, "PLANE", plane->base.base.id,
>   					 plane_state, &plane_state->scaler_id);

  reply	other threads:[~2024-12-23  9:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 18:07 [RFC v2 0/6] Check if is vblank too short Mitul Golani
2024-12-17 18:07 ` [RFC v2 1/6] drm/i915/scaler: Add and compute scaling factors Mitul Golani
2024-12-23  8:28   ` Nautiyal, Ankit K
2025-01-06 16:59     ` Golani, Mitulkumar Ajitkumar
2024-12-17 18:07 ` [RFC v2 2/6] drm/i915/scaler: Add member to track scaler user Mitul Golani
2024-12-23  8:29   ` Nautiyal, Ankit K
2024-12-17 18:07 ` [RFC v2 3/6] drm/i915/scaler: Use crtc_state to setup plane or pipe scaler Mitul Golani
2024-12-23  9:09   ` Nautiyal, Ankit K [this message]
2024-12-17 18:07 ` [RFC v2 4/6] drm/i915/scaler: Compute scling factors for " Mitul Golani
2024-12-23  9:52   ` Nautiyal, Ankit K
2024-12-17 18:07 ` [RFC v2 5/6] drm/i915/scaler: Check if vblank is sufficient for scaler Mitul Golani
2024-12-23  9:59   ` Nautiyal, Ankit K
2024-12-30 14:17   ` Jani Nikula
2024-12-17 18:07 ` [RFC v2 6/6] drm/i915/dsc: Check if dsc prefill sufficient for vblank Mitul Golani
2024-12-23 10:05   ` Nautiyal, Ankit K
2024-12-17 23:04 ` ✓ CI.Patch_applied: success for Check if is vblank too short Patchwork
2024-12-17 23:04 ` ✓ CI.checkpatch: " Patchwork
2024-12-17 23:05 ` ✓ CI.KUnit: " Patchwork
2024-12-17 23:23 ` ✓ CI.Build: " Patchwork
2024-12-17 23:26 ` ✓ CI.Hooks: " Patchwork
2024-12-17 23:27 ` ✗ CI.checksparse: warning " Patchwork
2024-12-18  0:00 ` ✗ Xe.CI.BAT: failure " Patchwork
2024-12-18  9:07 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-12-18  9:19 ` ✗ i915.CI.BAT: failure " Patchwork
2024-12-18  9:24 ` ✗ Xe.CI.Full: " 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=43d6dbbd-5b5e-422c-bf1d-e3b7550fa011@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.