public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>
To: "S, Sowmiya" <sowmiya.s@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 12:01:46 +0530	[thread overview]
Message-ID: <e19b3713-4095-4fe1-ae25-920195a0be04@intel.com> (raw)
In-Reply-To: <82ebd2b2-f1b2-4130-aa1d-e911d9ad4194@intel.com>

Hi Sowmiya,

On 3/20/2026 11:23 AM, Naladala, Ramanaidu wrote:
> Hi Sowmiya,
>
> Thanks for the review.
>
> On 1/21/2026 10:28 AM, S, Sowmiya 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.");
>> Use igt_skip_on_f, so only the current dynamic subtest is skipped, 
>> not the entire test.
>
> Sure, I will update the logic to use igt_skip_on_f.
When converting from igt_skip to igt_skip_on_if it introduced a 
LONG_LINE warning in checkpatch. To avoid this, I am proceeding with the 
if + igt_skip approach instead.
>
> FYI, Using igt_skip also skips only the current dynamic subtest, not 
> the entire test.
>
>>
>> Regards,
>> Sowmiya
>>
>>> +        igt_subtest_with_dynamic("vrr") {
>>> +            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");
>>> +
>>> +                    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,
> Ramanaidu N.

  reply	other threads:[~2026-03-20  6:32 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 [this message]
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
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=e19b3713-4095-4fe1-ae25-920195a0be04@intel.com \
    --to=ramanaidu.naladala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sowmiya.s@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