From: "B, Jeevan" <jeevan.b@intel.com>
To: "B, Jeevan" <jeevan.b@intel.com>,
"Modem, Bhanuprakash" <bhanuprakash.modem@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 7/8] tests/kms_setmode: Force joiner support in bigjoiner checks
Date: Thu, 27 Jun 2024 08:29:30 +0000 [thread overview]
Message-ID: <DM4PR11MB6312CDDB03F882AED33FF43290D72@DM4PR11MB6312.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM4PR11MB6312CFB9FF56795F65D3DEE490D72@DM4PR11MB6312.namprd11.prod.outlook.com>
LGTM
Reviewed-by: Jeevan B <jeevan.b@intel.com>
> -----Original Message-----
> From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of B, Jeevan
> Sent: Thursday, June 27, 2024 12:35 PM
> To: Modem, Bhanuprakash <bhanuprakash.modem@intel.com>; igt-
> dev@lists.freedesktop.org
> Cc: Joshi, Kunal1 <kunal1.joshi@intel.com>
> Subject: RE: [i-g-t V6 7/8] tests/kms_setmode: Force joiner support in bigjoiner
> checks
>
>
>
> > -----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 7/8] tests/kms_setmode: 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_setmode.c | 22 ++++++++++++++++++----
> > 1 file changed, 18 insertions(+), 4 deletions(-)
> >
> > diff --git a/tests/kms_setmode.c b/tests/kms_setmode.c index
> > 490bfd3dd..95c5bfadc 100644
> > --- a/tests/kms_setmode.c
> > +++ b/tests/kms_setmode.c
> > @@ -709,24 +709,38 @@ static void test_one_combination(const struct
> > test_config *tconf,
> >
> > for (i = 0; i < crtc_count; i++) {
> > struct crtc_config *crtc = &crtcs[i];
> > + char conn_name[24], prev_conn_name[24];
> > +
> > + snprintf(conn_name, sizeof(conn_name),
> > + "%s-%d",
> > + kmstest_connector_type_str(crtcs[i].cconfs-
> > >connector->connector_type),
> > + crtcs[i].cconfs->connector-
> > >connector_type_id);
> > +
> > + if (i > 0)
> > + snprintf(prev_conn_name,
> > sizeof(prev_conn_name),
> > + "%s-%d",
> > + kmstest_connector_type_str(crtcs[i -
> > 1].cconfs->connector->connector_type),
> > + crtcs[i - 1].cconfs->connector-
> > >connector_type_id);
> Same here...
> >
> > /*
> > * Handle BW limitations on intel hardware:
> > *
> > - * if mode resolution > 5K (or) mode clock >
> > max_dotclock,
> > + * 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)
> > + * - previous crtc (force joiner (or) mode resolution >
> > 5K (or)
> > * mode clock > max_dotclock) and
> > * - current & previous crtcs are consecutive
> > */
> > - if ((igt_bigjoiner_possible(&crtc->mode, max_dotclock)
> > &&
> > + if (((igt_check_force_joiner_status(drm_fd, conn_name)
> > ||
> > + igt_bigjoiner_possible(&crtc->mode, max_dotclock))
> > &&
> > ((crtc->crtc_idx >= (tconf->resources->count_crtcs -
> > 1)) ||
> > ((i < (crtc_count - 1)) && (abs(crtcs[i + 1].crtc_idx -
> > crtc->crtc_idx) <= 1)))) ||
> > - ((i > 0) && igt_bigjoiner_possible(&crtc[i - 1].mode,
> > max_dotclock) &&
> > + ((i > 0) && (igt_check_force_joiner_status(drm_fd,
> > prev_conn_name) ||
> > + igt_bigjoiner_possible(&crtc[i -
> > 1].mode, max_dotclock)) &&
> > (abs(crtc->crtc_idx - crtcs[i - 1].crtc_idx) <= 1))) {
> > igt_info("Combo: %s is not possible with
> selected mode(s).\n",
> > test_name);
> > goto out;
> > --
> > 2.43.2
next prev parent reply other threads:[~2024-06-27 8:29 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
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 [this message]
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=DM4PR11MB6312CDDB03F882AED33FF43290D72@DM4PR11MB6312.namprd11.prod.outlook.com \
--to=jeevan.b@intel.com \
--cc=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