Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/scaler: Update Pipe src size check in skl_update_scaler
Date: Wed, 20 Mar 2024 12:45:50 +0530	[thread overview]
Message-ID: <b0a3c842-ff3d-454e-99bb-f1336ce70d22@intel.com> (raw)
In-Reply-To: <ZfQGTfxuYJ0bwQ3z@intel.com>


On 3/15/2024 1:56 PM, Ville Syrjälä wrote:
> On Wed, Mar 13, 2024 at 08:08:25PM +0530, Ankit Nautiyal wrote:
>> For Earlier platforms, the Pipe source size is 12-bits so
>> max pipe source width and height is 4096. For newer platforms it is
>> 13-bits so theoretically max width/height is 8192. For few of the
>> earlier platforms the scaler did not use all bits of the PIPESRC,
>> so max scaler source size was used to make that the pipe source
>> size is programmed within limits, before using scaler.
>>
>> This creates a problem, for MTL where scaler source size is 4096, but
>> max pipe source width can theroretically be 8192.
>>
>> Switch the check to use the max scaler destination size, which closely
>> match the limits.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks for the review, pushed to drm-intel-next.

Regards,

Ankit

>
>> ---
>>   drivers/gpu/drm/i915/display/skl_scaler.c | 7 ++++---
>>   1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c b/drivers/gpu/drm/i915/display/skl_scaler.c
>> index 8a934bada624..baa601d27815 100644
>> --- a/drivers/gpu/drm/i915/display/skl_scaler.c
>> +++ b/drivers/gpu/drm/i915/display/skl_scaler.c
>> @@ -213,10 +213,11 @@ skl_update_scaler(struct intel_crtc_state *crtc_state, bool force_detach,
>>   	 * The pipe scaler does not use all the bits of PIPESRC, at least
>>   	 * on the earlier platforms. So even when we're scaling a plane
>>   	 * the *pipe* source size must not be too large. For simplicity
>> -	 * we assume the limits match the scaler source size limits. Might
>> -	 * not be 100% accurate on all platforms, but good enough for now.
>> +	 * we assume the limits match the scaler destination size limits.
>> +	 * Might not be 100% accurate on all platforms, but good enough for
>> +	 * now.
>>   	 */
>> -	if (pipe_src_w > max_src_w || pipe_src_h > max_src_h) {
>> +	if (pipe_src_w > max_dst_w || pipe_src_h > max_dst_h) {
>>   		drm_dbg_kms(&dev_priv->drm,
>>   			    "scaler_user index %u.%u: pipe src size %ux%u "
>>   			    "is out of scaler range\n",
>> -- 
>> 2.40.1

      reply	other threads:[~2024-03-20  7:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 14:38 [PATCH] drm/i915/scaler: Update Pipe src size check in skl_update_scaler Ankit Nautiyal
2024-03-14  1:27 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-03-14 11:07 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-15  8:26 ` [PATCH] " Ville Syrjälä
2024-03-20  7:15   ` 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=b0a3c842-ff3d-454e-99bb-f1336ce70d22@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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