public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Reddy Guddati, Santhosh" <santhosh.reddy.guddati@intel.com>
To: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Sharma, Swati2" <swati2.sharma@intel.com>
Subject: Re: [PATCH i-g-t 4/4] tests/intel/kms_fbc_dirty_rect: check the plane size before fbc dirty rect tests
Date: Tue, 31 Mar 2026 12:52:46 +0530	[thread overview]
Message-ID: <c186c0e0-7324-4ca8-9be3-ea259385e07a@intel.com> (raw)
In-Reply-To: <d391a0cc1f238aa4f665e09e0c3782039e53030b.camel@intel.com>



On 27-03-2026 13:41, Govindapillai, Vinod wrote:
> On Fri, 2026-03-27 at 10:35 +0530, Reddy Guddati, Santhosh wrote:
>> Hi Vinod,
>>
>> On 26-03-2026 12:55, Vinod Govindapillai wrote:
>>> If the FBC cannot support the plan size, skip the tests
>>>
>> %s/plan/plane
>>> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
>>> ---
>>>    tests/intel/kms_fbc_dirty_rect.c | 19 +++++++++++++++++--
>>>    1 file changed, 17 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tests/intel/kms_fbc_dirty_rect.c
>>> b/tests/intel/kms_fbc_dirty_rect.c
>>> index efbd46985..ee13e95dd 100644
>>> --- a/tests/intel/kms_fbc_dirty_rect.c
>>> +++ b/tests/intel/kms_fbc_dirty_rect.c
>>> @@ -401,6 +401,22 @@ static void cleanup(data_t *data)
>>>    	igt_display_commit2(&data->display, COMMIT_ATOMIC);
>>>    }
>>>    
>>> +static bool check_fbc_supported(data_t *data)
>>> +{
>>> +	if (!intel_fbc_supported(data->crtc)) {
>>> +		igt_info("FBC not supported by the chipset on
>>> pipe\n");
>>> +		return false;
>>> +	}
>>> +
>>> +	if (!intel_fbc_plane_size_supported(&data->display, data-
>>>> mode->hdisplay,
>>> +					    data->mode->vdisplay))
>>> {
>>> +		igt_info("Plane size not supported as per FBC size
>>> restrictions\n");
>>> +		return false;
>>> +	}
>>> +
>>> +	return true;
>>> +}
>>> +
>>>    static bool prepare_test(data_t *data)
>>>    {
>>>    	igt_display_reset(&data->display);
>>> @@ -411,8 +427,7 @@ static bool prepare_test(data_t *data)
>>>    	data->pipe_crc = igt_crtc_crc_new(data->crtc,
>>>    					
>>> IGT_PIPE_CRC_SOURCE_AUTO);
>>>    
>>> -	igt_require_f(intel_fbc_supported(data->crtc),
>>> -		      "FBC not supported by the chipset on
>>> pipe\n");
>>> +	igt_require_f(check_fbc_supported(data), "FBC is not
>>> supported with this configuration\n");
>>>    
>> Since the change in fbc dirty rectangle is independent of other
>> changes
>> in the series and imho this can be a split as separate patch from
>> blocking it.
> 
> Yes. No dependency to other patches in this series. If this can be RB-
> ed with that typo fixed in the commit message, only this patch could be
> cherry-picked and merge and fix the typo at the merge time? I guess no
> need to resend only this patch again with typo fixed and waste CI. I
> don't have commit rights. Could you pls do that.
> 
> thanks
> Vinod

This change LGTM. I will merge these changes with typo fix.
Reviewed-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>


Regards,
Santhosh
> 
>>
>> Regards,
>> Santhosh
>>>    	if (psr_sink_support(data->drm_fd, data->debugfs_fd,
>>> PSR_MODE_1, NULL) ||
>>>    	    psr_sink_support(data->drm_fd, data->debugfs_fd,
>>> PSR_MODE_2, NULL) ||
>>
> 


  reply	other threads:[~2026-03-31  7:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  7:25 [PATCH i-g-t 0/4] updates to fbc tests Vinod Govindapillai
2026-03-26  7:25 ` [PATCH i-g-t 1/4] tests/intel/kms_frontbuffer_tracking: update the outdated fbc status checks Vinod Govindapillai
2026-03-26  9:27   ` Jani Nikula
2026-03-26 22:45     ` Ville Syrjälä
2026-03-31 10:49       ` Govindapillai, Vinod
2026-04-10 14:14       ` Kamil Konieczny
2026-03-26  7:25 ` [PATCH i-g-t 2/4] lib/i915/fbc: extract intel_fbc_get_fbc_status() Vinod Govindapillai
2026-03-26  7:25 ` [PATCH i-g-t 3/4] tests/intel/kms_frontbuffer_tracking: use intel_fbc_get_fbc_status() Vinod Govindapillai
2026-03-26  7:25 ` [PATCH i-g-t 4/4] tests/intel/kms_fbc_dirty_rect: check the plane size before fbc dirty rect tests Vinod Govindapillai
2026-03-27  5:05   ` Reddy Guddati, Santhosh
2026-03-27  8:11     ` Govindapillai, Vinod
2026-03-31  7:22       ` Reddy Guddati, Santhosh [this message]
2026-03-26 13:43 ` ✓ Xe.CI.BAT: success for updates to fbc tests Patchwork
2026-03-26 14:00 ` ✓ i915.CI.BAT: " Patchwork
2026-03-27  3:45 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-27  8:48 ` ✗ i915.CI.Full: failure " 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=c186c0e0-7324-4ca8-9be3-ea259385e07a@intel.com \
    --to=santhosh.reddy.guddati@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=swati2.sharma@intel.com \
    --cc=vinod.govindapillai@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