Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: "B, Jeevan" <jeevan.b@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/intel/kms_joiner: Add a new test to validate non-joiner mode
Date: Mon, 27 Jan 2025 14:26:11 +0530	[thread overview]
Message-ID: <beed6586-4463-4402-b739-ebd8bc513e31@intel.com> (raw)
In-Reply-To: <DM4PR11MB63121D29207E8875D958452590EC2@DM4PR11MB6312.namprd11.prod.outlook.com>

Hi Jeevan,

There is no specific debugfs entry at a pipe level to confirm joiner is 
enabled, but I found an entry in display info which shows joiner is 
enabled. "Linked to <> pipes as a (master|slave)". We should be able to 
parse this from display_info to confirm if joiner is enabled for a 
particular mode.

Thanks,
Karthik.B.S

On 1/27/2025 11:20 AM, B, Jeevan wrote:
> Hi Karthik,
>
> I have addressed couple of comments you had given me regarding sorting can mode selection.
> But for validation method apart from commit failure I was trying to find alternate methods but couldn't find any lead, I have couple of opens. 1. Is there any debugfs entry where we get to know joiner is enabled or not. 2. Is it possible to get pipe active status after modeset/commit. Based on this we can validate.
>
> Thanks
> Jeevan B
>

  reply	other threads:[~2025-01-27  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-26 18:19 [PATCH i-g-t] tests/intel/kms_joiner: Add a new test to validate non-joiner mode Jeevan B
2025-01-26 19:27 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-01-26 19:44 ` ✓ i915.CI.BAT: " Patchwork
2025-01-26 20:35 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-26 22:04 ` ✗ i915.CI.Full: " Patchwork
2025-01-27  5:50 ` [PATCH i-g-t] " B, Jeevan
2025-01-27  8:56   ` Karthik B S [this message]
2025-01-28  6:30 ` Sharma, Swati2
  -- strict thread matches above, loose matches on Subject: below --
2025-01-29 17:17 Jeevan B

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=beed6586-4463-4402-b739-ebd8bc513e31@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@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