From: "Reddy Guddati, Santhosh" <santhosh.reddy.guddati@intel.com>
To: Karthik B S <karthik.b.s@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <ankit.k.nautiyal@intel.com>, <kunal1.joshi@intel.com>,
<bhanuprakash.modem@intel.com>
Subject: Re: [PATCH i-g-t v2 2/3] lib/kms: Update force joiner helpers to accomodate Ultra joiner
Date: Wed, 11 Sep 2024 13:13:52 +0530 [thread overview]
Message-ID: <dc9c09b5-bb86-421e-b60d-bcda9717e340@intel.com> (raw)
In-Reply-To: <20240911072204.22825-3-karthik.b.s@intel.com>
Hi Karthik,
Can we add an enum something like below , which can be re used at other
places.
enum joiner_mode {
JOINED_PIPES_NONE,
JOINED_PIPES_1,
JOINED_PIPES_2,
JOINED_PIPES_3,
JOINED_PIPES_4,
JOINED_PIPES_MAX
};
bool kmstest_force_connector_joiner(int drm_fd, drmModeConnector
*connector, int joined_pipes)
{
const char *value;
drmModeConnector *temp;
switch (joined_pipes) {
case 0: -- > case JOINED_PIPES_NONE
value = "0";
break;
On 11-09-2024 12:52, Karthik B S wrote:
> + status = kmstest_force_connector_joiner(data->drm_fd, output->config.connector, 2);
>> status = kmstest_force_connector_joiner(data->drm_fd,
output->config.connector, JOINED_PIPES_2);
next prev parent reply other threads:[~2024-09-11 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 7:22 [PATCH i-g-t v2 0/3] Add tests for ultrajoiner validation Karthik B S
2024-09-11 7:22 ` [PATCH i-g-t v2 1/3] tests/kms_joiner: Add tests for Ultrajoiner validation Karthik B S
2024-09-17 5:06 ` Reddy Guddati, Santhosh
2024-09-18 7:13 ` Karthik B S
2024-09-11 7:22 ` [PATCH i-g-t v2 2/3] lib/kms: Update force joiner helpers to accomodate Ultra joiner Karthik B S
2024-09-11 7:43 ` Reddy Guddati, Santhosh [this message]
2024-09-18 7:14 ` Karthik B S
2024-09-11 7:22 ` [PATCH i-g-t v2 3/3] tests/kms_joiner: Add subtests for force ultra joiner validation Karthik B S
2024-09-12 4:47 ` ✓ Fi.CI.BAT: success for Add tests for ultrajoiner validation (rev2) Patchwork
2024-09-12 4:59 ` ✓ CI.xeBAT: " Patchwork
2024-09-12 23:01 ` ✗ Fi.CI.IGT: failure " 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=dc9c09b5-bb86-421e-b60d-bcda9717e340@intel.com \
--to=santhosh.reddy.guddati@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@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