public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>
To: "Bilal, Mohammed" <mohammed.bilal@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 v1] kms/feature_discovery: Add VRR capability subtest per output
Date: Fri, 20 Mar 2026 10:46:19 +0530	[thread overview]
Message-ID: <57b0a0d1-5737-41a4-9abe-49fad4804d96@intel.com> (raw)
In-Reply-To: <LV2PR11MB6045974F9E4C0C24CE5731E38197A@LV2PR11MB6045.namprd11.prod.outlook.com>

Hi Bilal,

Thanks for the review.

On 1/22/2026 9:48 PM, Bilal, Mohammed wrote:
> Hi Ramanaidu ,
>
>> -----Original Message-----
>> From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Naladala
>> Ramanaidu
>> Sent: 21 January 2026 05:43
>> To: igt-dev@lists.freedesktop.org
>> Cc: Sharma, Swati2 <swati2.sharma@intel.com>; Naladala, Ramanaidu
>> <ramanaidu.naladala@intel.com>
>> Subject: [PATCH i-g-t v1] kms/feature_discovery: Add VRR capability subtest per
>> output
>>
>> Add a dynamic "vrr" subtest that checks vrr capability on each connected output,
>> skipping if the driver or output lacks VRR support.
>>
>> Signed-off-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com>
>> ---
>>   tests/kms_feature_discovery.c | 19 +++++++++++++++++++
>>   1 file changed, 19 insertions(+)
>>
>> diff --git a/tests/kms_feature_discovery.c b/tests/kms_feature_discovery.c index
>> da80ecf66..bf36740cf 100644
>> --- a/tests/kms_feature_discovery.c
>> +++ b/tests/kms_feature_discovery.c
>> @@ -60,6 +60,10 @@
>>    * Description: Make sure that we have eDP panel with PSR2 support.
>>    * Mega feature: PSR
>>    *
>> + * SUBTEST: vrr
>> + * Description: Make sure that we have VRR support on output.
>> + * Mega feature: Adaptive Sync
>> + *
>>    * SUBTEST: dp-mst
>>    * Description: Make sure that we have DP-MST configuration.
>>    *
>> @@ -155,6 +159,21 @@ int igt_main() {
>>   			igt_require(psr_sink_support(fd, debugfs_fd,
>> PSR_MODE_2, NULL));
>>   		}
>>
>> +		igt_describe("Make sure that we have VRR support on output.");
>> +		igt_subtest_with_dynamic("vrr") {
> igt_subtest could be sufficient here, as feature discovery only requires checking if any output supports VRR.
Dynamic subtest for each output clearly shows which output will support 
and which don't.
>
>> +			igt_output_t *output;
>> +
>> +			for_each_connected_output(&display, output) {
>> +				igt_dynamic_f("%s", output->name) {
>> +					if (!igt_output_has_prop(output,
>> IGT_CONNECTOR_VRR_CAPABLE))
>> +						igt_skip("Driver not supports
>> VRR.\n");
> With igt_dynamic_f, if the driver does not support VRR, this skip message will repeat for every output.
> Better to check driver capability once before iterating.
Sure. I will fix in the next rev.
>
>> +
>> +					if (!igt_output_get_prop(output,
>> IGT_CONNECTOR_VRR_CAPABLE))
>> +						igt_skip("Output not supports
>> VRR.\n");
>> +				}
>> +			}
>> +		}
>> +
>>   		igt_describe("Make sure that we have DP-MST configuration.");
>>   		igt_subtest("dp-mst") {
>>   			struct kmstest_connector_config config;
>> --
>> 2.43.0
> Regards,
> Mohammed Bilal .
>

  reply	other threads:[~2026-03-20  5:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  0:13 [PATCH i-g-t v1] kms/feature_discovery: Add VRR capability subtest per output Naladala Ramanaidu
2026-01-21  1:16 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-01-21  1:19 ` ✓ i915.CI.BAT: " Patchwork
2026-01-21  4:58 ` [PATCH i-g-t v1] " S, Sowmiya
2026-03-20  5:53   ` Naladala, Ramanaidu
2026-03-20  6:31     ` Naladala, Ramanaidu
2026-01-21  5:47 ` ✗ Xe.CI.Full: failure for " Patchwork
2026-01-21 11:10 ` ✓ i915.CI.Full: success " Patchwork
2026-01-22 16:18 ` [PATCH i-g-t v1] " Bilal, Mohammed
2026-03-20  5:16   ` Naladala, Ramanaidu [this message]
2026-03-20  6:43 ` [PATCH i-g-t v2] " Naladala Ramanaidu
2026-03-26  7:12   ` Sharma, Swati2
2026-03-26  8:05     ` Naladala, Ramanaidu
2026-03-20  7:25 ` ✓ Xe.CI.BAT: success for kms/feature_discovery: Add VRR capability subtest per output (rev2) Patchwork
2026-03-20  7:51 ` ✓ i915.CI.BAT: " Patchwork
2026-03-20 18:30 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-21  2:47 ` ✗ 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=57b0a0d1-5737-41a4-9abe-49fad4804d96@intel.com \
    --to=ramanaidu.naladala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mohammed.bilal@intel.com \
    --cc=swati2.sharma@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