Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: "B, Jeevan" <jeevan.b@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Joshi, Kunal1" <kunal1.joshi@intel.com>
Subject: Re: [i-g-t V6 6/8] tests/kms_flip: Force joiner support in bigjoiner checks
Date: Thu, 27 Jun 2024 12:50:49 +0530	[thread overview]
Message-ID: <a0bf4c0a-e6ad-40d1-bd77-cf333f1c814b@intel.com> (raw)
In-Reply-To: <DM4PR11MB63127477EE32B49DEA29C12090D72@DM4PR11MB6312.namprd11.prod.outlook.com>

Hi Jeevan,

Thanks for the review, please find my comments inline.

On 27-06-2024 12:34 pm, B, Jeevan wrote:
> 
> 
>> -----Original Message-----
>> From: Modem, Bhanuprakash <bhanuprakash.modem@intel.com>
>> Sent: Tuesday, June 18, 2024 1:53 PM
>> To: igt-dev@lists.freedesktop.org; B, Jeevan <jeevan.b@intel.com>
>> Cc: Modem, Bhanuprakash <bhanuprakash.modem@intel.com>; Joshi, Kunal1
>> <kunal1.joshi@intel.com>
>> Subject: [i-g-t V6 6/8] tests/kms_flip: Force joiner support in bigjoiner checks
>>
>> As we recently introduced the option (through debugfs) to force the bigjoiner,
>> needs to extend the support in bigjoiner checks to handle the force joiner.
>>
>> V2: - Fix connector name
>>
>> Cc: Kunal Joshi <kunal1.joshi@intel.com>
>> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> ---
>>   tests/kms_flip.c | 23 +++++++++++++++++++----
>>   1 file changed, 19 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/kms_flip.c b/tests/kms_flip.c index d352ee14c..cbabbe74f
>> 100755
>> --- a/tests/kms_flip.c
>> +++ b/tests/kms_flip.c
>> @@ -1730,22 +1730,37 @@ static void run_test_on_crtc_set(struct
>> test_output *o, int *crtc_idxs,
>>   	/*
>>   	 * Handle BW limitations on intel hardware:
>>   	 *
>> -	 * if mode resolution > 5K (or) mode clock > max_dotclock, then ignore
>> +	 * if force joiner (or) mode resolution > 5K (or) mode clock >
>> +max_dotclock, then ignore
>>   	 *  - last crtc in single/multi-connector config
>>   	 *  - consecutive crtcs in multi-connector config
>>   	 *
>>   	 * in multi-connector config ignore if
>> -	 *  - previous crtc (mode resolution > 5K or mode clock > max_dotclock)
>> and
>> +	 *  - previous crtc (force joiner or mode resolution > 5K or mode
>> +clock > max_dotclock) and
>>   	 *  - current & previous crtcs are consecutive
>>   	 */
>>   	if (!is_intel_device(drm_fd))
>>   		goto test;
>>
>>   	for (i = 0; i < crtc_count; i++) {
>> -		if ((igt_bigjoiner_possible(&o->kmode[i], max_dotclock) &&
>> +		char conn_name[24], prev_conn_name[24];
>> +
>> +		snprintf(conn_name, sizeof(conn_name),
>> +			 "%s-%d",
>> +			 kmstest_connector_type_str(o->kconnector[i]-
>>> connector_type),
>> +			 o->kconnector[i]->connector_type_id);
>> +
>> +		if (i > 0)
>> +			snprintf(prev_conn_name, sizeof(prev_conn_name),
>> +				 "%s-%d",
>> +				 kmstest_connector_type_str(o->kconnector[i -
>> 1]->connector_type),
>> +				 o->kconnector[i - 1]->connector_type_id);
> Is printing this necessary ??

Here we are not printing anything, but extracting the connector name 
from o->kconnector.

- Bhanu

>> +
>> +		if (((igt_check_force_joiner_status(drm_fd, conn_name) ||
>> +		      igt_bigjoiner_possible(&o->kmode[i], max_dotclock)) &&
>>   		     ((crtc_idxs[i] >= (total_crtcs - 1)) ||
>>   		      ((i < (crtc_count - 1)) && (abs(crtc_idxs[i + 1] - crtc_idxs[i])
>> <= 1)))) ||
>> -		    ((i > 0) && igt_bigjoiner_possible(&o->kmode[i - 1],
>> max_dotclock) &&
>> +		    ((i > 0) && (igt_check_force_joiner_status(drm_fd,
>> prev_conn_name) ||
>> +				 igt_bigjoiner_possible(&o->kmode[i - 1],
>> max_dotclock)) &&
>>   		     (abs(crtc_idxs[i] - crtc_idxs[i - 1]) <= 1))) {
>>
>>   			igt_debug("Combo: %s is not possible with selected
>> mode(s).\n", test_name);
>> --
>> 2.43.2
> 

  reply	other threads:[~2024-06-27  7:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  8:22 [i-g-t V6 0/8] Force joiner support in bigjoiner checks Bhanuprakash Modem
2024-06-18  8:22 ` [i-g-t V6 1/8] lib/igt_kms: Split the bigjoiner check into multiple Bhanuprakash Modem
2024-06-24 18:15   ` B, Jeevan
2024-06-18  8:22 ` [i-g-t V6 2/8] lib/igt_kms: Update force joiner debugfs check Bhanuprakash Modem
2024-06-18  8:22 ` [i-g-t V6 3/8] lib/igt_kms: New helper to check force joiner status Bhanuprakash Modem
2024-06-27  6:50   ` B, Jeevan
2024-06-18  8:22 ` [i-g-t V6 4/8] lib/igt_kms: Force joiner support in bigjoiner checks Bhanuprakash Modem
2024-06-27  6:54   ` B, Jeevan
2024-06-18  8:22 ` [i-g-t V6 5/8] tests/intel/kms_pm_lpsp: " Bhanuprakash Modem
2024-06-27  6:58   ` B, Jeevan
2024-06-18  8:22 ` [i-g-t V6 6/8] tests/kms_flip: " Bhanuprakash Modem
2024-06-27  7:04   ` B, Jeevan
2024-06-27  7:20     ` Modem, Bhanuprakash [this message]
2024-06-27  8:28       ` B, Jeevan
2024-06-18  8:22 ` [i-g-t V6 7/8] tests/kms_setmode: " Bhanuprakash Modem
2024-06-27  7:05   ` B, Jeevan
2024-06-27  8:29     ` B, Jeevan
2024-06-18  8:22 ` [i-g-t V6 8/8] HAX: Test force joiner on BAT Bhanuprakash Modem
2024-06-18 13:54 ` ✓ CI.xeBAT: success for Force joiner support in bigjoiner checks (rev8) Patchwork
2024-06-18 13:58 ` ✓ Fi.CI.BAT: " Patchwork
2024-06-18 21:35 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-06-19  2:24 ` ✗ CI.xeFULL: " 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=a0bf4c0a-e6ad-40d1-bd77-cf333f1c814b@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@intel.com \
    --cc=kunal1.joshi@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