public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: "Bhadane, Dnyaneshwar" <dnyaneshwar.bhadane@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Heikkila, Juha-pekka" <juha-pekka.heikkila@intel.com>,
	"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>
Subject: Re: [igt-dev] [i-g-t] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test
Date: Mon, 16 Jan 2023 15:44:54 +0530	[thread overview]
Message-ID: <917ad227-fbae-a57a-a539-5dd878157ada@intel.com> (raw)
In-Reply-To: <IA1PR11MB6266EA7F413938CAE8CBE29BE2C19@IA1PR11MB6266.namprd11.prod.outlook.com>



On Mon-16-01-2023 12:12 pm, Bhadane, Dnyaneshwar wrote:
> Hi Ville,
> 
>> -----Original Message-----
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Sent: Thursday, January 12, 2023 6:07 PM
>> To: Bhadane, Dnyaneshwar <dnyaneshwar.bhadane@intel.com>
>> Cc: igt-dev@lists.freedesktop.org; Kurmi, Suresh Kumar
>> <suresh.kumar.kurmi@intel.com>; Heikkila, Juha-pekka <juha-
>> pekka.heikkila@intel.com>
>> Subject: Re: [igt-dev] [i-g-t] tests/kms_cursor_crc: skip pipe on invalid
>> connector in cursor size test
>>
>> On Thu, Jan 12, 2023 at 04:27:02PM +0530, Dnyaneshwar Bhadane wrote:
>>> Only the valid pipe connector combination reach to the igt commit.
>>> Cursor max-size test will not affect existing flow as only skip for
>>> invalid connector.
>>> For cursor-dpms and cursor-suspend not require to check
>>> require_cursor_size becuase the cursor height and width used from drm
>> capablities.
>>>
>>> Signed-off-by: Dnyaneshwar Bhadane
>> <dnyaneshwar.bhadane@intel.com>
>>>
>>> ---
>>>   tests/kms_cursor_crc.c | 21 +++++++++++++++------
>>>   1 file changed, 15 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/tests/kms_cursor_crc.c b/tests/kms_cursor_crc.c index
>>> d5a4b30b..4ab4c005 100644
>>> --- a/tests/kms_cursor_crc.c
>>> +++ b/tests/kms_cursor_crc.c
>>> @@ -752,6 +752,13 @@ static void run_size_tests(data_t *data, int w, int
>> h)
>>>   			for_each_pipe(&data->display, pipe) {
>>>   				data->pipe = pipe;
>>>
>>> +				if(!igt_pipe_connector_valid(pipe, data-
>>> output)) {
>>
>> Isn't there a for_each_something() that does all of that?
> 
> Yes, I found for_each_pipe_with_valid_output()  and this macro loop checks for the invalid connectors on
> each pipe. I will update the code using for_each_pipe_with_valid_output().
> Thanks for the suggestion.

As for_each_pipe_with_valid_output() will iterate over all possible 
pipe/output combinations which is not required (one output is enough).

I think you can use for_each_pipe_with_single_output();

- Bhanu

> 
> Dnyaneshwar Bhadane,
> Intel
> 
>>
>>> +					igt_debug("Invalid connector on
>> pipe-%s-%s\n",
>>> +						kmstest_pipe_name(pipe),
>>> +						data->output->name);
>>> +					continue;
>>> +				}
>>> +
>>>   				if (require_cursor_size(data, w, h)) {
>>>   					igt_info("Cursor size %dx%d not
>> supported by driver\n", w, h);
>>>   					continue;
>>> @@ -854,9 +861,10 @@ static void run_tests_on_pipe(data_t *data)
>>>   			data->pipe = pipe;
>>>   			data->flags = TEST_DPMS;
>>>
>>> -			if (require_cursor_size(data, data->cursor_max_w,
>> data->cursor_max_h)) {
>>> -				igt_debug("Cursor size %dx%d not supported
>> by driver\n",
>>> -					  data->cursor_max_w, data-
>>> cursor_max_h);
>>> +			if(!igt_pipe_connector_valid(pipe, data->output)) {
>>> +				igt_debug("Invalid connector on pipe-%s-
>> %s\n",
>>> +					kmstest_pipe_name(pipe),
>>> +					data->output->name);
>>>   				continue;
>>>   			}
>>>
>>> @@ -875,9 +883,10 @@ static void run_tests_on_pipe(data_t *data)
>>>   			data->pipe = pipe;
>>>   			data->flags = TEST_SUSPEND;
>>>
>>> -			if (require_cursor_size(data, data->cursor_max_w,
>> data->cursor_max_h)) {
>>> -				igt_debug("Cursor size %dx%d not supported
>> by driver\n",
>>> -					  data->cursor_max_w, data-
>>> cursor_max_h);
>>> +			if(!igt_pipe_connector_valid(pipe, data->output)) {
>>> +				igt_debug("Invalid connector on pipe-%s-
>> %s\n",
>>> +					kmstest_pipe_name(pipe),
>>> +					data->output->name);
>>>   				continue;
>>>   			}
>>>
>>> --
>>> 2.35.1
>>
>> --
>> Ville Syrjälä
>> Intel

  reply	other threads:[~2023-01-16 10:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 10:57 [igt-dev] [i-g-t] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test Dnyaneshwar Bhadane
2023-01-12 12:36 ` Ville Syrjälä
2023-01-16  6:42   ` Bhadane, Dnyaneshwar
2023-01-16 10:14     ` Modem, Bhanuprakash [this message]
2023-01-12 15:06 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-12 21:39 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-01-16 14:32 ` [igt-dev] [PATCH] [i-g-t, v2] " Dnyaneshwar Bhadane
2023-01-16 14:42   ` Petri Latvala
2023-01-23  9:58     ` Bhadane, Dnyaneshwar
2023-01-23 10:15       ` Petri Latvala
2023-01-23 10:39         ` Bhadane, Dnyaneshwar
2023-01-16 15:06 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev2) Patchwork
2023-01-23 15:30 ` [igt-dev] [i-g-t, v3] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test Dnyaneshwar Bhadane
2023-01-23 16:04   ` Modem, Bhanuprakash
2023-01-23 17:12 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev3) Patchwork
2023-01-24  3:56 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-24 13:03 ` [igt-dev] [i-g-t, v4] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test Dnyaneshwar Bhadane
2023-01-24 13:39   ` Modem, Bhanuprakash
2023-01-24 15:33 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev4) Patchwork
2023-01-25 10:49 ` [igt-dev] [i-g-t, v5] tests/kms_cursor_crc: s/for_each_pipe/for_each_pipe_with_single_output/ Dnyaneshwar Bhadane
2023-01-25 16:44 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev5) Patchwork
2023-01-26  1:52 ` [igt-dev] ✓ Fi.CI.IGT: " 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=917ad227-fbae-a57a-a539-5dd878157ada@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juha-pekka.heikkila@intel.com \
    --cc=suresh.kumar.kurmi@intel.com \
    --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