Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
	Kunal Joshi <kunal1.joshi@intel.com>
Subject: [i-g-t V2 3/6] tests/intel/kms_pm_lpsp: Force joiner support in bigjoiner checks
Date: Thu, 18 Apr 2024 14:49:56 +0530	[thread overview]
Message-ID: <20240418091959.781560-4-bhanuprakash.modem@intel.com> (raw)
In-Reply-To: <20240418091959.781560-1-bhanuprakash.modem@intel.com>

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.

Cc: Kunal Joshi <kunal1.joshi@intel.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
 tests/intel/kms_pm_lpsp.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/intel/kms_pm_lpsp.c b/tests/intel/kms_pm_lpsp.c
index a76b423f4..f9ac508fb 100644
--- a/tests/intel/kms_pm_lpsp.c
+++ b/tests/intel/kms_pm_lpsp.c
@@ -163,6 +163,9 @@ static bool test_constraint(data_t *data)
 	mode = igt_output_get_mode(data->output);
 
 	/* For LPSP avoid Bigjoiner. */
+	if (igt_check_force_joiner_status(data->drm_fd, data->output->name))
+		return false;
+
 	if (igt_bigjoiner_possible(mode, max_dotclock)) {
 		for_each_connector_mode(data->output) {
 			mode = &data->output->config.connector->modes[j__];
-- 
2.43.2


  parent reply	other threads:[~2024-04-18  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  9:19 [i-g-t V2 0/6] Force joiner support in bigjoiner checks Bhanuprakash Modem
2024-04-18  9:19 ` [i-g-t V2 1/6] lib/igt_kms: New helper to check force joiner status Bhanuprakash Modem
2024-04-18  9:19 ` [i-g-t V2 2/6] lib/igt_kms: Force joiner support in bigjoiner checks Bhanuprakash Modem
2024-04-18  9:19 ` Bhanuprakash Modem [this message]
2024-04-18  9:19 ` [i-g-t V2 4/6] tests/kms_flip: " Bhanuprakash Modem
2024-04-18  9:19 ` [i-g-t V2 5/6] tests/kms_setmode: " Bhanuprakash Modem
2024-04-18  9:19 ` [i-g-t V2 6/6] HAX: Test force joiner on BAT Bhanuprakash Modem
2024-04-18 13:35   ` [i-g-t V3 " Bhanuprakash Modem
2024-04-18 11:04 ` ✗ Fi.CI.BAT: failure for Force joiner support in bigjoiner checks (rev3) Patchwork
2024-04-18 11:32 ` ✓ CI.xeBAT: success " Patchwork
2024-04-19  0:05 ` ✗ Fi.CI.BAT: failure for Force joiner support in bigjoiner checks (rev4) Patchwork
2024-04-19  0:09 ` ✓ CI.xeBAT: success " 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=20240418091959.781560-4-bhanuprakash.modem@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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