All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Cc: Nemesa Garg <nemesa.garg@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/display: Check number of scalers for casf
Date: Mon, 24 Nov 2025 23:07:46 +0200	[thread overview]
Message-ID: <aSTJIoHSCRuomRFk@intel.com> (raw)
In-Reply-To: <313381a1-6195-4ea5-a25c-0f34d6a57bfb@intel.com>

On Mon, Nov 24, 2025 at 04:39:43PM +0530, Nautiyal, Ankit K wrote:
> 
> On 11/24/2025 2:16 PM, Nemesa Garg wrote:
> > Before exposing the property check if the number of scalers
> > is 2 as casf needs second scaler. If not then dont expose the
> > property.
> 
> 
> We are not checking if num_scalers == 2. So the commit message is a bit 
> misleading.
> 
> Need bit more context:
> 
> CASF requires the second scaler for sharpness. Skip creating the 
> 'SHARPNESS_STRENGTH' property when num_scalers <= 1.

Does it really need two scalers always, or just when the first scaler
is doing actual scaling/etc?

> 
> Also, it would be good to align the commit message with this explanation.
> 
> 
> Regards,
> 
> Ankit
> 
> >
> > Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
> > ---
> >   drivers/gpu/drm/i915/display/intel_crtc.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c b/drivers/gpu/drm/i915/display/intel_crtc.c
> > index 153ff4b4b52c..963e6c7d75b8 100644
> > --- a/drivers/gpu/drm/i915/display/intel_crtc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
> > @@ -395,7 +395,7 @@ int intel_crtc_init(struct intel_display *display, enum pipe pipe)
> >   
> >   	drm_WARN_ON(display->drm, drm_crtc_index(&crtc->base) != crtc->pipe);
> >   
> > -	if (HAS_CASF(display))
> > +	if (HAS_CASF(display) && crtc->num_scalers > 1)
> >   		drm_crtc_create_sharpness_strength_property(&crtc->base);
> >   
> >   	return 0;

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2025-11-24 21:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24  8:46 [PATCH] drm/i915/display: Check number of scalers for casf Nemesa Garg
2025-11-24 11:09 ` Nautiyal, Ankit K
2025-11-24 21:07   ` Ville Syrjälä [this message]
2025-11-25  3:31     ` Nautiyal, Ankit K
2025-11-25  0:59 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-11-25  2:14 ` ✓ CI.KUnit: success " Patchwork
2025-11-25  3:23 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-25  5:18 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-26  8:41 ` [PATCH v2] drm/i915/crtc: Expose sharpness only if num_scalers is >= 2 Nemesa Garg
2025-11-28  6:13   ` Nautiyal, Ankit K
2025-11-26  8:52 ` ✓ CI.KUnit: success for drm/i915/display: Check number of scalers for casf (rev2) Patchwork
2025-11-26  9:55 ` ✗ i915.CI.BAT: failure " Patchwork
2025-11-26  9:55 ` ✓ Xe.CI.BAT: success " Patchwork
2025-11-26 10:48 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-28  8:25   ` Garg, Nemesa
2025-11-27  6:31 ` ✓ i915.CI.BAT: success " Patchwork
2025-11-27 10:32 ` ✗ i915.CI.Full: failure " Patchwork
2025-11-28  7:00 ` ✓ 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=aSTJIoHSCRuomRFk@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=nemesa.garg@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.