Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/i915/kms_dsc: add limited flag
Date: Wed, 31 May 2023 14:46:48 +0530	[thread overview]
Message-ID: <cb3cd5ba-639f-bd05-a64a-b78c76cd9de0@intel.com> (raw)
In-Reply-To: <20230530173510.qi55lelzipcdclit@zkempczy-mobl2>



On 30-May-23 11:05 PM, Zbigniew Kempczyński wrote:
> On Mon, May 29, 2023 at 10:10:22PM +0530, Swati Sharma wrote:
>> Add limited flag to restrict test execution to one valid pipe-output
>> combination. By default all tests will run on all valid pipe-output
>> combinations.
>>
>> v2: -rename extended to limited (Kamil)
>>
>> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>> ---
>>   tests/i915/kms_dsc.c | 26 ++++++++++++++++++++++++--
>>   1 file changed, 24 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/i915/kms_dsc.c b/tests/i915/kms_dsc.c
>> index 3ce28f84..9ddb441d 100644
>> --- a/tests/i915/kms_dsc.c
>> +++ b/tests/i915/kms_dsc.c
>> @@ -51,6 +51,7 @@ typedef struct {
>>   	int input_bpc;
>>   	int disp_ver;
>>   	enum pipe pipe;
>> +	bool limited;
>>   } data_t;
>>   
>>   static int output_format_list[] = {DSC_FORMAT_YCBCR420, DSC_FORMAT_YCBCR444};
>> @@ -250,13 +251,34 @@ static void test_dsc(data_t *data, enum dsc_test_type test_type, int bpc,
>>   
>>   		igt_dynamic_f("pipe-%s-%s%s",  kmstest_pipe_name(data->pipe), data->output->name, name)
>>   			update_display(data, test_type);
>> +
>> +		if (data->limited)
>> +			break;
>>   	}
>>   }
>>   
>> -igt_main
>> +static int opt_handler(int opt, int opt_index, void *_data)
>>   {
>> -	data_t data = {};
> 
> You don't need to introduce static data below, handler has pointer
> to it, and functions are called with &data so keeping this on stack
> is better for me (protects from global access in any place).
> 
>> +	data_t *data = _data;
>> +
>> +	switch (opt) {
>> +	case 'l':
>> +		data->limited = true;
>> +		break;
>> +	default:
>> +		return IGT_OPT_HANDLER_ERROR;
>> +	}
>> +
>> +	return IGT_OPT_HANDLER_SUCCESS;
>> +}
>> +
>> +static const char help_str[] =
>> +	"  --limited\t\tLimit execution to 1 valid pipe-output combo\n";
> 
> I see you're using short option '-l', just add this to line above like:
> 
> "  --limited\t-l\tLimit ..."
> 
>>   
>> +static data_t data = {};
> 
> Keep this on stack. With this nit fixed:
> 
> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>

Thanks Zbigniew for the review. With above changes floated v3.

> 
> --
> Zbigniew
> 
>> +
>> +igt_main_args("l", NULL, help_str, opt_handler, &data)
>> +{
>>   	igt_fixture {
>>   		data.drm_fd = drm_open_driver_master(DRIVER_INTEL | DRIVER_XE);
>>   		data.devid = intel_get_drm_devid(data.drm_fd);
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2023-05-31  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 16:40 [igt-dev] [PATCH i-g-t v2] tests/i915/kms_dsc: add limited flag Swati Sharma
2023-05-30 15:05 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-05-30 17:35 ` [igt-dev] [PATCH i-g-t v2] " Zbigniew Kempczyński
2023-05-31  9:16   ` Sharma, Swati2 [this message]
2023-05-31  8:24 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=cb3cd5ba-639f-bd05-a64a-b78c76cd9de0@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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